Discussion in 'General Discussion' started by Anonymous, Nov 15, 2005.

  1. Anonymous

    Anonymous Guest

    I have one of these routers, from reading other posts it appears that this router is on fact a poor excuse for one... but has anybody managed to make one work for any legth of time?

    Setup: 3 Windows XP computers (2 wireless), WPA-PSK encryption, router connected to cable modem via ethernet.
    Router is running version 1.56 firmware.

    Problem: Router behaves as though it is blocked, it can be connected one minute, the next the connection is gone (both wired and wireless). It isn't the modem, it's definately the router.
    All the lights are still on, the internet light still flashes continously, but as far as the computers are concerned the router is gone. No ping, no nothing.

    The only cure is to turn it off and on again. After this it works perfectly... for a while. A day or so later it all goes down again. Never happens at the same time of the day or when any particular site/activity is happening.

    Only thing I can think of is that:
    a) the router firmware has become corrupted somehow (one of the computers has been doing a lot of BitTorrent downloading and god knows what else)
    b) traffic is increasing somehow to the point that it is overwhelming the routers ability to process it
    c) the router is complete crap

    Would a firmware update be likely to help, or is continuing to work with this router a waste of time?

  2. howardp6

    howardp6 Network Guru Member

    This is the change log for the WRK54G v1.0:

    Linksys- A Division of Cisco System, Inc.

    Firmware Date : May 24, 2004
    Current Firmware : Version 1.55.02
    Product PartNo : WRK54G

    Ver #. Date Description
    1.55.02 May 24, 2004 1. Modified the Help files
    2. Added L2TP Internet connection type
    3. Added CTS Protection Mode item in wireless
    advance setup page
    4. Updated wireless libraries
    5. Fixed Heart Beat connection problem
    6. Fixed CGI attack issue
    7. Fixed DHCP security issue
    8. Fix NAT_T on a VPN pass-through connection
    9. Added Filter Ident(port 113) option
    10. Fixed with some PPPoE connections
    11. Modified some text.

    1.52 Feb 05,2004 First Official release


    No where does it stat there a fix for large file trransfers, which appeared in the WRT54G series of routers. Try limiting the number of Torrents. if possible.
  3. Anonymous

    Anonymous Guest

    Thanks, I have spoken to Linksys help who basically told me to step the MTU down to 1300. I tried 1400 but it still went belly up after a day.
    As it kills both the wired and wireless connections completely, a ping won't even get to the router, if it happens again the router will be going back I think.

    I looked at the traffic log, and everything appears to be coming in to port 10,000. Is this right? seems a bit wierd.
  4. howardp6

    howardp6 Network Guru Member

    Sorry for the typos. Is the computer with Btorrent opening port 10000? Port 10000 is associated with remote adminstration for LINUX based systems. In the log can you determine the IP Address that is generating the traffic.
  5. Anonymous

    Anonymous Guest

    The computer with Bitorrent isn't running at the moment, and it's the incoming log which is showing Port 10000 as the destination.
    And there are multiple IPs on the list, with the same ones sometimes appearing several times.

    IP Destination Port 10000 10000 10000 10000 10000 10000 10000 10000 10000 10000 10000 10000 10000 10000 1025 10000 10000 10000 10000 10000 10000

    I guess nothing is getting through... my firewall is showing nothing and no spyware/viruses exists on my system (which is the only one connected right now).
  6. howardp6

    howardp6 Network Guru Member

    Go to http://www.dslreports.com/whois and copy the Addresses in any you can find out where the source is. Do you have a Vonage internet phone service that is another thing that uses port 10000.
  7. Anonymous

    Anonymous Guest

    Well, I checked out most of them, a lot of RIPE (Amsterdam) and various other networks.
    Since nothing is using that port and nothing seems to be getting through I guess the NAT is ignoring it, so I don't think it is the cause of the routers ills. :(

    It has been quiet the last few days though, no problems, but if it happens again within a week it's going back.
    I'm sure it shouldn't be this much hassle.
  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