Problem with fixed-address statement
Jeffrey Collyer
jwc3f at virginia.edu
Tue Jul 28 14:59:13 UTC 2009
I have a dhcp client with a fixed address defined in the conf that is
not getting the defined fixed-address, but one from the pool for the
shared-network.
DHCP server is 4.1.0 running under Linux. Client is Windows XP SP3.
Config looks thusly :
host tty3 {fixed-address 137.54.142.125; hardware ethernet
00:1e:4f:b8:0c:23;}
host tty1 {fixed-address 137.54.142.127; hardware ethernet
00:14:22:60:0d:70;}
shared-network vlan-2442 {
subnet 137.54.142.0 netmask 255.255.255.0 {
option routers 137.54.142.1;
option subnet-mask 255.255.255.0;
pool {
deny unknown clients;
deny dynamic bootp clients;
failover peer "fopeer";
range 137.54.142.128 137.54.142.253;
}
}
}
When the machine in question (tty3) requests an address, the DHCP server
is currently handing back 137.54.142.205
Jul 28 09:40:53 herakles dhcpd: DHCPDISCOVER from 00:1e:4f:b8:0c:23 via
137.54.142.1
Jul 28 09:40:54 herakles dhcpd: DHCPOFFER on 137.54.142.205 to
00:1e:4f:b8:0c:23 (D2BFT3G1) via 137.54.142.1
Jul 28 09:40:54 herakles dhcpd: DHCPREQUEST for 137.54.142.205
(128.143.2.225) from 00:1e:4f:b8:0c:23 (D2BFT3G1) via 137.54.142.1
Jul 28 09:40:54 herakles dhcpd: DHCPACK on 137.54.142.205 to
00:1e:4f:b8:0c:23 (D2BFT3G1) via 137.54.142.1
However, the fixed-address defined as tty1, works fine on the same subnet.
Jul 27 08:39:34 herakles dhcpd: DHCPDISCOVER from 00:14:22:60:0d:70 via
137.54.142.1
Jul 27 08:39:34 herakles dhcpd: DHCPOFFER on 137.54.142.127 to
00:14:22:60:0d:70 via 137.54.142.1
Jul 27 08:39:34 herakles dhcpd: DHCPREQUEST for 137.54.142.127
(128.143.2.225) from 00:14:22:60:0d:70 via 137.54.142.1
Jul 27 08:39:34 herakles dhcpd: DHCPACK on 137.54.142.127 to
00:14:22:60:0d:70 via 137.54.142.1
So far my troubleshooting -
- had the client release/renew multiple times, rebooted the machine
several times as well.
- reset the switch the client was attached to, cleared the MAC from the
router's ARP cache (on a whim that maybe something was stuck).
- verified that no other machine was using that address, not pingable,
on the switch, or seen by the router.
- packet captured the traffic for that interface with wireshark and made
sure that the incoming DHCP request had the right MAC in it.
- another host on the same shared-network (tty1) is working properly, so
no generic problem.
- set up a new fixed-address definition for my laptop, restarted DHCP
server, saw that it worked, removed definition, restarted, got an
address from the default pool.
I'm stumped. Does anyone see anything amiss, or that I missed?
Or anyone know how to debug/log what the DHCP server is doing to choose
what address to hand out?
--
Jeff
More information about the dhcp-users
mailing list