E2500 Random Crash/Reboot Debug Help Needed

Discussion in 'Tomato Firmware' started by Pearl, May 8, 2014.

  1. Pearl

    Pearl Network Newbie Member

    I have a Linksys E2500 dual band wireless N router.
    I live in a busy apartment building with a lot of wifi overcrowding on the 2.4ghz band. The 5ghz band is much better but unfortunately some of my devices do not support it.

    I wanted to flash to DD-WRT but after reading it didn't support 5ghz, and shibby tomato does, I decided to flash it with latest shibby tomato: tomato-E2500-NVRAM60K-1.28.RT-N5x-MIPSR2-117-Max. I pretty much left all default config untouched, other than configuring my wifi 2.4ghz AP and 5ghz AP. There are no ethernet connections to the router, only wireless.

    Everything is working fine and my speed on 2.4ghz is a lot faster than stock firmware. 5ghz is also working fine. However there is one problem, which is after some extended period of WIFI activity (from any of the connected devices), the router will crash and/or reboot. I know it crashes / reboots because when it comes back, I can see the uptime being reset. It doesn't seem to isolate to any one device, but usually after about 2-3 hours of steady streaming or other usage, all devices against the router will lose wireless connection and then router will reboot/restart.

    I can't see anything in the log that's out of the ordinary, but I also can't seem to retrieve logs prior to the reboot / crash, as when I go under log view, I only see the log since it has been rebooted. My question is how do I go about using administration/debugging or administration/logging to help me isolate the problem? I can SSH into the router just fine, but I am not entirely sure how to use the debugging features.

    Anyone else have this problem with E2500 and tomato?
    I set my 2.4ghz and 5ghz both to 20mhz channel width. And they both have WPA2 on them. And just as I am writing this thread, it rebooted :(

    Any help greatly appreciated.
  2. koitsu

    koitsu Network Guru Member

    Start by providing a full list of all the configuration adjustments you change from stock defaults. And when I say all, I mean all. We want to know your entire configuration -- every single thing you change. If you need an example of what to provide (e.g. how verbose), here you go. We do not need your wireless password, of course, but everything else matters.
  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