client ignores DHCPOFFER
Martin Miethe
mmiethe at protourschile.com
Fri Mar 2 15:04:58 UTC 2007
David W. Hankins schrieb:
> On Thu, Mar 01, 2007 at 07:09:59PM -0300, Martin Miethe wrote:
>> This is my tcpdump:
>>> 12:31:31.046159 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:05:5d:94:c1:fb (oui Unknown), length: 548
>>> 12:31:31.048488 IP 192.168.1.9.bootps > ws097.ltsp.bootpc: BOOTP/DHCP, Reply, length: 300
>
> I wonder...if the client isn't setting the broadcast bit but
> needs it set.
>
> You might try setting always-broadcast server option (I can't
> remember the exact syntax right now), and have another look with:
>
> tcpdump -vvv -len -s 1500 udp port 67
>
> It could be that the server isn't sending some option(s) that the
> boot rom considers mandatory.
Ok, I added: "always-broadcast on;" to my dchpd.conf.
Now, this is the tcpdump (client still does not set the IP):
> 11:51:45.761287 00:05:5d:94:c1:fb > Broadcast, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto: UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:05:5d:94:c1:fb, length: 548, xid:0x5d9f9bdd, flags: [none] (0x0000)
> Client Ethernet Address: 00:05:5d:94:c1:fb
> Vendor-rfc1048:
> DHCP:DISCOVER
> MSZ:1500
> VC:"Etherboot-5.4"
> PR:SM+DG+HN+VO
> T150:175.5.1.17.6.49.6.177.2.3.0
> 11:51:45.761574 00:15:f2:d3:ba:a4 > Broadcast, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto: UDP (17), length: 328) 192.168.1.9.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length: 300, xid:0x5d9f9bdd, flags: [Broadcast] (0x8000)
> Your IP: 192.168.1.97
> Client Ethernet Address: 00:05:5d:94:c1:fb
> file "/lts/vmlinuz-2.6.17.8-ltsp-1"
> Vendor-rfc1048:
> DHCP:OFFER
> SID:192.168.1.9
> LT:21600
> SM:255.255.255.0
> DG:192.168.1.1
> HN:"ws097"
To me, this looks good.
Could it be that there is a problem with the linux kernel to load?
The path is good (/tftpbook//lts/vmlinuz-2.6.17.8-ltsp-1)...
I do not understand why windows does that and it wont work with the
boort rom...
Thanks for the help again, but I really would love to get this done...
Do you have another idea?
Best regards
Martin
More information about the dhcp-users
mailing list