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 -- :r ~/.signature
Attachment:
signature.asc
Description: Digital signature