Gene Heskett wrote:
On Friday 04 August 2006 09:09, Paul Howarth wrote:subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.20 192.168.2.31; option domain-name-servers 192.168.2.11, 192.168.2.1; option subnet-mask 255.255.255.0; option broadcast-address 192.168.2.255; option domain-name "intra.city-fan.org"; option routers 192.168.2.11; }Ok I had this: ddns-update-style interim; ignore client-updates; subnet 192.168.71.0 netmask 255.255.255.0 { # --- default gateway option routers 192.168.71.1; option subnet-mask 255.255.255.0; option domain-name "coyote.den"; option domain-name-servers 192.168.71.1; option time-offset -18000; # Eastern Standard Time # option ntp-servers 192.168.1.1; # option netbios-name-servers 192.168.1.1;# --- Selects point-to-point node (default is hybrid). Don't change this unless# -- you understand Netbios very well # option netbios-node-type 2; range dynamic-bootp 192.168.71.101 192.168.71.115; default-lease-time 21600; max-lease-time 43200; # we want the nameserver to appear at a fixed address host ns { next-server gene.coyote.den; hardware ethernet 00:04:4B:5D:EB:7D; fixed-address 192.168.71.1; } } Which may not be correct in itself :( but it worked. And I've added this below that: group { # we want the lappy at a fixed address too host diablo { hardware ethernet 00:14:A5:75:32:C9; fixed address 192.168.71.5; } } But a network restart on the lappy is still getting 192.168.71.102?
You did restart the dhcp server, right? Paul. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
