Keith Winston
12/18/01 03:26PM >>> OK, your setup appears to be OK. Here is some general info on how SuSE handles DHCP clients which may help out...
When you configure a network interface in YaST, you can mark it for DHCP, which writes for example "eth0=dhclient" into /etc/rc.config.
If you have dhcpcd installed (which is the default), then the /etc/init.d/dhclient script uses it for the DHCP client program when it runs. From my understanding dhcpcd runs as a daemon and does NOT use any configuration file. That's the way it is working on my laptop.
If you DON'T have dhcpcd installed, but DO have dhclient, then it uses dhclient, which DOES use a configuration file.
I think the difference is that dhclient lets you control the settings more, but is usually not necessary.
So, see if you /sbin/dhcpcd installed. If not, then you are
probably using dhclient as your client program.
dhcpcd should always be running in the background. It is on my
lappy.
Regardless of which client program you are using, you can set
some general things in /etc/rc.config.d/dhcpcd.rc.config.
Hope this helps.
Keith
A few steps ahead of you Keith, /sbin/dhcpcd is installed. I found out that the following is executed at boot: startproc -t 1 -q /sbin/dhcpcd -R -t 999999 -d eth0 I added the -R and -d (don't overwrite /etc/resolv.conf and run in debug mode) using options in /etc/rc.confid.d/dhcpcd.rc.config If I run "/sbin/dhcpcd -R -t 999999 -l -1 eth0" or "/sbin/dhcpcd -R -t 999999 -d eth0" at the command line it prints out: dhcpcd: your IP address = 192.168.0.3 The -l -1 was a suggestion from Jeff to specify an infinite lease time, but from the dhcpcd man page, this is the default anyway. That's fine, but it still logs "infinite IP address lease time. Exiting" in /var/log/message and there are no dhcpcd processes running. If I run "/sbin/dhcpcd -R -t 999999 -l 9999 eth0" (lease time of 9999 seconds) it prints the same "your IP address" message but this time there is a dhcpcd process running. Unfortunately, after the amount of time elapses, my network connection is lost... Jeff also suggested changing the router's DHCP server configuration to specify a different lease time. Reading through the router's reference manual, that does not seem possible. The DHCP server is on or off, that is the limit of its "configuration". I am wondering if the router even needs to be a DHCP server? Does it just provide each machine a local IP (192.168.0.x), gateway (192.168.0.1), and subnet mask (255.255.255.0)? Can I point the other machines on the LAN to use the DNS server on 192.168.0.3 (my SuSE machine) for their address? I assume this would not work until after configuring the router to allow NetBIOS information to be forwarded to 192.168.0.3? Thanks for your help! I am starting to understand all this stuff finally... Josh