Tomato hiccups up randomly and frequently, different vers & hardware, same prob. Details inside.

Discussion in 'Tomato Firmware' started by adster2000, Mar 23, 2010.

  1. adster2000

    adster2000 Network Guru Member

    Ok, I foresee this post being fairly long, so I'm going to get right to it.

    I currently use Road Runner service with a 15/1.5 bandwidth limit. I have the cable modem connected to a WRT54G-TM currently running the new Tomato with Kernel 2.6 Beta 07 from teddy_bear. That is connected through WDS to another WRT54G running Tomato on the other side of the apartment. I also have an Apple Time Capsule connected to the original WRT54G-TM broadcasting a 5gz N-only signal.

    A few times a day, visiting websites becomes unresponsive. I can connect to them "Website found, waiting for reply..." but no content loads. During this time, I am unable to connect to Tomato GUI on the main router. I can, however, connect to Tomato on the 2nd WDS router.

    Things I have done:
    -Use OpenDNS as my DNS servers entered into Tomato.
    -First, I had Time Warner come out and check things out. They tested the line, said that was fine but gave me a brand new cable modem (which seems much faster BTW) but I still get these hiccups.
    -I originally had an Asus WL-520GU router running Tomato 1.25 with the same issue. I removed that and replaced it with the WRT54G-TM, cleared NVram and inputted my settings manually.

    I'm getting fed up, and I have a feeling that Tomato is involved, especially since I cannot connect to the web interface while these "hiccups" are happening. Does anyone have any idea what might be causing this?
     
  2. rhester72

    rhester72 Network Guru Member

    Can we get a snapshot of the relevant entries from /var/log/messages during an event like this?

    Rodney
     
  3. adster2000

    adster2000 Network Guru Member

    Sure! However there isn't anything relevant in the syslog. Here's my log for the last 2 hours (where it has happened a few times)

    Code:
    Mar 23 10:00:01 wrt-54g-tm syslog.info root: -- MARK --
    Mar 23 10:08:08 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:08:08 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 10:10:16 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:10:16 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 10:12:58 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:12:58 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 10:34:29 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:34:29 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 10:47:13 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:47:13 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 10:58:38 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.126 00:26:08:96:d1:1b 
    Mar 23 10:58:38 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.126 00:26:08:96:d1:1b Speed-Demon
    Mar 23 11:00:01 wrt-54g-tm syslog.info root: -- MARK --
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPDISCOVER(br0) 00:24:e4:00:13:1e 
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPOFFER(br0) 192.168.1.109 00:24:e4:00:13:1e 
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPDISCOVER(br0) 00:24:e4:00:13:1e 
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPOFFER(br0) 192.168.1.109 00:24:e4:00:13:1e 
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPREQUEST(br0) 192.168.1.109 00:24:e4:00:13:1e 
    Mar 23 11:43:52 wrt-54g-tm daemon.info dnsmasq-dhcp[1102]: DHCPACK(br0) 192.168.1.109 00:24:e4:00:13:1e 
    Mar 23 12:00:01 wrt-54g-tm syslog.info root: -- MARK --
    Those 2 devices asking for DHCP are cell phones in the house. Other then that, no error messages :-/
     
  4. rhester72

    rhester72 Network Guru Member

    Erk...this is going to be fun [sarcasm]. I'd recommend cronning VIT with a period less than the outage duration to see if we can get some decent diagnostic data when it's actually happening.

    Rodney
     
  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