WRT54G v7 loses connection daily

Discussion in 'Networking Issues' started by santo, Dec 31, 2006.

  1. santo

    santo LI Guru Member

    I wanted to replace my old pentium based software router (ipcop) with a "real" (wireless) router.
    Therefore I decided to buy a Linksys WRT54G because we use it at our office too without any problems after having replaced the firmware with OpenWRT.

    Unfortunately, the linksys WRT54G I bought seems to have different hardware (v7) making it impossible to replace the firmware with OpenWRT :-(
    So I have to use the default firmware...

    With this default firmware I notice a strange problem with my WRT54G router.
    Every morning the following happens:
    - the laptops can't establish a wireless connection with the router
    - the desktop pc's and servers, which have a fixed ip address, can still ping the router, but can't access the web interface and don't have internet access.

    The only solution is unplugging the router and then plugging it back in.

    I also have a Belkin wireless router (which I used to provide wireless access for my laptops).
    When I use this Belkin as the router for my entire network (instead of the linksys) everything works as expected.
    Unfortunately the firmware has some limitations making it rather useless as a router for me.

    When using the pentium pc with ipcop I don't have any problems either.

    My internet connection is a broadband connection through a motorola cable modem
  2. Toxic

    Toxic Administrator Staff Member

    You may wanto to try the new Beta v7.00.3 that has been released. there are tons of changes on the firmware.

    Linksys, A division of Cisco Systems, Inc.

    Product: WRT54G (EMEA and APAC regions only)

    Classification: Firmware Release History

    Firmware Date: December 4, 2006

    Release Date: December 21, 2006

    Last Firmware Version: 7.00.3 (BETA FIRMWARE)

    General Notes:
    - This firmware is currently in BETA and will be dealt with at such with limited technical support.
    - This firmware is NOT backwards compatible with hardware versions prior to 7.0
    - This firmware is only for usage in EMEA (Europe, Middle East, and Africa) and APAC (Asia-Pacific).
    - Disconnect all wireless clients from the router during the upgrade process. Make sure no wireless clients attempt to associate with the router until the upgrade process is complete.
    - After upgrading to this firmware, Setup Wizard ver. 7 (shipped with the product) can configure the router, but is no longer able to change the language on the web-based/GUI on the router.
    - Channels 12 and 13 are not functional in this version of the firmware.

    Firmware 7.00.3 BETA FIRMWARE
    - Resolves interoperability issue with WAP54G and WRE54G in WPA-PSK mode.
    - Resolves intermittent reboot issue when BitTorrent is running when UPnP is enabled on the router.
    - Resolves wireless data rate performance issues.
    - Resolves issue with router assigns declined IP address to LAN host.
    - Resolves issue with QoS module algorithm.
    - Resolves reboot issue if fragmentation threshold is set to value less than 1500.
    - Resolves issue with wireless MAC filtering configuration GUI.
    - Resolves issue with saving RADIUS passphrase.
    - Resolves display problems in routing policy configuration GUI.
    - Resolves issue of RIP request packets not being sent out after switching to router mode.
    - Resolves issue of logging the same event more than once when log function is enabled.
    - Resolves issue of unexpected clearing of log when user stops and closes traceroute.
    - Resolves issue of not being able to accessing some configuration settings after changing password.
    - Resolves issues with incorrect beacon interval acceptable range and beacon packets not being sent out on some particular settings.
    - Corrects "Port Range Forward" policies validation.
    - Fixes problem of not storing DNS address(es) correctly if static DNS address(es) is/are used.
    - For security purpose, "Clone Your PC's MAC" functionality is no longer available if user accesses router remotely.
    - Resolves issue of displaying incorrect HTTPS certificate message.
    - Fixes problem in QoS configuration validation.
    - Fixes incorrect supported rates in beacon packets when wireless mode is set to 'mixed'.
    - Resolves reboot issue with setting beacon interval to value greater than 5000.
    - Corrects ARP exchange behavior on WAN interface (DHCP mode) after obtaining IP address via DHCP.
    - Corrects PPTP connection behavior when PPTP mode is set to "on-demand" mode.
    - Resolved issue with not being able to set UPnP policy with port number less than 1024.
    - Fixes problem of DMZ feature not functioning properly.
    - Resolves issue with not showing the most up-to-date connection status on WAN interface in MS Windows XP via UPnP.
    - Resolves issue with LAN host intermittently not being able to obtain IP address from router via DHCP when DHCP server is enabled.
    - Resolves issue with IP address assignment via DHCP on some particular devices.
    - Corrects DHCP protocol stack behavior when switching from PPPoE mode to DHCP mode.
    - Corrects "Access Restriction" behavior when system time is not available.
    - Resolves issue of not trying alternative DNS if the preferred DNS does not respond.

    Firmware 7.00.1
    - Initial Release

  3. Mastec

    Mastec Network Guru Member

    If that firmware update doesn't work you may want to consider returning it and getting a WRT54GL
  4. santo

    santo LI Guru Member

    Thanks for the info.
    A lot of bugs seem to be fixed indeed, but this part is worrying me:
    What exactly does that mean ?
    I don't want to brick my router with a beta firmware and then get the answer that it cannot be replaced because I tried to install a beta firmware.
  5. santo

    santo LI Guru Member

    Unfortunately the shop where I bought the WRT54G doesn't sell any other linksys models :-(
    Only the WRT54G and 2 belkin wireless routers
  6. Toxic

    Toxic Administrator Staff Member

    if linksys has released it they have to abide by their word on warranty. I remeber the old BEFSR41 v1 i had. linksys released a firmware that trashed ALL BEFSR41 v1's. they had to replace all of them.

    do you think that they replease Beta firmware so you can brick the router? Beta firmware is Firmware that has past Alpha testing/developement to a stage where it now needs to be tested. however since there are so many fixes they have release new firmware (beta, be it may) but they know the issues have been resloved. what they many not know is what bugs may have crept into the firmware with all these changes.
  7. Mastec

    Mastec Network Guru Member

    Oh man.... Maybe the beta will work. Also, Linksys won't hold you resposible if you brick your router updating with their official firmware. If you brick it using third party then they stop talking to you.
  8. Toxic

    Toxic Administrator Staff Member

    this is my ALL my affilate links for the WRT54G WRT54GS and WRT54GL all point to Amazons WRT54GL. I will not link directly to a brand new G or GS anymore.

    The GL is the rebadged WRT54G v4 which is Linux.
  9. Toxic

    Toxic Administrator Staff Member

    well thats strictly not true. I trashed a WRT54G years ago on DDWRT firmware and they replaced it, it really depends what you tell them:)
  10. Mastec

    Mastec Network Guru Member

    COOL Have to remember that. I was told different by tech support when the wireless quit working on my version 4. The dude asked me if I had run third party firmware and if so Linksys can not help me. I obviously said no... LOL I'm such a liar. HA HA HA HA

    That reminds me... A friend bought a version 6 from Amazon. Flashed it and bricked the router. Took it to Walmart and asked for a refund. Not without a receipt but did offer an exchange instead. He was lucky enough they had a version 4 on the shelf. Talk about luck HA HA HA
  11. santo

    santo LI Guru Member

    I went back to the store with my linksys WRT54G and after a week of testing they told me - of course - they haven't noticed any lockups or other similar problems

    Eventually I could convince them to take the router back and replace it with a WRT54GL (it had to be ordered, as they don't sell it), which I got yesterday.

    So let's hope this one doesn't suffer the same problems...

    Thanks for the help guys.
  12. mahsrow

    mahsrow Guest

    Found a solution to my problem

    I had the exact same problem and I traced it back to the MAC addresses of the routers - THEY WERE THE SAME! From a command prompt run "arp -a" and look at the hardware addresses associated with the IP's for your routers. If they are the same then you'll need to do some "MAC Cloning" from the routers http interface. BTW - my hardware are both WRT54G's but I read somewhere that Belkin licenses hardware from other vendors, maybe even Cisco. At any rate, the problem didn't manifest until I flashed to the latest firmware (v1.02.0) so I think that maybe the firmware reset the hardware addresses installed with the shipping firmware - at least the stickers on the boxes indicated that the original MAC's were different than what the new firmware reported. Comments?

    PS - Linksys.com tech support can bite me. I had several web chats with them which kept getting disconnected because of my problem. Each time they claimed they couldn't find a record of the previous chats (even though they emailed the transcripts to me) and made me start the troubleshooting process over. After 4 chats and 6 hours they finally decided to send me a new router. I was told "Kristelle M. (10339): Please give me five minutes to process an RMA. After five minutes, a Reference number of this session will be sent to your e-mail account. Once you have the reference number, please go to this website; https://ssl.linksys.com/rma1.asp, and fill out the Warranty Return Form. Your reference number is the value that you need to input on the Case ID field on the Warranty Return Form." Of course the email never arrived. That is what prompted me to figure out the issue myself so I guess I *might* owe them some thanks. Nah
  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