1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Asus RT-N66U - wireless scheduling issue

Discussion in 'Tomato Firmware' started by Demolishing81, Jul 21, 2012.

  1. Demolishing81

    Demolishing81 Serious Server Member

    I'm running Shibby v097 on my Asus RT-N66U and Linksys E3000. The wireless on/off scheduling (in Access Restrictions) doesn't appear to be working right on the Asus. Basically I have a schedule which turns off the wireless at 00:30 and then turns it back on at 06:00.

    Asus:
    Wireless turns off okay at 00:30
    Wireless does not turn back on at 06:00 although Tomato reports that it is enabled. Status LEDs are not lit. Disabling and re-enabling wireless through the GUI does not resolve this.
    Have to reboot device to resolve it.

    Linksys E3000:
    Behaves as expected.

    I had the same issues when running v093 (I didn't go to v095) but assumed this was down to the shell script bug. Unfortunately it seems not. Anyone else experienced this problem? Ideas and help appreciated.
     
  2. blackmack

    blackmack Addicted to LI Member

    I can confirm this behavior.
     
  3. StevenG

    StevenG LI Guru Member

    I don't shut the wireless off, but do have an access restriction that just blocks all internet access for certain MAC IDs for a certain window. it's working fine on my 66 with Shibbys 097 build.
     
  4. M_ars

    M_ars LI Guru Member

    I can also confirm that problem with wireless on/off in Access Restriction - not working
    Right now, i am not using it...
     
  5. piotrpiano

    piotrpiano Serious Server Member

    Hello everyone! My first post in the forum, though I've been present here in a Read-Only mode for a while ;)

    I also confirm the problem on RT-N66U but it does not seem to be limited to a scheduler only. I think it is a more general problem with bringing wireless up after it was turned off. I actually don't use the scheduler but I manually switch off wireless (with WPS button) when I leave my flat. And when switched on, the same thing as described above happens (not every time though): in the GUI wireless appears to be enabled and working but the led indicator is off and the wlan is down. I am now on Shibby's 097 but I saw it happen also on 095 - though only to 2.4 Ghz band.
     
  6. M_ars

    M_ars LI Guru Member

    @shibby/toastman: can you confirm that problem? any ideas?
     
  7. shibby20

    shibby20 Network Guru Member

    confirm. problem exist from integration with multissid
     
  8. Demolishing81

    Demolishing81 Serious Server Member

    That's good it's been confirmed.
    @Shibby any likelihood this will be fixed in your next release?
     
  9. jyavenard

    jyavenard Network Guru Member

    Is this something unique to the RT-N66 or can you see it on the RT-N16 as well?

    I just tried with the firmware with my last Multi-SSID fixes on a RT-N16, and it worked just fine... Considering those fixes are related to how the wireless drivers are started/stopped, it could very well has fixed this scheduling issue.
     
  10. Toastman

    Toastman Super Moderator Staff Member Member

    In the past year or so many people have commented on this or similar bug on all versions. However, when modders have tried to reproduce it we couldn't. My RT-N16's appeared to work OK. This "bug", if it is one, may have been around for a while.
     
  11. shibby20

    shibby20 Network Guru Member

    i suppose problem is on RT-N builds only.
     
  12. jyavenard

    jyavenard Network Guru Member

    Well, cant reproduce it on either n66 or n16 using rt-n and the build with the new stop/start wireless code.
     
  13. shibby20

    shibby20 Network Guru Member

    well maybe you was already fix it :)
     
  14. M_ars

    M_ars LI Guru Member

    With AOI RT-N V097 i can reproduce it most of the time. (RT-N16)

    BUT with your patch its working like expected
    thx :)
     
  15. Demolishing81

    Demolishing81 Serious Server Member

    Just upgraded to Shibby AIO RT-N v102 and the problem is still apparent unfortunately.
     

Share This Page