FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Edubuntu User

 
 
LinkBack Thread Tools
 
Old 02-03-2008, 09:59 PM
Gavin McCullagh
 
Default booting thin clients and firestarter

Hi,

On Sun, 03 Feb 2008, DB Clinton wrote:

> > A dhcp boot normally looks like this for us:
> >
> > Feb 1 08:18:57 brooks dhcpd[6450]: DHCPDISCOVER from 00:02:a5:77:46:6a via eth0
> > Feb 1 08:18:58 brooks dhcpd[6450]: DHCPOFFER on 87.42.170.159 to 00:02:a5:77:46:6a via eth0
> > Feb 1 08:18:58 brooks dhcpd[6450]: DHCPREQUEST for 87.42.170.159 (87.42.170.254) from 00:02:a5:77:46:6a via eth0
> > Feb 1 08:18:58 brooks dhcpd[6450]: DHCPACK on 87.42.170.159 to 00:02:a5:77:46:6a via eth0
> > Feb 1 08:18:58 brooks in.tftpd[21065]: tftp: client does not accept options
>
> > do you see all five of those lines in /var/log/syslog?
>
> Nope. The DHCPREQUEST, DHCPACK AND tftp: client does not... lines don't
> appear at all.

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?

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

which will show us what dhcp packets get sent and received. As an example,
here's one I've just done:

gavin@hector:~$ sudo /usr/sbin/tcpdump -n -i ath0 udp port 67 or port 68
tcpdump: WARNING: ath0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ath0, link-type EN10MB (Ethernet), capture size 96 bytes
22:50:34.004414 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:09:5b:d2:f0:2f, length 300
22:50:34.236718 IP 192.168.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 548
22:50:34.253600 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:09:5b:d2:f0:2f, length 300
22:50:34.477935 IP 192.168.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 548

> > > pxelinux.0 and nbi.img were actually not in that directory either. I
> > > copied them there but still no results.
> >
> > Any thoughts on how that happened? I would have thought you can't have
> > had booting working ever without at least one of those being in place.
>
> I have no idea. It certainly wasn't anything I did manually as I wasn't
> even aware there was such a directory until today. Sometime before the
> "crash", I did install a few packages (in my effort to set up some
> controls over the internet access of my clients). I installed (and
> subsequently, post-crash, uninstalled) Firehol, Dansguardian and Squid. I
> think that was all.

I can't imagine those would make a difference. Ogra would know better what
creates them but I'm pretty sure you couldn't have working network booting
without them.

Gavin


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-03-2008, 10:33 PM
"DB Clinton"
 
Default booting thin clients and firestarter

On Feb 3, 2008 5:59 PM, Gavin McCullagh <gmccullagh@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




--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-03-2008, 11:26 PM
Gavin McCullagh
 
Default booting thin clients and firestarter

On Sun, 03 Feb 2008, DB Clinton wrote:

> 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.

That's interesting -- an arp failure suggests the client is trying to
contact a machine but there is no response to the layer 2 arp request,
suggesting the ip address it's looking for is not up. Perhaps you might
try uncommenting the next-server directive in /etc/ltsp/dhcpd.conf, making
sure it points at your thin client server. Then restart dhcpd with

sudo /etc/init.d/dhcp3-server restart

and reboot your thin client.

Gavin



--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-04-2008, 12:04 AM
"DB Clinton"
 
Default booting thin clients and firestarter

That's interesting -- an arp failure suggests the client is trying to

contact a machine but there is no response to the layer 2 arp request,
suggesting the ip address it's looking for is not up. *Perhaps you might
try uncommenting the next-server directive in /etc/ltsp/dhcpd.conf, making

sure it points at your thin client server. *Then restart dhcpd with

* * * *sudo /etc/init.d/dhcp3-server restart

and reboot your thin client.
Done. But it didn't help for either client (desktop or laptop). The next-server ip address from dhcpd.conf (next-server 192.168.0.254 is definitely the one from eth1 in my ifconfig.




Gavin



--
edubuntu-users mailing list

edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users



--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-04-2008, 09:12 AM
"Denis Melnikov"
 
Default booting thin clients and firestarter

2008/2/3, DB Clinton <dbclin@gmail.com>:
> On Feb 3, 2008 1:29 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:
>
> I know. I remarked out (#) "authoritative" (along with every other line, for
> that matter) which I assumed would force the system to read the ltsp
> version.

Which file to use /etc/init.d/dhcp3-server decides. If you have
/etc/ltsp/dhcpd.conf
then it is used, otherwise the one in /etc/dhcp3/.

> Curiously, webmin, under servers, only shows me the dhcp3 version -
> remarks and all.

You can do 'Module Config' and pick the config file position.

Denis

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-07-2008, 01:25 AM
"DB Clinton"
 
Default booting thin clients and firestarter

After nearly two weeks of agony trying to figure out why my thin clients simply wouldn't boot (and what on earth it could have to do with Firestarter), I emailed an IT consultant (Gerald Butler - http://bffoss.com/bff/ to be precise) and asked for a professional consultation. He didn't have any time for that, but he still offered some ideas, one of which was to look at my switch (a simply 5-port Gigafast) as it sounded like it could be blocking ICMP packets. Thinking about that, I walked over to my switch and pulled its adapter plug, figuring I'd reset it.

That did it. Instant network! I still don't know exactly what went wrong. But then, I don't really much care either.
Thanks again for all the help from this forum...I've learned an enormous amount about Edubuntu from every step!

David

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 

Thread Tools




All times are GMT. The time now is 11:34 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org