Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: wifischedule - Add option to select SSID #7581

Open
forcefullpower opened this issue Jan 25, 2025 · 5 comments
Open

Feature request: wifischedule - Add option to select SSID #7581

forcefullpower opened this issue Jan 25, 2025 · 5 comments

Comments

@forcefullpower
Copy link

What would you like to see in luci?

The wifi schedule looks great but only works for disabling the whole wifi. Could you add an option in to just disable a specific SSID so I can use it to setup a kids only wifi that turns off. Would be great to be able to manage kids usage.

@systemcrash
Copy link
Contributor

The wifischedule package does not provide this.

@stokito
Copy link
Contributor

stokito commented Feb 25, 2025

It looks like such kind of functionality should be implemented on network level, not just a WiFi. There is a separate FR on this #6009
. I guess there are some advanced firewalls for this, please let me know if you know. This would be a good thing for a security in office.
Disabling the SSID while keeping others won't save electricity so it wasn't implemented in the tool.
If you do really need this you may try to make a cron job yourself.

@stokito stokito mentioned this issue Mar 3, 2025
@bracklanna
Copy link

bracklanna commented Mar 3, 2025

I am currently using something like this (with a few more mechanisms, implemented as a shell script) to disable only specific wifi SSIDs while leaving other SSIDs active:

uci set wireless.@wifi-iface[0].disabled=1
uci commit wireless
wifi

Above, @wifi-iface[x] corresponds to each SSID, where x = 0, 1, 2, .... n up to the number of configured SSIDs.

There is definitely a specific use case for this functionality. For example in a home with separate SSIDs such as "IoT Devices", "Home Office," and "General," it is useful to leave "IoT Devices" SSID active at all times, 24/7, as it has security cameras etc. on it. "Home Office" might also stay active at all times, while "General" might only be available from 6AM-9PM daily so that children using it are cut off when it's time for sleeping.

Similar examples could apply in institutional environments like businesses, non-profits, industrial settings, etc.

As far as separate scheduling for ethernet-connected devices, of course that would need to be implemented at the network layer.

Just shutting off the SSIDs for wifi is simpler, faster, easier to implement, and also communicates much more directly to users that their access is cut off. Instead of the wifi indicator on their device showing a normal connection (3 or 4 bars of reception, etc.), yet their internet just "stops working" at a certain time (confusing,) rather they are kicked off wifi completely, the Wifi connection indicator goes dark or blank, and they are unable to reassociate their device.

@stokito
Copy link
Contributor

stokito commented Mar 3, 2025

You probably can try uci set wireless.guest_iface_0.disabled='1' where the guest_iface_0 is an id of the ssid config section

@bracklanna
Copy link

bracklanna commented Mar 3, 2025

Thanks, I'll try that at some point & update here if it works. That would be clearer & therefore preferable as a syntax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants