Re: dhcpd/tftp server subservient to another tftp server
Kent West wrote:
Kent West wrote:
When I boot the client pc ("bi-19x"), it gets the IP address
150.252.x.y from my dhcpd/tftp server, as indicated by the BIOS's PXE
messages. But then, instead of finding the pxelinux.0 file on my
dhcpd/tftp server, it finds the campus's central RIS server instead.
How do I get my client to get my tftp offering instead of the RIS
offering? BTW, the RIS server is on a different network segment.
I found this info at: http://www.carotechnology.com/dbox/bootingdbox.htm
Start tcpdump with the parameters 'port bootps or port bootpc or port
nfs or port tftp'
this way you will see most of the stuff that will interest you.
Boot up your dbox and look at the tcpdump output.
If you see and bootp answer going to 255.255.255.255 you are using the
wrong dhcp server!
Download the right one, recompile it and look for an answer going to
the box it self in stead of a broadcast.
Then the results on my server are:
westk[@bi-22x]:/home/westk:> sudo tcpdump port bootps
tcpdump: listening on eth0
19:09:35.150031 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x6c464962
[|bootp
]
19:09:35.152879 150.252.216.1.bootps > 255.255.255.255.bootpc:
xid:0x6c464962 f
lags:0x8000 G:150.252.216.1 ether 0:e0:0:f7:33:78 [|bootp]
19:09:40.195592 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x10d9e56
[|bootp]
19:09:40.201482 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x10d9e56
[|bootp]
19:09:46.895574 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x4816e258
secs:10
24 flags:0x8000 [|bootp]
19:09:46.896337 bi-22x.acu.edu.bootps > 255.255.255.255.bootpc:
xid:0x4816e258
secs:1024 flags:0x8000 Y:bi-19x.acu.edu S:bi-22x.acu.edu ether
0:3:47:16:e2:58 [
|bootp] [tos 0x10]
19:09:46.898621 150.252.216.1.bootps > 255.255.255.255.bootpc:
xid:0x4816e258 f
lags:0x8000 Y:150.252.217.227 S:ns2.acu.edu G:150.252.216.1 ether
0:3:47:16:e2:5
8 [|bootp]
19:09:46.902411 150.252.216.1.bootps > 255.255.255.255.bootpc:
xid:0x4816e258 f
lags:0x8000 S:150.252.135.87 G:150.252.216.1 ether 0:3:47:16:e2:58 [|bootp]
19:09:48.872412 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x4816e258
secs:10
24 flags:0x8000 [|bootp]
19:09:48.873190 bi-22x.acu.edu.bootps > 255.255.255.255.bootpc:
xid:0x4816e258
secs:1024 flags:0x8000 Y:bi-19x.acu.edu S:bi-22x.acu.edu ether
0:3:47:16:e2:58 [
|bootp] [tos 0x10]
10 packets received by filter
0 packets dropped by kernel
There is indeed a reference to 255.255.255.255; I don't understand what
the article means when it says "If you see and bootp answer going to
255.255.255.255 you are using the wrong dhcp server!" Does this mean
that the Debian package dhcp3-server is the wrong package for what I'm
trying to do? If so, what package should I be using?
--
Kent
Reply to: