Sometimes Losing Connection WHR-HP-G54 / FIOS 20/20

Discussion in 'Tomato Firmware' started by The Doctor, Nov 12, 2008.

  1. The Doctor

    The Doctor LI Guru Member

    Hi, this is my first post to this forum, please try not to cause too much trauma.

    I have been running my Buffalo router with Tomato version 1.09 on it for about two years, it was hooked up to Comcast through a cable modem for most of that time, and I never had a single problem with it in two years. In fact, it has been a full year since the router was restarted.

    Recently, Verizon's FiOS service became available in my area, coincidentally, this just happened to be when Comcast started enforcing their usage caps. Well, I'm a very heavy user of the ed2k network, and the caps did not appeal much to me. Plus, 2 Mb upstream sucks when I can get 20 with Verizon. Bundled with my telephone service, the FiOS was actually cheaper:) Anyway, it was pretty much a no-brainer, I got the FiOS package with 20 Mb both directions. I must say, the service is awesome, I suggest you get it if it's available in your area. Okay, enough history, let me start on the problem.

    Well, Verizon gives you a router which are FiOS service, which usually receives its Internet connection through co-ax. However, you can also have them turn on an ethernet port on their ONT, in which case you can use a router which does not require a coaxial input. As the router they supply is known to have great deal of trouble with large numbers of simultaneous connections, I went with the ethernet option, which pretty much allows you to use any router you want.

    As I already had a Buffalo WHR-HP-G54 with tomato version 1.09 installed on it, and I really liked the reliability and features that combination gave, I decided to use that one with the FiOS and see if it could handle the bandwidth. Upon connecting it to the Verizon service, it obtains an IP address (through DHCP) and got me online in under a minute. Several extended tests showed that the router is in fact capable of handling the connection, although it CPU sometimes exceeds 100% usage if you are pushing the connections limit in both directions at once. For several weeks, everything was 100% perfect...

    Then came my first sign of trouble. I came out one morning and went to check my usual websites while my coffee was brewing, and found out that I was no longer connected. Logging into the router and checking the bandwidth graph for the last 24 hours, I found out that all Data quit flowing about 2:30 AM. Immediately before that, the connection was under fairly light load, only about 500 kB/S or so. Going back to the overview screen, the router indicated its status was connected, but the remaining lease time was listed as 0 days, 00:00:00. I clicked on the release button, and then the renew button. Within 30 seconds, I had a new IP address, everything was fine again. BTW, the normal lease with Verizon's FiOS service is two hours.

    Everything was going good for a few more weeks, then earlier today I was viewing some videos on YouTube. I clicked on a video, it started playing, but only about a quarter of it came down before it stopped. Refreshing did not work, I soon found that I once again had no Internet connection. A quick trip into the router showed the same thing as before, it said it was connected, but there was zero time remaining on the lease. I didn't even click release this time, just click the renew button. Again, within 30 seconds, I was back online. This time I had kept my original IP address.

    Anybody got a clue as to why it will sometime not renew its lease? It is usually able to do so dozens of times before failure, why not every time? This is new behavior, when it was running under Comcast this never happened. I am kind of guessing that perhaps sometimes Verizon's DHCP server does not respond, and the router does not ask again. It seems like one account gets to zero, it should automatically keep requesting a lease renewal until it gets one, is it supposed to do that and for some reason it is failing? Anybody got a suggestion on what I can do to fix this problem?

    I have considered just upgrading to the latest version of Tomato, but version 1.09 has been incredibly reliable, a year of uptime is pretty impressive. I have seen some complaints on here about the reliability of version 1.21, which makes me a bit leery. I would appreciate any suggestions you folks can offer, while I have only signed up a few minutes ago, I have been reading these forums for well over a year, and I have observed that there are some very smart people on them.

    Thank you
  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