Request ignored (not authoritative) to only one client

Jerimiah Cole jcole at tbtc.net
Fri Jul 29 17:51:24 UTC 2011



I've got some new gear in my test environment and the DHCP server won't give it a lease.  It gives other clients in the same network leases without fail:

Jul 29 10:40:09 access00 dhcpd: DHCPDISCOVER from ff:ff:ff:e1:ac:06 via 10.98.0.1
Jul 29 10:40:10 access00 dhcpd: DHCPOFFER on 10.98.100.2 to ff:ff:ff:e1:ac:06 via 10.98.0.1
Jul 29 10:40:10 access00 dhcpd: DHCPREQUEST for 10.98.100.2 (192.168.39.101) from ff:ff:ff:e1:ac:06 via 10.98.0.1
Jul 29 10:40:10 access00 dhcpd: DHCPACK on 10.98.100.2 to ff:ff:ff:e1:ac:06 via 10.98.0.1

But it doesn't like this new stuff:

Jul 29 10:40:27 access00 dhcpd: DHCPDISCOVER from ee:ee:ee:1e:8a:82 via 10.98.0.1
Jul 29 10:40:28 access00 dhcpd: DHCPOFFER on 10.98.193.233 to ee:ee:ee:1e:8a:82 via 10.98.0.1
Jul 29 10:40:29 access00 dhcpd: DHCPREQUEST for 10.98.193.233 (192.168.39.101) from ee:ee:ee:1e:8a:82 via 10.98.0.1: ignored (not authoritative).

The config is about as as simple as they come:

option domain-name-servers 192.168.4.13;

default-lease-time 600;
max-lease-time 600;

# local
subnet 192.168.39.0 netmask 255.255.255.0 {
}

# test
subnet 10.98.0.0 netmask 255.255.0.0 {
  pool {
    range 10.98.100.0 10.98.255.254;
    deny dynamic bootp clients;
  }
  option routers 10.98.0.1;
}

I captured and compared the request packets for both the successful and failed transaction and there are no substantiative differences that I can find.  Anybody else seen this or have some suggestions for further troubleshooting?

Jerimiah




More information about the dhcp-users mailing list