Clients not recieving IP's via DHCP
Tim Philips
timp at rndgroup.co.nz
Fri Feb 9 22:34:47 UTC 2007
David W. Hankins wrote:
Hi David,
> On Fri, Feb 09, 2007 at 09:18:22PM +1300, Tim Philips wrote:
>> 21:10:56.441805 IP (tos 0x10, ttl 16, id 0, offset 0, flags [none],
>> proto 17, length: 328) 127.0.0.1.bootps > 192.168.2.252.bootpc:
> ^^^^^^^^^
>> BOOTP/DHCP, Reply, length: 300, xid:0x889c873, flags: [none]
>> Your IP: 192.168.2.252
>> Server IP: 192.168.2.1
>> Client Ethernet Address: 00:0d:3a:4e:f4:da
>> Vendor-rfc1048:
>> DHCP:OFFER
>> SID:127.0.0.1
> ^^^^^^^^^
>> LT:7200
>> SM:255.255.255.0
>> DG:192.168.2.1
>> NS:192.168.2.1
>
> That doesn't work.
>
> The client has to unicast their renewals to the DHCP server as
> identified by the SID option.
>
> Probably the client is smart enough to know this and doesn't bother
> binding.
>
> Possibly the client also has a firewall applied that keeps out
> martians (IP source address of loopback).
>
>>>> server-identifier router;
>
> I'm guessing 'router' resolves to 127.0.0.1 due to /etc/hosts.
You were dead right, I have used an IP address as the server-identifier
now and the clients are picking up their IP address's.
Thanks everyone for your help.
Cheers.
--
Thanks
Tim Philips (RHCE)
RND GROUP LIMITED
More information about the dhcp-users
mailing list