Feature request: schedule guest network

[man_at_work]

Hi Merlin,

First of all thanks for all the firmware, thumbs up. However I have a request below.

Is it possible to have scheduler to allow guest network on RTN-66U?
It's allowing the guest network to be allowed only certain timing, e.g. from 8pm - 12am everyday to limit and control the guest connection time.

Thanks,

PS: sorry, I'm not sure whether this is the correct sub forum for such request.

 

[Deleted member 27741]

This should be possible and pretty easy through scripting. Perhaps someone else has already done this and will post you some instructions.

 

[Deleted member 27741]

nvram settings for the three guest 2.4 networks start with:
wl0.1
wl0.2
wl0.3

nvram settings for the three guest 5.0 networks start with:
wl1.1
wl1.2
wl1.3

To start a guest network in SSH, the command is:
nvram set wl0.1_bss_enabled=1
To stop it, the command is:
nvram set wl0.1_bss_enabled=0

After changing the nvram settings, you need to restart wireless via command:
service restart_wireless

Now you need to get those start and stop commands in a script that will start and stop them when you want. Note that you can start/stop as many as you want, so you could start all of the 2.4 guest newtorks with the commands:
nvram set wl0.1_bss_enabled=1
nvram set wl0.2_bss_enabled=1
nvram set wl0.3_bss_enabled=1
service restart_wireless

 

[Martineau]

Hi Merlin,

First of all thanks for all the firmware, thumbs up. However I have a request below.

Is it possible to have scheduler to allow guest network on RTN-66U?
It's allowing the guest network to be allowed only certain timing, e.g. from 8pm - 12am everyday to limit and control the guest connection time.

Thanks,

PS: sorry, I'm not sure whether this is the correct sub forum for such request.

The commands to stop/start both the 2.4 and 5G Guest wireless instance #1 are given here by RMerlin:

http://forums.smallnetbuilder.com/showpost.php?p=66327&postcount=2


and if you follow the User script tutorial on RMerlins Wiki:

https://github.com/RMerl/asuswrt-merlin/wiki

you should be able to modify the cron based example script which schedules the LEDs ON/OFF

https://github.com/RMerl/asuswrt-merlin/wiki/Scheduled-LED-control

to enable/disable the appropriate Guest Wireless according to your desired schedule.

Regards,

 

[dimbert]

Hi guys!

I have one question (because I have no clue about writing a decent script).

So What I need is to create a script that turns off my Guest Network at 8pm and then Turn it on at 23:50 that runs every Monday, Tuesday and Thursday...

So I digged a little bit and found a script in "init-start" that I worked fine for me to make a scheduled reboot...

So I has the idea to add the script to the same "init-start" file.

Is this script correct? Using one gru per line/command is ok?

#!/bin/sh

cru a nvram set wl0.1_bss_enabled=1 "50 23 * * 1,2,4"
cru a nvram commit "50 23 * * 1,2,4"
cru a service restart_wireless "50 23 * * 1,2,4"
cru a nvram set wl0.1_bss_enabled=0 "0 20 * * 1,2,4"
cru a nvram commit "0 20 * * 1,2,4"
cru a service restart_wireless "0 20 * * 1,2,4"
cru a ScheduledReboot "0 7 * * * /sbin/reboot"

Tks a lot guys

 

[dimbert]

Anyone?

 

[hardtotell]

Hi guys!

I have one question (because I have no clue about writing a decent script).

So What I need is to create a script that turns off my Guest Network at 8pm and then Turn it on at 23:50 that runs every Monday, Tuesday and Thursday...

So I digged a little bit and found a script in "init-start" that I worked fine for me to make a scheduled reboot...

So I has the idea to add the script to the same "init-start" file.

Is this script correct? Using one gru per line/command is ok?

#!/bin/sh

cru a nvram set wl0.1_bss_enabled=1 "50 23 * * 1,2,4"
cru a nvram commit "50 23 * * 1,2,4"
cru a service restart_wireless "50 23 * * 1,2,4"
cru a nvram set wl0.1_bss_enabled=0 "0 20 * * 1,2,4"
cru a nvram commit "0 20 * * 1,2,4"
cru a service restart_wireless "0 20 * * 1,2,4"
cru a ScheduledReboot "0 7 * * * /sbin/reboot"

Tks a lot guys

Here's another way. The "&&" means to continue if successful. In other words, if a command were to fail, it would not run the next command.

/jffs/scripts/services-start

cru a GuestsAllowed "50 23 * * 1,2,4 (nvram set wl0.1_bss_enabled=1 && nvram commit && service restart_wireless)"
cru a GuestsDenied "0 20 * * 1,2,4 (nvram set wl0.1_bss_enabled=0 && nvram commit && service restart_wireless)"
cru a ScheduledReboot "0 7 * * * /sbin/reboot"

 

[dimbert]

Here's another way. The "&&" means to continue if successful. In other words, if a command were to fail, it would not run the next command.

/jffs/scripts/services-start

cru a GuestsAllowed "50 23 * * 1,2,4 (nvram set wl0.1_bss_enabled=1 && nvram commit && service restart_wireless)"
cru a GuestsDenied "0 20 * * 1,2,4 (nvram set wl0.1_bss_enabled=0 && nvram commit && service restart_wireless)"
cru a ScheduledReboot "0 7 * * * /sbin/reboot"

Thanks a lot! I'll try it and tomorrow let you know if it's working

This Forum Rocks

 

[dimbert]

Tks! The script worked perfectly...

I'll let my script code that include multiple days and a daily restart

I used the init-start file

#!/bin/sh
cru a GuestsAllowed "59 23 * * 1,2,3,4 (nvram set wl0.1_bss_enabled=1 && nvram commit && service restart_wireless)"
cru a GuestsDenied "30 19 * * 1,2,3 (nvram set wl0.1_bss_enabled=0 && nvram commit && service restart_wireless)"
cru a GuestsDenied "30 20 * * 4 (nvram set wl0.1_bss_enabled=0 && nvram commit && service restart_wireless)"
cru a ScheduledReboot "0 7 * * * /sbin/reboot"