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

E3000 with Tomato (toastman 1.28.7465) dropping WAN packets

Discussion in 'Tomato Firmware' started by Morac, Apr 9, 2011.

  1. Morac

    Morac Network Guru Member

    I installed the Toastman build on my new E3000 and it seemed to be working but at some point the WAN interface appeared to go down. Nothing would go in or out over it. I rebooted and that brought it back up and I started sending 1472 byte pings to my gateway as fast as I could send them out, a bunch dropped. The drop percentage wasn't that high, but it was there.

    I swapped my WRT54GL back in running the stock Tomato 1.28 and sent over 4000 pings without dropping any.
    Swapped my E3000 back in and it dropped a packet after sending 600. So the E3000 isn't routing as well.

    The E3000 with Toastman doesn't seem particularly stable. Is there something else I can try?

    Edit:

    I did a NVRAM thorough reset and that seemed to fix things, but considering I juts set things up I have no idea why. I thought maybe it was the CPU setting since the router defaults to an unknown frequency, but I set it to 480 and rebooted and it still seems okay. I'm going to try and track down what exactly is causing the issue.

    Edit 2:

    I manually set everything up again (left a few unnecessary things out like wireless fillters for old devices and QOS settings I don't use (since I don't use QOS) and everything seems okay now. I'm not sure what was wrong earlier. I'm going to keep an eye on it though. I can't have a router dropping the WAN port periodically since I use VOIP (that's actually how I originally saw the problem when the phone stopped working).

    Edit 3:

    I wonder if it had to do with the fact that I unplugged the E3000. Whenever I do that the listed CPU seems to change. When I first installed it showed 480 MHz in the log even after a few reboots, but after unplugging the router and plugging it back in, that changed to 133 Mhz. It was at that point I changed it to 480 MHz in the misc settings and then things went berserk. This time I did a NVRAM reset, changed it to 480 MHz and reboot, but I have yet to unplug it and plug it back in. I have a feeling that might cause it to fail, though I don't know why it would.
     
  2. TexasFlood

    TexasFlood Network Guru Member

    I haven't tried to change the CPU clock speed yet and am not seeing any dropped packets. Now I'm thinking that I shouldn't try setting a clock speed, at least just yet :smile:.
     
  3. Toastman

    Toastman Super Moderator Staff Member Member

    You should set a clock speed, which will set an nvram variable so that in future the router will boot at your selected speed. Until you do so, it will presumably run at whatever the cfe set it to when it began to boot. Perhaps this is the problem.

    I don't know if the 3000 has something odd about it's hardware, but scanning the forums shows that the majority of the recent reports of problems, in Teddy Bear, Victek, and Toastman builds, seem to be about the E3000. I don't see any problems on any of my RT-N16's.

    I've looked through the nvram.c defaults files for routers going back to Tomato 1.23 - and as far as I can see, this nvram variable was never set there. Presumably relying on the router to use sensible (stock) defaults, unless it's set somewhere else.

    Perhaps the E3000 doesn't do that? Maybe something should be set.

    Setting the CPU clock speed sets an nvram variable. The fact that this is not being successfully read on startup even after you set it to 480 may point to corruption of nvram, or perhaps it is not being saved.

    It is possible to corrupt nvram very easily by unplugging the router, plugging it back in, then just as it begins to boot, unplugging again. This happens during the course of a power failure quite often here, which is why all my routers run on a UPS.

    Additional note - 12 June 2011

    I remembered this thread and came back to check on it. I have an E3000 now and have flashed with the same firmware and been experimenting. To me, it appears unconditionally stable. I have plugged and unplugged, entered every clock frequency selection, erased nvram, and rebooted and pulled out plugs some more. I can't make it do anything unusual. Actually, I'm quite impressed with the E3000 now. Even if it does look like a flying saucer!
     
  4. TexasFlood

    TexasFlood Network Guru Member

    OK, set clkfreq to 480MHz and rebooted. CPU speed is reported as 480MHz, did it through the Advanced->Miscellaneous GUI dropdown, no dropped packets in the first test after reboot.
     

    Attached Files:

Share This Page