Re: Occasional Network/DHCP weirdness
On Wednesday 07 November 2001 22:55, Raghavendra Bhat wrote:
> [Wed, Nov 07, 2001 at 07:50:58PM -0500] David P James :
> > our ISP uses DHCP that's what the server set to use and most of the
> > time it works just fine (It's set up with dhcp-client). But every now
> > and then it loses the connection altogether
>
> Is the server a 'Potato' one ? I have observed a similar issue at one
> location, with the dhcp-client logging these messages inside
> /var/log/syslog. System is a 'Potato' machine with Adrian Bunk-ed
> packages and 2.4.x kernel.
Yes, it is a potato box - I can't recall installing anything on it from
woody. Would compiling a 2.4.x kernel and/or upgrading to woody help? Or
perhaps just upgrading dhcp-client?
>
> -----<snip>--------
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6
> dhclient-2.2.x: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
> dhclient-2.2.x: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7
> dhclient-2.2.x: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 10
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 17
> dhclient-2.2.x: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 11
> dhclient-2.2.x: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
> dhclient-2.2.x: DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 10
> dhclient-2.2.x: No DHCPOFFERS received.
> dhclient-2.2.x: No working leases in persistent database - sleeping.
> -----<snip>-------
>
> This is repeated at regular intervals.
I've got the same sort of messages. It's also one enormous file as it goes
back over a month in time.
>
> > This problem seems to have something to do with leases
>
> I have observed another issue, this DHCP DISCOVERY is not that
> persistent when there is activity on the server, by way of users' in the
> internal LAN accessing the Web.
Interesting... for me it has gone down in the middle of the night, during the
afternoon and during the evening. It doesn't seem to be too particular about
when it quits.
Here's some of the more strange occurances with ping (I have 'queensu' mapped
to the IP in my hosts.conf file for ease of use and for testing in case we
lose DNS):
gateway:/home/dpjames# ping queensu
PING queensu (130.15.126.54): 56 data bytes
ping: sendto: Operation not permitted
ping: wrote queensu 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote queensu 64 chars, ret=-1
--
David P. James
Third Year Economics
Queen's University,
Kingston, Ontario
http://members.home.com/dpjames/
The bureaucratic mentality is the only constant in the universe.
-Dr. Leonard McCoy, Star Trek IV
Reply to: