Re: prevent dhclient from exting

To: debian-user@lists.debian.org
Subject: Re: prevent dhclient from exting
From: Arjen Verweij <a.verweij@student.tudelft.nl>
Date: Wed, 19 Oct 2005 11:12:53 +0200
Message-id: <[🔎] 200510191112.53616.a.verweij@student.tudelft.nl>
In-reply-to: <[🔎] 20051017145903.GH5235@a85-156-196-68.elisa-laajakaista.fi>
References: <[🔎] 43535621.60906@student.tudelft.nl> <[🔎] 4353A2A3.6010409@student.tudelft.nl> <[🔎] 20051017145903.GH5235@a85-156-196-68.elisa-laajakaista.fi>
Well Simo, thank you very much. Installing dhcp3-client was the solution.

Now my dhclient sleeps when it can't obtain an address.

Regards,

Arjen


Oct 19 00:21:26 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 
port 67 interval 11
Oct 19 00:21:37 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 
port 67 interval 15
Oct 19 00:21:37 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed out
Oct 19 00:21:37 localhost kernel: eth1: Tx timed out, cable problem? TSR=0x0, 
ISR=0x0, t=11084.
Oct 19 00:21:52 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 
port 67 interval 14
Oct 19 00:22:06 localhost dhclient: No DHCPOFFERS received.
Oct 19 00:22:06 localhost dhclient: No working leases in persistent database - 
sleeping.

On Monday 17 October 2005 16:59, Simo Kauppi wrote:
> On Mon, Oct 17, 2005 at 03:09:55PM +0200, Arjen Verweij wrote:
> > Well, I am at a loss then. This is my /etc/network/interfaces:
> >
> > sphere@sluis:~$ more /etc/network/interfaces
> > # This file describes the network interfaces available on your system
> > # and how to activate them. For more information, see interfaces(5).
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > auto eth1
> > iface eth1 inet dhcp
> >
> > auto eth0
> > iface eth0 inet static
> >        address 192.168.1.1
> >        netmask 255.255.255.0
> >        network 192.168.1.0
> >        broadcast 192.168.1.255
>
> Yes, that looks just like mine.
>
> > Seems pretty standard. It's really beyond me why your dhclient won't
> > exit. It is written in the manual that the retry statement governs a
> > standard interval of 5 minutens even if there are no DHCP offerings. I
> > can't find any reason in syslog why it would exit. See below for a
> > syslog snippet. I suppose my dhclient is run from ifup as well? This is
> > what I have installed dhcp-wise:
> > sphere@sluis:~$ dpkg -l | grep dhcp
> > rc  dhcp           2.0pl5-19.1    DHCP server for automatic IP address
> > assignm
> > ii  dhcp-client    2.0pl5-19.1    DHCP Client
> > ii  dhcp3-common   3.0.1-2        Common files used by all the dhcp3*
> > packages
> > ii  dhcp3-server   3.0.1-2        DHCP server for automatic IP address
> > assignm
> >
> > Regards,
> >
> > Arjen
>
> The only difference would be the dhclient version. I have
> i dhcp3-client	3.0.3-4
> i dhcp3-common	3.0.3-4
>
> My lease time is about 60 minutes. Just last night the dhcp server
> was down and I got this in my syslog every five minutes:
>
> Oct 17 13:18:02 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 5
> Oct 17 13:18:07 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 6
> Oct 17 13:18:13 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 6
> Oct 17 13:18:19 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 11
> Oct 17 13:18:30 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 7
> Oct 17 13:18:37 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 13
> Oct 17 13:18:50 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 13
> Oct 17 13:19:03 localhost dhclient: No DHCPOFFERS received.
> Oct 17 13:19:03 localhost dhclient: No working leases in persistent
> database - sleeping.
>
> After 13 hours, when the dhcp server came alive, the dhclient got the
> address just like always:
>
> Oct 17 13:25:25 localhost dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 3
> Oct 17 13:25:25 localhost dhclient: DHCPOFFER from vvv.xxx.yyy.zzz
> Oct 17 13:25:25 localhost dhclient: DHCPREQUEST on eth0 to
> 255.255.255.255 port 67
> Oct 17 13:25:25 localhost dhclient: DHCPACK from vvv.xxx.yyy.zzz
> Oct 17 13:25:25 localhost dhclient: bound to vvv.xxx.my.ip -- renewal in
> 2731 seconds.
>
> I'm sorry I can't think of any reason why yours exit while mine goes to
> sleep. I don't know any config file where that could be adjusted.
>
> My /etc/dhclient.conf is pretty much commented out, i.e. the retry and
> the timeout are the default.
>
> > Syslog snippet:
> >
> > Oct 17 09:04:19 localhost dhclient: Internet Software Consortium DHCP
> > Client 2.0pl5
> > Oct 17 09:04:19 localhost dhclient: Copyright 1995, 1996, 1997, 1998,
> > 1999 The Internet Software Consortium.
> > Oct 17 09:04:19 localhost dhclient: All rights reserved.
> > Oct 17 09:04:19 localhost dhclient:
> > Oct 17 09:04:19 localhost dhclient: Please contribute if you find this
> > software useful.
> > Oct 17 09:04:19 localhost dhclient: For info, please visit
> > http://www.isc.org/dhcp-contrib.html
> > Oct 17 09:04:19 localhost dhclient:
> > Oct 17 09:04:19 localhost dhclient: sit0: unknown hardware address type
> > 776 Oct 17 09:04:19 localhost kernel: NETDEV WATCHDOG: eth1: transmit
> > timed out Oct 17 09:04:19 localhost kernel: eth1: Tx timed out, cable
> > problem? TSR=0x0, ISR=0x0, t=397.
> > Oct 17 09:04:20 localhost dhclient: sit0: unknown hardware address type
> > 776 Oct 17 09:04:20 localhost dhclient: Listening on
> > LPF/eth1/00:20:18:80:85:50 Oct 17 09:04:20 localhost dhclient: Sending on
> >   LPF/eth1/00:20:18:80:85:50 Oct 17 09:04:20 localhost dhclient: Sending
> > on
> > Socket/fallback/fallback-net
> > Oct 17 09:04:20 localhost dhclient: DHCPREQUEST on eth1 to
> > 255.255.255.255 port 67
> > Oct 17 09:04:20 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:20 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=377.
> > Oct 17 09:04:21 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:21 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=760.
> > Oct 17 09:04:24 localhost dhclient: DHCPREQUEST on eth1 to
> > 255.255.255.255 port 67
> > Oct 17 09:04:24 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:24 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=2960.
> > Oct 17 09:04:25 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:25 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=377.
> > Oct 17 09:04:26 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:26 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=376.
> > Oct 17 09:04:30 localhost kernel: eth1: no IPv6 routers present
> > Oct 17 09:04:30 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:30 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=1177.
> > Oct 17 09:04:30 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 3
> > Oct 17 09:04:31 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:31 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=976.
> > Oct 17 09:04:33 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 4
> > Oct 17 09:04:33 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:33 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=1389.
> > Oct 17 09:04:37 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 7
> > Oct 17 09:04:41 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:41 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=3776.
> > Oct 17 09:04:43 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:04:43 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=1077.
> > Oct 17 09:04:44 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 19
> > Oct 17 09:05:03 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:03 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=18576.
> > Oct 17 09:05:03 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 8
> > Oct 17 09:05:04 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:04 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=576.
> > Oct 17 09:05:11 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 9
> > Oct 17 09:05:11 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:11 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=6653.
> > Oct 17 09:05:20 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 10
> > Oct 17 09:05:30 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 1
> > Oct 17 09:05:30 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:30 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=10176.
> > Oct 17 09:05:31 localhost dhclient: No DHCPOFFERS received.
> > Oct 17 09:05:31 localhost dhclient: Trying recorded lease 83.85.134.79
> > Oct 17 09:05:32 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:32 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=1061.
> > Oct 17 09:05:34 localhost dhclient: bound: renewal in 117 seconds.
> > Oct 17 09:05:34 localhost dhclient: receive_packet failed on eth1:
> > Network is down
> > Oct 17 09:05:36 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:36 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=398.
> > Oct 17 09:05:41 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:05:41 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=4061.
> > Oct 17 09:05:45 localhost kernel: eth1: no IPv6 routers present
> > Oct 17 09:07:28 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:07:28 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:07:28 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:07:36 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:07:36 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:07:36 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:07:43 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:07:43 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:07:43 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:07:56 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:07:56 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:07:56 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:08:05 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:08:05 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:08:05 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:08:16 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:08:16 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:08:16 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:08:33 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:08:33 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:08:33 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:08:50 localhost fetchmail[2017]: awakened at Mon Oct 17
> > 09:08:50 2005
> > Oct 17 09:08:50 localhost fetchmail[2017]: POP3 connection to
> > pop3.casema.nl failed: temporary name server error.
> > Oct 17 09:08:50 localhost fetchmail[2017]: Query status=2 (SOCKET)
> > Oct 17 09:08:50 localhost fetchmail[2017]: POP3 connection to
> > pop.wanadoo.nl failed: temporary name server error.
> > Oct 17 09:08:50 localhost fetchmail[2017]: Query status=2 (SOCKET)
> > Oct 17 09:08:50 localhost fetchmail[2017]: POP3 connection to
> > elektron.its.tudelft.nl failed: temporary name server error.
> > Oct 17 09:08:50 localhost fetchmail[2017]: Query status=2 (SOCKET)
> > Oct 17 09:08:50 localhost fetchmail[2017]: sleeping at Mon Oct 17
> > 09:08:50 2005
> > Oct 17 09:09:03 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:09:03 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:09:03 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:09:55 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:09:55 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:09:55 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:10:41 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:10:41 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:10:41 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:11:12 localhost dhclient: DHCPREQUEST on eth1 to 10.1.127.7
> > port 67
> > Oct 17 09:11:12 localhost dhclient: send_packet: Network is unreachable
> > Oct 17 09:11:12 localhost dhclient: send_packet: please consult README
> > file regarding broadcast address.
> > Oct 17 09:11:20 localhost dhclient: DHCPREQUEST on eth1 to
> > 255.255.255.255 port 67
> > Oct 17 09:11:20 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:11:20 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=335861.
> > Oct 17 09:11:42 localhost dhclient: DHCPREQUEST on eth1 to
> > 255.255.255.255 port 67
> > Oct 17 09:12:03 localhost dhclient: DHCPREQUEST on eth1 to
> > 255.255.255.255 port 67
> > Oct 17 09:12:03 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:12:03 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=21171.
> > Oct 17 09:12:30 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:12:30 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=798.
> > Oct 17 09:12:30 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 5
> > Oct 17 09:12:30 localhost dhclient: receive_packet failed on eth1:
> > Network is down
> > Oct 17 09:12:31 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:12:31 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=786.
> > Oct 17 09:12:34 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 14
> > Oct 17 09:12:35 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:12:35 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=785.
> > Oct 17 09:12:40 localhost kernel: eth1: no IPv6 routers present
> > Oct 17 09:12:48 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 8
> > Oct 17 09:12:48 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:12:48 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=9535.
> > ct 17 09:12:56 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 8
> > Oct 17 09:13:04 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 10
> > Oct 17 09:13:04 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:13:04 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=8185.
> > Oct 17 09:13:14 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 15
> > Oct 17 09:13:29 localhost dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 1
> > Oct 17 09:13:29 localhost kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out Oct 17 09:13:29 localhost kernel: eth1: Tx timed out, cable problem?
> > TSR=0x0, ISR=0x0, t=15185.
> > Oct 17 09:13:30 localhost dhclient: No DHCPOFFERS received.
> > Oct 17 09:13:30 localhost dhclient: No working leases in persistent
> > database.
> > Oct 17 09:13:30 localhost dhclient: Exiting.
> >
> > Simo Kauppi wrote:
> > >On Mon, Oct 17, 2005 at 09:43:29AM +0200, Arjen Verweij wrote:
> > >>Hi,
> > >
> > >Hi,
> > >
> > >>I'm looking for a way to keep my box connected. Sometimes the
> > >>connections drops for various reasons:
> > >>
> > >>- cable removed from modem/nic
> > >>- power outage
> > >>- booted without cable
> > >>
> > >>The problem is, that dhclient just gives up:
> > >>Oct 17 09:13:29 localhost kernel: eth1: Tx timed out, cable problem?
> > >>TSR=0x0, ISR=0x0, t=15185.
> > >>Oct 17 09:13:30 localhost dhclient: No DHCPOFFERS received
> > >>Oct 17 09:13:30 localhost dhclient: No working leases in persistent
> > >>database.
> > >>Oct 17 09:13:30 localhost dhclient: Exiting.
> > >>
> > >>From this point on, I need physical access to the machine to make it
> > >>connect again. I tried installing ifplugd and configured it for eth1,
> > >>but removing/replugging the cable does not have the desired effect.
> > >>According to syslog nothing happens and dmesg looks uneventful as well.
> > >>Anyhow, if there were a way to have dhclient keep running, I would not
> > >>have this problem, and my box could just regain connectivity itself.
> > >>
> > >>Can anyone point me in the right direction, so far I have tried man
> > >>dhclient.conf and installed ifplugd for eth1, but no cigar.
> > >>
> > >>Regards,
> > >>
> > >>Arjen
> > >>
> > >>P.S. Please Cc: me on reply.
> > >>
> > >>--
> > >>No virus found in this outgoing message.
> > >>Checked by AVG Anti-Virus.
> > >>Version: 7.0.344 / Virus Database: 267.12.1/136 - Release Date:
> > >> 15-10-2005
> > >
> > >I run my dhclient (I'm using dhcp3) automatically from ifup and it
> > >doesn't exit eventhough the dhcp server is down and there is no
> > >DHCPOFFERS. It just continues trying after the default time (5 minutes).
> > >
> > >If you run dhclient manually, you could try -w option. See man dhclient
> > >for details.
> > >
> > >Simo
>
> Simo
Reply to:
References:
- prevent dhclient from exting
  - From: Arjen Verweij <a.verweij@student.tudelft.nl>
- Re: prevent dhclient from exting
  - From: Arjen Verweij <a.verweij@student.tudelft.nl>
- Re: prevent dhclient from exting
  - From: Simo Kauppi <swk@nic.fi>
Prev by Date: Re: Socket 754 Sempron Kernel
Next by Date: Re: 2 wan + 2 fire + 1 mdz
Previous by thread: Re: prevent dhclient from exting
Next by thread: a sanitary equipment company from China
Index(es):
- Date
- Thread