sebaz Posted May 3, 2018 Share Posted May 3, 2018 Hi all! Is there a default location for the pineap settings? I'm trying to make it so that the settings stay saved even when you reboot the device. Thanks in advance! Regards, Sebastiaan Quote Link to comment Share on other sites More sharing options...
trashbo4t Posted May 13, 2018 Share Posted May 13, 2018 PineAP settings are stored like any other module onboard the pineapple. To make your configuration static across all boots: ssh root@172.16.42.1 cd /pineapple/modules/PineAP/js Modify module.js block for 'PineAPSettingsController' registerController('PineAPSettingsController', ['$api', '$scope', '$timeout', function($api, $scope, $timeout) { $scope.disableInputs = true; $scope.disableButton = false; $scope.saveAlert = false; $scope.pineAPenabling = false; $scope.settings = { allowAssociations: false, logEvents: false, pineAPDaemon: false, beaconResponses: false, captureSSIDs: false, broadcastSSIDs: false, broadcastInterval: 'low', responseInterval: 'low', sourceMAC: '00:00:00:00:00:00', targetMAC: 'FF:FF:FF:FF:FF:FF' }; Heres an example of some configurations stored here. Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 14, 2018 Author Share Posted May 14, 2018 Thanks for the clear and easy reply! Have a nice day 1 Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 14, 2018 Author Share Posted May 14, 2018 (edited) However, When I change these settings, they don't stay 'saved' The checkboxes load as 'checked' but then get unchecked as the page loads further. Quote registerController('PineAPSettingsController', ['$api', '$scope', '$timeout', function($api, $scope, $timeout) { $scope.disableInputs = true; $scope.disableButton = false; $scope.saveAlert = false; $scope.pineAPenabling = true; $scope.settings = { allowAssociations: false, logEvents: true, pineAPDaemon: true, beaconResponses: false, captureSSIDs: true, broadcastSSIDs: false, broadcastInterval: 'low', responseInterval: 'low', sourceMAC: '00:00:00:00:00:00', targetMAC: 'FF:FF:FF:FF:FF:FF' }; Edited May 14, 2018 by sebaz Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted May 14, 2018 Share Posted May 14, 2018 (edited) 7 minutes ago, sebaz said: When I change these settings, they don't stay 'saved' In the latest RC1 test firmware (i have currently installed) the settings are saved over reboots/power downs - they are stored in /etc/config/pineap Edited May 14, 2018 by Just_a_User Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 14, 2018 Author Share Posted May 14, 2018 Cool! Now the daemon starts properly, and the 'capture SSIDs to Pool' checkbox stays checked. However, the 'log Pineap events' checkbox stays unchecked.. Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted May 14, 2018 Share Posted May 14, 2018 9 minutes ago, sebaz said: However, the 'log Pineap events' checkbox stays unchecked.. For me on TETRA that box state remains over reboot/power cycle. Do you click the "Save PineAP Settings" button each time you change anything? Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 14, 2018 Author Share Posted May 14, 2018 I do, but it doesn't. Im on the nano but latest firmware (2.02) Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted May 14, 2018 Share Posted May 14, 2018 4 minutes ago, sebaz said: I do, but it doesn't. Im on the nano but latest firmware (2.02) OK im using the 2.1.0 RC1 Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 23, 2018 Author Share Posted May 23, 2018 Finally managed to upgrade to 2.1.0 RC1 and it worked. Thanks for the help! Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 23, 2018 Author Share Posted May 23, 2018 Well.. now my API calls stopped working. Do you have any idea if the update changed something with the api for the logging and client modules? Sending notifications still works, so it isn't my api key or syntax as far as I can see Quote Link to comment Share on other sites More sharing options...
sebaz Posted May 23, 2018 Author Share Posted May 23, 2018 Jup, lot of API output changed. Fixed it ^^ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.