James Carlson wrote: > Kyle McDonald writes: > >> 486138db: Datagram received on network device: bge0(limited broadcast) >> 486138db: Client: 0100145E2A91E2 has DYNAMIC 172.30.170.27 owned by >> server: 172.30.170.21. >> > > The "owned by server" message from in.dhcpd means that this server > believes that some *OTHER* server owns that entry. (See lines 259-292 > in the current Nevada in.dhcpd/dhcp.c.) > > It doesn't believe that it is identified as 172.30.170.21. > > Hmm. Ok. > At a guess, the address on this system was changed, and you didn't use > the OWNER_IP feature in dhcpsvc.conf(4) to let the server know about > its many identities. > > The address of the server hasn't changed, not since the dhcp server was configured from scratch. To be sure I just wiped it and configured it again.
The host has only 'bge0' configuired with the one IP (172.30.170.21). When immediately after dhcpconfig was run, 'dhcpconfig -P INTERFACES="bge0"' was also run. Given that that's the only interface and IP address (excepting the loopback addr.) on the host, that the host had that IP at boot, and when dhcpconfig was run to initially setup the server, *and* the debug output shows that that is the address for the interface in.dhcpd is listening on, should I need to add OWNER_IP="172.30.170.21" also? I'll try it, and see what happens. -Kyle _______________________________________________ networking-discuss mailing list [email protected]
