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

Hyperwrt+thibor 13d - does not auto connect to dsl

Discussion in 'HyperWRT Firmware' started by myersw, Feb 13, 2006.

  1. myersw

    myersw Network Guru Member

    Upgraded from 13c to 13d of Hyperwrt+thibor. Great work by the way, Thibor. Noticed after the upgrade that the wrt54gs v4 did not reconnect to the dsl network as it normally does after configuration. Didn't think a lot about it, but have tested and find that I always have to go to the status page and select connect to get a connection to the internet. I did a nvram reset before the configuration as usual.

    Configuration I use is this. The wrt54gs is always powered on. The PC and the dsl modem are powered off at nite. Have always run this way and this is the first time I have experienced this problem, with either the official Linksys firmware, Hyperwrt+thibor, as well as other 3rd party. I know I could just leave the modem on, I just have never had to before.
    --bill
     
  2. myersw

    myersw Network Guru Member

    Forgot to state the config for dsl is set for keep alive poll every 30 sec. The default.
     
  3. Thibor

    Thibor Super Moderator Staff Member Member

    i have exactly the same config as you and have no issues here. try resetting to defaults and reconfiguring
     
  4. myersw

    myersw Network Guru Member

    Thibor, thanks for the reply and the great software. I'll do a complete reset and give it another try. Was suprised when I had the issue. Will post with update when I know more.

    Just a fyi, I used to use dd-wrt but that has not been very stable of late. Yours on the other hand is stable and "just works".
    --bill
     
  5. mmisnan

    mmisnan Network Guru Member

    If you were on DD-WRT and just moved to HyperWRT, you may want to clear your NVRAM. Go to Administration, diagnostic and there is an option to clear NVRAM there. I had problem with my static DHCP setup eventhough I did the 20 seconds reset before when first moving from DD-WRT to HyperWRT .. clearing the NVRAM fixed the problem.
     
  6. myersw

    myersw Network Guru Member

    mmisnan, Thanks for the response. I have been using Hyperwrt+thibor 3c.
    I am well aware of the need to reset nvram especially when going from one firmware to another. I will give it a go this eve. Probably do another firmware upgrade to 3d, just in case something didn't go quite right. Do a nvram reset, and a 30 sec reset of the reset button. Between those it should be cleaned out! I'll then do a new config. No I don't copy the config and just reapply. Good way to get a problem back.

    I always do over kill. I do:
    reset to factory defaults and reset nvram before the upgrade, even with in the same family such as Hyperwrt. Got bit by that one with dd-wrt. Then just to be sure I do the same thing again after the upgrade. Doing this has always worked for me.

    Before following this procedure, I bricked a WRT54G v1.1 but got it back again with the 15-16 pin short. Would not answer to 192.168.1.1. until then.
     
  7. myersw

    myersw Network Guru Member

    Thibor, I reset nvram and factory defaults. Reinstalled 13d. Again reset nvram and just for good measure, held the reset for 30+ sec. Now, after reconfig, seems to be working as expected. Does seem to take a little longer to get connected for some reason. Real test will be with it turned off over nite then powered on. If the wife can access her email in the morning life will be good.

    Test was this. Turn off PC. Turn off power to PC and dsl modem. Turn power back on after waiting more then 1 minute, just to make sure went thru one 30 sec poll of the dsl network with the modem off, and then powered the PC back on. Checked the status screen of the 54gs and shows connected and can access the Internet.

    Thanks for a great firmware package.
    ---bill :cheer:
     
  8. myersw

    myersw Network Guru Member

    Thibor, update. Left off as usually last nite. Connected fine this am. Don't know what is different, but works now.
    Thanks again.
    --bill
     

Share This Page