At a RUTM56 we use one SSID as WAN connection (client) and another as access point. Now we want to use a hard wired switch an GPIO to enable/disable the access point. In event juggler settings we can only enable / disable all wifi together. Is there a possibility to switch a SSID instead of WIFI?
You can set Event Juggler to run a script as an action e.g. a script for a RUTX50 will read as ….
uci set wireless.default_radio0.disabled=‘1’
uci commit wireless
/etc/init.d/network restart
…. to disable the default SSID on 2.4GHz, whilst ….
uci del wireless.default_radio0.disabled=‘1’
uci commit wireless
/etc/init.d/network restart
…. will enable it.
To enable/disable other SSID’s, then you will have to ammend the ‘uci set ….’ and ‘uci del ….’ commands, in the text marked in bold …. wireless.default_radio0.disabled
For a hint as to what that replacement text is, you can run the command ….
uci show wireless
Note that issuing the /etc/init.d/network restart command will restart all network interfaces, and there might be a short drop in connectivity.
Give it a go and see if it does the trick. If you are unfamiliar with uci commands, then take a peer here, if of interest.
There’s an API call that you can use instead of uci; the API route seems to be the way that Teltonika are going longer term. I took a quick look at the API documentation and for the default SSID on 2.4GHz, try using ….
api put /wireless/interfaces/config/default_radio0 ‘{“data”:{“enabled”:“0”}}’
…. to disable the the default SSID on 2.4GHz, and ….
api put /wireless/interfaces/config/default_radio0 ‘{“data”:{“enabled”:“1”}}’
…. to enable it.
The API won’t need a ‘commit equivalent’ but I am unsure as to whether you will need to restart the network - my guess is that it will need a restart. If this guess is correct, then just add, the command below to the end of the script. EDIT: it is suggested by @Marija in other posts that …. “When using the API, there is no need to restart the network ….”.
/etc/init.d/network restart
Let us know how you get on.