dyhcpd replaced with dnsmasq - but users not authenticating

Sat Jan 31 15:49:37 GMT 2009

I've replaced dhcpd with dnsmasq, I set dnsmasq.conf file up and now thin clients are receiving the proper IP address and booting from server.
The problem now is I try to login, the system waits for 30 seconds and thenI get the message:

"No response from server. Restarting."
Then the screen goes blank, displaying only the arrow cursor. Nothing elsehappens.
I feel I'm near the solution, but I can't understand why it's not authenticating the users.

Any clue ?

TIA,
Sergio

PS: I attach the tcpdump I did before with standard dhcpd:

10:53:44.607037 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 548
10:53:44.607793 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:46.666456 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 548
10:53:46.666644 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:49.144202 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 548
10:53:49.144411 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:51.204159 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 548
10:53:51.204364 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:54.893507 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 548
10:53:54.893716 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:56.879436 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 271
10:53:56.879628 IP 192.168.1.200.67 > 192.168.1.1.68: BOOTP/DHCP, Reply, length 303
10:53:56.879845 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 283
10:53:56.879961 IP 192.168.1.200.67 > 192.168.1.1.68: BOOTP/DHCP, Reply, length 303
10:53:56.953445 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 548
10:53:56.953568 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:53:57.955509 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 283
10:53:57.955710 IP 192.168.1.200.67 > 192.168.1.1.68: BOOTP/DHCP, Reply, length 303
10:54:00.664466 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 548
10:54:00.664680 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:01.243267 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 271
10:54:01.243451 IP 192.168.1.200.67 > 192.168.1.2.68: BOOTP/DHCP, Reply, length 303
10:54:01.244279 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 283
10:54:01.244395 IP 192.168.1.200.67 > 192.168.1.2.68: BOOTP/DHCP, Reply, length 303
10:54:02.243319 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 283
10:54:02.243516 IP 192.168.1.200.67 > 192.168.1.2.68: BOOTP/DHCP, Reply, length 303
10:54:02.724395 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 548
10:54:02.724579 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:07.143094 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 271
10:54:07.143287 IP 192.168.1.200.67 > 192.168.1.3.68: BOOTP/DHCP, Reply, length 303
10:54:07.143517 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 283
10:54:07.143633 IP 192.168.1.200.67 > 192.168.1.3.68: BOOTP/DHCP, Reply, length 303
10:54:07.343918 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 548
10:54:07.344051 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:09.347284 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 283
10:54:09.347499 IP 192.168.1.200.67 > 192.168.1.3.68: BOOTP/DHCP, Reply, length 303
10:54:09.403865 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 548
10:54:09.404051 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:15.002160 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 271
10:54:15.002394 IP 192.168.1.200.67 > 192.168.1.4.68: BOOTP/DHCP, Reply, length 303
10:54:15.004538 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 283
10:54:15.004695 IP 192.168.1.200.67 > 192.168.1.4.68: BOOTP/DHCP, Reply, length 303
10:54:16.209999 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 548
10:54:16.210332 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:18.269914 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 548
10:54:18.270099 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:54:19.206566 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 283
10:54:19.206769 IP 192.168.1.200.67 > 192.168.1.4.68: BOOTP/DHCP, Reply, length 303
10:54:29.479319 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 271
10:54:29.941160 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 271
10:54:30.143568 IP 192.168.1.200.67 > 192.168.1.6.68: BOOTP/DHCP, Reply, length 303
10:54:31.041266 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 271
10:54:33.141502 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 271
10:54:33.141643 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 271
10:54:36.924349 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:95, length 548
10:54:38.677969 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:aa, length 548
10:54:38.775796 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 271
10:54:38.775934 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 271
10:54:39.011780 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:95, length 548
10:54:40.737909 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:aa, length 548
10:54:42.480133 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:1b:eb, length 548
10:54:43.076780 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:95, length 548
10:54:44.540070 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:1b:eb, length 548
10:54:44.802860 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:aa, length 548
10:54:45.151559 IP 192.168.1.200.67 > 192.168.1.5.68: BOOTP/DHCP, Reply, length 303
10:54:45.151762 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 283
10:54:47.248243 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 271
10:54:47.320653 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:19, length 548
10:54:48.605002 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:1b:eb, length 548
10:54:48.703228 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 283
10:54:49.380624 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:19, length 548
10:54:51.151846 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:95, length 548
10:54:52.877830 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:aa, length 548
10:54:53.445630 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:19, length 548
10:54:53.693000 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:43, length 548
10:54:55.662076 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:5c, length 548
10:54:55.752954 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:43, length 548
10:54:56.679931 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:1b:eb, length 548
10:54:57.722030 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:5c, length 548
10:54:59.817945 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:43, length 548
10:55:00.163284 IP 192.168.1.200.67 > 192.168.1.5.68: BOOTP/DHCP, Reply, length 303
10:55:01.520698 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:19, length 548
10:55:01.787003 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:5c, length 548
10:55:07.892981 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:43, length 548
10:55:09.862017 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:5c, length 548
10:55:15.175299 IP 192.168.1.200.67 > 192.168.1.5.68: BOOTP/DHCP, Reply, length 303
10:55:20.045314 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 271
10:55:45.195283 IP 192.168.1.200.67 > 192.168.1.6.68: BOOTP/DHCP, Reply, length 303
10:55:45.195484 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 283
10:56:05.211298 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:56:08.308444 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 283
10:56:30.242329 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
10:56:55.262270 IP 192.168.1.200.67 > 192.168.1.6.68: BOOTP/DHCP, Reply, length 303
11:01:08.401160 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 548
11:01:08.401663 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:10.461106 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 548
11:01:10.461318 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:12.490478 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 548
11:01:12.490646 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:14.550434 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 548
11:01:14.550612 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:17.755356 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 548
11:01:17.755552 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:19.815296 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 548
11:01:20.486305 IP 192.168.1.200.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
11:01:22.996180 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 548
11:01:23.127818 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 271
11:01:24.227919 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 271
11:01:25.083570 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 548
11:01:25.446012 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 271
11:01:26.001915 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 548
11:01:28.061866 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 548
11:01:28.061998 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 271
11:01:29.148493 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:bf, length 548
11:01:29.148624 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 271
11:01:30.613575 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 271
11:01:31.282145 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 548
11:01:32.126825 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d8:b9, length 548
11:01:32.126951 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:09, length 271
11:01:33.369521 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:88:d1:59, length 548
11:01:33.369649 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:86, length 271
11:01:33.369676 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:03:47:75:94:0b, length 271

