Filters/SSID Filter Mode not persistent

Device: NANO
Type: Bug
Status: Closed

The SSID filtering mode doesn't persist when navigating to other pages in the management interface.
This can be reproduced reliably on Nano firmware version 1.0.1 using the following procedure.

From the Recon page, add an SSID to PineAP filter, then navigate to the Filters page. The SSID Filtering panel seems to default to Deny Mode. Switch to Allow Mode. Navigate away from the Filter page, and then back. The SSID Filtering is back in Deny Mode. If you switch Client Filtering to Allow Mode, the setting persists when you navigate away from and back to the page.

The impact is that clients don't seem to be captured when the SSID Filtering is set to Allow Mode for a single SSID.


2016/01/06 22:24
Some additional info:

When clicking on the Switch mode button in the SSID Filtering panel, no event is fired, so no POST is made to the API.

Testing shows that doing the following makes the switch persistent:

POST /api/ HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.5.0
Accept: application/json, text/plain, */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/json;charset=utf-8
X-XSRF-TOKEN: c45ebbc16154ed4bf177ab0354eae11ab09f219e
Content-Length: 60
Cookie: PHPSESSID=15ed80b6ef65f54656c0e840051bff27; XSRF-TOKEN=c45ebbc16154ed4bf177ab0354eae11ab09f219e
DNT: 1
Connection: close
Pragma: no-cache
Cache-Control: no-cache

{"module":"Filters","action":"toggleSSIDMode","mode":"Deny"} //or "mode":"Allow" as appropriate.
2016/01/06 22:50
Fix: ./modules/Filters/js/module.js

registerController('ssidFilterController', ['$api', '$scope', function($api, $scope) {
$scope.mode = '';
$scope.ssid = '';
$scope.ssidFilters = '';

$scope.toggleMode = (function() {
if ($scope.mode == 'Allow') {
$scope.mode = 'Deny';
} else {
$scope.mode = 'Allow';
//Add this>>>
module: 'Filters',
action: 'toggleSSIDMode',
mode: $scope.mode
2016/01/07 09:21
Hi Bobjones,

Thank you for reporting this bug and even providing a fix! I have added the fix to our next firmware release.

Best Regards,

Add Comment:

Please log in to comment.