WRT54G v2.2 keeps dropping connection

Discussion in 'HyperWRT Firmware' started by dolly_oops, Aug 17, 2006.

  1. dolly_oops

    dolly_oops Network Guru Member

    I've been having problems with my WRT54G v2.2 when there is a lot of wireless traffic going on.

    When I first got my router, there was a problem transferring a lot of data over the wireless connection - the connection would drop after a few minutes (giving a "The specified network name cannot be found" error message). I remember there was a lot of people complaining about the same issue - this was fixed eventually by Linksys (I think it was firmware 4.00.7).

    However, I'm now running Thibor 15c, and I think I'm having the same problem occurring. It used to be that when I either did large file transfers, or used VNC for a while, the connection would drop (and then re-establish itself), and it seems to be happening again.

    I've tried disabling a few things to see if that helps - I've disabled QoS controls, I've turned off encryption, but it is still running into problems.

    Has anyone else run into this? I know that when I upgraded to the fixed Linksys firmware, I couldn't reproduce the problem, and I know HyperWRT is meant to be based on the most recent Linksys firmware, so I wouldn't have thought for it to be a problem.

    One other thing - according to my router, it's running "Firmware Version: v4.71.1, Hyperwrt 2.1b1 + Thibor15c", but according to this page, v4.30.5 is the latest version - so is that page out of date, or am I missing something?
  2. Thibor

    Thibor Super Moderator Staff Member Member

    set "nvram set cpu_overdrive=1;nvram commit" on the command line and then reboot.
  3. dolly_oops

    dolly_oops Network Guru Member

    That seems to have done the trick, thanks. Any reason why this isn't enabled by default?
  4. Thibor

    Thibor Super Moderator Staff Member Member

    yes, it's because the firmware is based on the GS codebase, and i made it so that it works for the G as well. this fix is well documented both here and at the Hyperwrt forums mate. this issue only affected the G's and not their equivalent GS models i believe.
  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