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

WAG54G (annex A) reboot problems

Discussion in 'Other Linksys Equipment' started by rijko, Jun 25, 2004.

  1. rijko

    rijko Network Guru Member

    Hi all,

    I have a WAG54G annex A with the latest firmware 1.0.1.7
    Lately i am experiencing troubles.

    It seems a portscan is all it takes to crash the router.
    In other forums this behaviour is confirmed.
    It reboots - and frequently fails to bring up the WLAN...
    Sometimes it reboots 3 or 4 times...
    Most of the time i need to power down&up the darn thing to get it to work properly again.
    The router sometimes reports : "Ceiling for number of connections reached, dropping packet"
    and then crashes&reboots.
    Is anyone else experiencing this behaviour ?
    The worst part of it is.... the portscan also crashes the router if scanned from the outside !! Kind of DoS :))

    Regards,
    Rijk
     
  2. SloppyFredFloppy

    SloppyFredFloppy Network Guru Member

    Rijk,

    Had some reboot problems with my set as well. Don't know if a portscan was the cause of it, but I do know that a hard reset (press the reset button at the back of the set for more than 10 seconds) was the cure.
    Re-entered all the settings manually, and the set has been stable since.

    I am running firmware 1.02.3. Restoring the settings did not work. I had to re-enter all of it. Apparently my problem is in one of the settings that is included in the back-up I made.

    good luck!
    Fred
     
  3. rijko

    rijko Network Guru Member

    I have tried that... without any luck...
    If this behaviour persists i will ask for a replacement

    Thanks for the tip though !

    Best regards,
    Rijk
     
  4. yonnage

    yonnage Network Guru Member

    1.02.3 cures rebooting

    according to Linksys, the latest beta 1.02.3 will stop the reboot issue. but you must do a full factory reset, and manually enter all settings, a restore will not resolve it
     

Share This Page