trouble with dhcp3-client "Can't allocate interface etlease {"
Hi all,
I am having trouble with dhcp3-client. First the trouble, then why I think
it is dhcp3-client.
I: When I try to start the network I get this error:
----------------------------------------------------------------------------
# /etc/init.d/networking start
Configuring network interfaces...Internet Systems Consortium DHCP Client
V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Can't allocate interface etlease {
interface .
Failed to bring up eth0.
done.
----------------------------------------------------------------------------
II: This also occurs if I just try to "ifup" the interface:
----------------------------------------------------------------------------
# ifup eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Can't allocate interface etlease {
interface .
Failed to bring up eth0.
----------------------------------------------------------------------------
III. Running dhclient (from dhcp3-client) (on a preconfigured wireless device)
does work:
----------------------------------------------------------------------------
# dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 2141
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:16:6f:8a:d5:78
Sending on LPF/eth0/00:16:6f:8a:d5:78
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
ip length 314 disagrees with bytes received 534.
accepting packet with data after udp payload.
DHCPACK from 192.168.1.100
bound to 192.168.1.3 -- renewal in 38361 seconds.
----------------------------------------------------------------------------
IV. I believe the culprit is dhcp3-client because using alternative dhcp
clients gives different (successful) results:
----------------------------------------------------------------------------
with dhcpcd instead of dhcp3-client
--------------------------------
# /etc/init.d/networking start
Configuring network interfaces...dhcpcd.exe: interface eth0 has been
configured with new IP=192.168.1.4
done.
-----------------------------------
with dhcp-client instead of dhcp3-client
-----------------------------------
# /etc/init.d/networking start
Configuring network interfaces...Internet Software Consortium DHCP Client
2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Listening on LPF/eth0/00:16:6f:8a:d5:78
Sending on LPF/eth0/00:16:6f:8a:d5:78
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
ip length 314 disagrees with bytes received 534.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.1.100
DHCPREQUEST on eth0 to 255.255.255.255 port 67
ip length 314 disagrees with bytes received 534.
accepting packet with data after udp payload.
DHCPACK from 192.168.1.100
bound to 192.168.1.5 -- renewal in 43200 seconds.
done.
----------------------------------------------------------------------------
Why does directly running "dhclient eth0" from dhcp3-client work (marked
with a "III" above), while using "ifup eth0" doesn't work ("II")? It almost
appears as though ifup is pass garbled arguments to dhclient, but I don't
know enough to figure out more.
My /etc/network/interfaces:
...................
auto lo
auto eth0
allow-hotplug eth1
# The loopback network interface
iface lo inet loopback
# eth0 is wireless
iface eth0 inet dhcp
wireless-mode managed
wireless-essid any
wireless-key off
# eth1 is wired
iface eth1 inet dhcp
...................
Thanks for your help!
C.
Reply to: