N66U Stuck on 54mbps @5Ghz

Discussion in 'Tomato Firmware' started by cloneman, Oct 10, 2018.

  1. cloneman

    cloneman Addicted to LI Member

    Hi guys,

    I'm on Shibby 1.32 RT-N firmware and I did do some silly things, like dirty flash directly from the RT-AC with no nvram wipe.

    However, the 5Ghz radio on this unit never worked well and I'm wondering if I could get help troubleshooting this anyway.

    For some reason the signal is good but Windows reports "54mbps" and never more for 5Ghz on this router. If I move further away it drops to 48mbps or 36mbps - it's almost as though it "thinks it's G router."

    Anyone know what could cause this?
     
  2. Sean B.

    Sean B. LI Guru Member

    Please post a screen shot of the Basic->Network wireless section and the Advanced->Wireless 5ghz section from the GUI.
     
  3. cloneman

    cloneman Addicted to LI Member

  4. Sean B.

    Sean B. LI Guru Member

    Set:

    Beacon interval = 100

    802.11n Preamble = Green Field ( unless you have legacy G devices )

    WMM = enabled

    APSD Mode = disabled

    After saving reboot the router and see if there's a change.
     
  5. koitsu

    koitsu Network Guru Member

    If nothing else works, I'd suggest doing a thorough NVRAM reset (re: "I did do some silly things, like dirty flash directly from the RT-AC with no nvram wipe") and re-applying settings in the GUI by hand. Stock firmware is not guaranteed to have the same NVRAM variable names or values. Wireless is one of the things that "acts the craziest" in this situation (though in your case, the wireless GUI is at least working partially, but it's also older Shibby).

    Edit: ...unless I misread/misunderstood what you meant?
     
    Last edited: Oct 11, 2018
    Sean B. likes this.
  6. cloneman

    cloneman Addicted to LI Member

    My dirty flash consisted of going from Shibby 1.32 K26RT-AC to Shibby 1.32 K26RT-N without resetting nvram.
     
  7. koitsu

    koitsu Network Guru Member

    Considering that I think RT-AC and RT-N use different wireless drivers, a thorough NVRAM reset might be worthwhile. That one shouldn't be too bad to test -- do a config backup using the GUI (yes, you heard me right!), do the thorough NVRAM erase, let the router reboot, configure it a little bit when it comes up (mainly the 802.11 bits), and see if the 5GHz band starts working. If it does, well then now you know the cause. If it doesn't, then you can restore the previously-backed-up settings without too much worry.

    I swear, the more we deal with NVRAM complexities, the more I realise OpenWRT really got it right by leaving NVRAM almost entirely alone and sticking with text config files.
     
    maurer likes this.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice