booting thin clients and firestarter

[DB Clinton]

On Feb 3, 2008 5:59 PM, Gavin McCullagh <gmccullagh at gmail.com> wrote:

>
> To me, the lack of these lines suggests something odd about your client,
> ie
> you're not getting the DHCPREQUEST which should come from the client after
> which the server should respond with a DHCPACK.  Then when the tftp
> request
> happens the little tftp warning goes in.
>
> To do the network booting, are you using a PXE booting network card, a
> floppy or what?


For my three desktop boxes, I'm booting through a floppy (courtesy of
rom-o-matic). I also have a Compaq laptop that I use to test - that boots
through it's own BIOS network boot and looks a bit different from the client
side. It appears to take an IP address (192.168.0.246) and then:
PXE E11 ARP Timeout
PXE E38 TFTP cannot open connection
PXE M0F
before giving up and moving on to Windows.

>
>
> Can you do the same test again, with the "tail -f" monitoring the logfile
> and also run this command:
>
>        sudo /usr/sbin/tcpdump -n -i eth0 udp port 67 or port 68


I switched the NIC to eth1. Here's the output from my desktop client's boot
(it too seemed to accept an IP address 192.168.0.245 this time):
=======================
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
18:18:48.574568 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:48.590466 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:49.001074 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:18:50.826211 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:50.826262 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:50.826745 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:18:50.826886 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:18:55.439513 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:55.439566 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:18:55.440063 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:18:55.440202 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:04.446435 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:04.446483 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:04.446956 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:04.447096 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:20.538075 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:20.538120 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:20.538590 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:20.538731 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:52.611528 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:52.611573 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:19:52.612046 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:19:52.612185 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:20:56.483827 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:20:56.483874 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:2a:43:ae:30:94, length 548
18:20:57.005112 IP 192.168.0.254.67 > 192.168.0.245.68: BOOTP/DHCP, Reply,
length 300
18:21:07.089950 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:07.090004 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:08.001072 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:10.089998 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:10.090046 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:10.090537 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:10.090689 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:17.088883 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:17.088929 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:17.089488 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:17.089643 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:33.086320 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:33.086371 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:21:33.086858 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:21:33.087001 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
========================

...and here's the output from the laptop's boot:
========================
18:23:57.080843 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:02:a5:b5:4d:2f, length 548
18:23:57.080892 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:02:a5:b5:4d:2f, length 548
18:23:58.001067 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:23:58.001200 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:23:58.124439 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:02:a5:b5:4d:2f, length 548
18:23:58.124490 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:02:a5:b5:4d:2f, length 548
18:23:58.144762 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:23:58.144891 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:23:58.146943 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:23:58.147068 IP 192.168.0.254.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 321
18:26:59.091978 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:26:59.092033 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:00.001101 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:03.091457 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:03.091509 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:03.091993 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:03.092136 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:12.089996 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:12.090044 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:12.090536 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:12.090680 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:29.087314 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:29.087369 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:50:da:d0:c6:af, length 300
18:27:29.265503 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
18:27:29.265658 IP 192.168.0.254.67 > 192.168.0.250.68: BOOTP/DHCP, Reply,
length 300
69 packets captured
69 packets received by filter
0 packets dropped by kernel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20080203/fefb751d/attachment.htm