The Road Runner IP leases are 2 hours. I am not sure of the length of your
lease, but probably is at least that long or longer. The standard lease on
a DHCP server is 72 hours. You may want to connect one of your boxes
directly to the DSL line (as a DSL client) to rule out whether or not it is
your router. The line itself may be flaking. Any new
neighbors/construction in the area? Some thing may have disrupted the DSL
line. Since I have Road Runner... sometimes, when my RR is flaking, my
cable picture will be poor, course' this does not help you. Does your DSL
modem have any diagnostic lights? My cable modem, when flaking, will
sometimes have a blinking "cable light"
Pete
----- Original Message -----
From: "Paul M Foster" <paulf@quillandmouse.com>
To: "SLUG List" <slug@nks.net>
Sent: Wednesday, May 15, 2002 11:59 PM
Subject: [SLUG] More Odd Firewall Problems
> I'm using a coyote firewall on a Verizon DSL line that I haven't touched
> in months. But it's acting a little squirrelly. The "connection" won't
> stay up for any length of time. I test it by pinging known sites which
> will respond to pings. When the connection falters (on the order of
> minutes between failures), I can kill the dhcpcd daemon, and reissue the
> dhcpcd command (/sbin/dhcpcd -d eth1) and it will respond with an IP.
> Moreover, it's the same IP every time (I have dynamic IP). Then the
> connection will inexplicably go down after a few minutes. And if I
> repeat the above, I'm connected again. I thought maybe it was a lease
> timeout problem, so I issued /sbin/dhcpcd -l 36000 eth1, but the
> connection went down after a few minutes anyway.
>
> Anyone have a clue why this type of thing would happen (_before_ I
> contact the retards at Verizon)?
>
> Paul
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:41:27 EDT