jbyers: > I put in following file > > [root@r3-mobile etc]# cat dhcpd.conf > > default-lease-time 259200; > max-lease-time 518400; > > subnet 192.168.2.0 netmask 255.255.255.0 { > option subnet-mask 255.255.255.0; > option broadcast-address 192.168.2.255; > option routers 192.168.2.1; > range 192.168.2.90 192.168.2.150; > option domain-name-servers 206.13.28.12 206.13.31.12; > } ... jbyers: But since having my laptop do the serving via that dhcpd.conf file appears to be working, why not leave it? what downside? Max: none except you won't be able to get a dynamically assigned address for any other node unless the laptop is up and running. So the router running dhcp in this case is a better solution since it is likely to always be on. jbyers: goodpoint I have another question re what is shown in: [root@r3-mobile ~]# cd /var/lib/dhclient [root@r3-mobile dhclient]# less dhclient-eth0.leases lease { interface "eth0"; fixed-address 192.168.2.112; option subnet-mask 255.255.255.0; option routers 192.168.2.1; option dhcp-lease-time 86400; option dhcp-message-type 5; option domain-name-servers 206.13.20.12,206.13.31.12,68.94.156.1; option dhcp-server-identifier 192.168.2.1; option domain-name "pacbell.net"; renew 3 2008/6/4 06:15:30; rebind 3 2008/6/4 17:18:48; expire 3 2008/6/4 20:18:48; } this lease info seems to identify my linksys router 192.168.2.1 as the dhcp server but I am still using the laptop dhcpd.conf to do the serving. This seems like a contradiction to me. I havent yet made any changes in my router. ???? Jack -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list