On Wed, 2002-09-04 at 04:46, Michael Brown wrote:
On Tue, 3 Sep 2002, Stew Benedict wrote:
> > Yes. I used the GUI. This is the contents of /etc/dhcpd.conf:
> > #dhcpd.conf - generated by drakTermServ
> > ddns-update-style none;
> > # Long leases (48 hours)
> > default-lease-time 172800;
> > max-lease-time 172800;
> > # Include Etherboot definitions and defaults
> > include "/etc/dhcpd.conf.etherboot.include";
> > # Network-specific section
> > subnet 192.168.0.0 netmask 255.255.255.0 {
> > option routers 202.0.35.1;
> > option subnet-mask 255.255.255.0;
> > option broadcast-address 192.168.0.255;
> > option domain-name "ext.dev-zone.org";
> > option domain-name-servers 203.96.152.4, 127.0.0.1;
> > }
> > # Include client machine configurations
> > include "/etc/dhcpd.conf.etherboot.clients";
> > To be honest I don't know what the setting routers means. I guess it
> > got that from my static IP address, which ends in another number, not 1.
You've got a few major problems there:
"option routers" is presumably picked up from your default gateway
setting. I'm guessing you've got two network cards: one internal and one
external (or possibly a dial-up link etc in place of the external).
Yes you are correct, I have two network cards (one internal, the other
to my cable modem).
If
so, then you need to set "option routers 192.168.0.x;" so that clients on
the internal network use your box as the default gateway. You will also
need to set up IP forwarding, iptables etc.
I didn't set up those other things yet. But I did change "routers" to
192.168.0.1 (the IP address of this machine internally).
This is a change from what the GUI suggested.
You also need to set "option domain-name-servers" to something reasonable.
Since 127.0.0.1 appears in your list, I'm assuming that your box is
running a DNS server, in which case probably best to set "option
domain-name-servers 192.168.0.x;" as with "option routers" (note - no-one
else can access your box as 127.0.0.1! :-)
Ok, I just left the DNS of the ISP I use, since as far as I know I don't
run DNS (maybe that was an artifact on the internet connection sharing I
had earlier set up?).
> > This is the contents of /etc/dhcpd.conf.etherboot.clients:
> > host jennifer {
> > hardware ethernet 00:80:AD:77:A3:9B;
> > fixed-address 192.168.0.2;
> > filename "boot-tulip.2.4.19-7mdk.nbi";
> > }
> Looks resaonable.
If you're using Etherboot 5.0.7 or greater, then the declaration is
unnecessary; 5.0.7+ will automatically pick up the correct .nbi image
file based on the PCI ID of the network card that they boot from.
Ok, but that is what the GUI setup based on the values I gave. I didn't
change that.
Unfortunately the client can still not boot. It get's TX setup timeout,
then .TX timeout!
BTW if this is better discussed off list (since I'm clearly not an
expert on these matters and this discussion may be of no use to the
developers), then that's fine with me :-)
Damon
