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

Satori-4.0 v2.07.1.7sv crashing after 24 hrs+ uptime

Discussion in 'Sveasoft Firmware' started by MikeBomb, Aug 30, 2004.

  1. MikeBomb

    MikeBomb Network Guru Member

    I have been running this firmware on a WRT54G v. 2 for about a week and have have had to pull the plug on the router and restart it several times. I leave the router running 24/7 and it has always been running for more than a day when it crashes.

    When the crash occurs, the WLAN and port lights blink together over and over and the router cannot be reached from either a wired or wireless PC. When I pull the plug and reboot everything seems okay again.

    I have not tried using the resetbutton; I find that its recessed nature makes it hard to use, plus I would hate to hold it too long and lose my configuration setup.

    I have a PC, a Sipura 2000, and a Linksys WPS54GU2 Print Server on wired, static DHCP connections to the router, plus 2 notebook PCs that occasionally connect wirelessly using WPA-PSK (AES), MAC Filter (permit known only), and regular DHCP.

    I used to use WifiBox's firmware on a WRT54G v. 1.0 box; then the box and a WPS54GU2 Print Server fried each other and I had to get them both replaced under warranty. Now I am afraid to use WifiBox's current firmware. (I am pretty sure it was a murder-suicide but I do not know which one committed the crimes. The other possibility is that they were both simultaneous victims of something else.)

    The only reason I am not using the latest official firmware is that I need static DHCP for my Sipura 2000 (voip adapter) and for port forwarding to the wired PC. With WifiBox out of the running, I tried the Satori firmware. If it keeps crashing, I don't know what I am going to do.

    Has anyone any help or suggestions for me?
  2. Anonymous

    Anonymous Guest

    There were some DHCP server bugs in the older Sveasoft firmware that have been fixed in the Alchemy versions.
  3. Toxic

    Toxic Administrator Staff Member

    try setting the DHCP time to 1440 and not 0 see if that helps
  4. MikeBomb

    MikeBomb Network Guru Member

    Okay, I am. I will let you know if it helps.

Share This Page