-----------------------------

Date: Sun, 25 Jan 2009 11:27:13 -0800 (PST)
From: Sergio Dicandia <sdicandia at yahoo.com>
Subject: Re: Re: your mail
To: edubuntu-users at lists.ubuntu.com
Message-ID: <60846.79395.qm at web51011.mail.re2.yahoo.com>
Content-Type: text/plain; charset="us-ascii"

OK, now I installed DNSMasq and disabled dhcp3 on the server.
I
edited the .conf file to reflect my needs in terms of IP range and the
like; service seems to be up, I can monitor the requests with tcpdump
(I'll post the previous results asap), but thin clients don't boot. Is
there anything I should add/edit in dnsmasq.conf to have the clients
boot from the server ?
dhcpd had a couple of lines about pxe, but I'm not sure how to manage this with dnsmasq.

Thanks in advance for your help with this ...

Sergio

------------------------------

Message: 5
Date: Thu, 22 Jan 2009 10:15:04 +0000
From: Gavin McCullagh <gmccullagh at gmail.com>
Subject: Re: your mail
To: edubuntu-users at lists.ubuntu.com
Message-ID: <20090122101503.GM30775 at gmail.com>
Content-Type: text/plain; charset=us-ascii

Hi,

On Wed, 21 Jan 2009, Sergio Dicandia wrote:

> Now I'm thinking to replace the DHCP server, but I need something on the
> server itself, or on a device (the router, maybe) since I cannot ask the
> teacher to:
>
> 1- start a service machine (acting as a DHCP server)
> 2 - wait until it's up&running
> 3 - start the server
> 4 - start the TCs
> 
> Way too tricky for people used to switch on a general button and have all the PCs running (OK, WindowsME, but)
> What about a router ? I also need to assign fixed IPs to specific MAC adddresses to be able to use iTalc ...

Without looking in detail (yet) at your tcpdump, what I'd suggest is trying
to install one of the alternative dhcp servers on your ltsp server.  The
options I know of are udhcpd or dnsmasq.  I'm not certain of the config
details with those though.

The main reason for this is simply to be able to say "there _must_ be
something amiss in dhcpd".  Also, it will solve all your other issues
above in terms of not requiring users to do anything different.

Gavin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20090131/abb58082/attachment-0001.htm 