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

reboot router ever 36-48 hours

Discussion in 'DD-WRT Firmware' started by eobiont, Mar 18, 2006.

  1. eobiont

    eobiont Network Guru Member

    I am having a problem where I will lose internet conectivity ecery 36 or so hours. I have to cycle power on the wtr54G and then it functions normally.

    I have the "mini" version of DD-WRT, the christmas version installed.

    Is this par for the course, or is there something I might be doing wrong?

    When it goes down, clients are unable to connect to the outside or LAN, and attempts to renew IP addresses fail.
     
  2. dvaskelis

    dvaskelis Network Guru Member

    I have not run that version of DD-WRT.

    But that type of problem every couple of days is why I switched to HyperWRT. Lost a few nifty features, gained a few others, but HyperWRT Thibor is rock solid. I only have to reboot the router when I load an update from Thibor!
     
  3. myersw

    myersw Network Guru Member

    I also had issues with DD-WRT losing Internet connections and having to reboot. I tried using up thru v23 middle of January. Decided there had to be a more solid firmware load out there. Decided to give Hyperwrt a try. Loaded Hyperwrt + Thibor 13 and had no issues. Am now running Thibor 14 on my wrt54gs without any issues, just works. May have lost some feature/function BUT gained a solid router in return, I'll take reliability over feature/function everytime.

    I left dd-wrt when even dhcp wasn't solid. That was the end for me.
    --bill
     
  4. jgutz20

    jgutz20 Network Guru Member

    i just recently switched to DD-WRT, my first alternative from Sveasoft (satori, alchemy and talisman) and i cant say i've had any problems although i dont use the DHCP function.
     
  5. Sundance

    Sundance Network Guru Member

    Even worse when you use Torrent or Donkey

    Hello,
    I'm using DD-WRT 23 and experiencing the same problem.

    It is even worse when you are using a connection extensive protocol (like torrent or donkey). When doing such a thing after five or six hours WRT54G even begins losing ping packages in the subnet and the gui connection.

    Not so sure but did not have this reboot issue in V22.

    I love DD-WRT but if this issue can not be solved will try others.
     
  6. roclimber

    roclimber Guest

    well i am not sure if you have looked, i just downloaded this firmware ( DD-WRT ) and noticing this problem.

    i think what happened is the lease time of the IP address. it's default to maximum of 5746 minutes which equates to about 3 days.

    what you can do is open a dos window, and type in "ipconfig /release" , then "ipconfig /renew", that will give you a new IP address without rebooting it.

    give that a try and see.

    hope that helps.
     
  7. G_Styles

    G_Styles Network Guru Member

    There is an issue with DD-WRT v23 final. This issue has been addressed in the v23 SP1 beta. If you like the feature set of DD-WRT, try the SP1 beta versions, they are much more solid, and do not have the disconnect issue.
     
  8. fizze

    fizze Network Guru Member

    why dont you just turn on the cron daemon, and set it to reboot automatically once a day at a time you wont really need the WRT.

    I set mine up to reboot at 7am daily, and never had problems.


    before that, with alchemy or whatever I had to reset every 3-4 days.
     
  9. mw1001

    mw1001 Network Guru Member

    Becouse my ISP will change my IP every time I reconnect... So, if I do such thing, I can forget good rates with p2p applications.

    Any way, it's impossible to run p2p applications with this firmware. I let it @ my wrt about 2 hours to experiment problems. Will try again in the future, to se if the incomming versions are more stable, becouse the features looks really great!

    Regards,
    mw1001.
     
  10. bytes2000

    bytes2000 Network Guru Member

    are you using AP watchdog ?
    if yes disable it.

    do you have enough netfilter ports ?
    -> in administration > setup ports to 4096 and timeout to something like 90 or 120.
     

Share This Page