Following another post about Red Hat 9.0, I added the following lines
to my dhcpd.conf file:
not authoritative;
shared-network WORKSTATIONS {
subnet 172.16.0.0 netmask 255.255.0.0 {
ping-check true;
deny unknown-clients;
}
}
(The shared-network declaration existed previously, but without
ping-check and deny unknown-clients.)
It now works satisfactorily. (I didn't actually check exactly which
of these additions is strictly necessary.)
Eric
> > I am unable to boot with dhcp. The error occurs when dhclient runs
> > (in preparation for the root pivot I assume). It bombs with this
> > error:
>
> > ERROR! No root-path!
>
> > The log on the server shows what looks to me like odd behaviour (see
> > log entries below). It looks like the client gets the correct ip
> > address the first time, when booting from the network card. However
> > when the client machine subsequently calls dhclient, it requests a
> > different ip address (172.16.249.254) and is refused. What's going on
> > here?
>
> > I'm running Red Hat 9.0.
>
> > Jun 12 04:34:29 lts1 dhcpd: DHCPDISCOVER from 00:10:5a:12:08:6b via
> > eth0
> > Jun 12 04:34:29 lts1 dhcpd: DHCPOFFER on 172.16.1.8 to
> > 00:10:5a:12:08:6b via eth0
> > Jun 12 04:34:29 lts1 dhcpd: DHCPREQUEST for 172.16.249.254
> > (172.16.0.1) from 00:10:5a:12:08:6b via eth0: lease 172.16.249.254
> > unavailable.
> > Jun 12 04:34:29 lts1 dhcpd: DHCPNAK on 172.16.249.254 to
> > 00:10:5a:12:08:6b via eth0
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
