At least we are making progress :/ One step at a time. First, on the IP address... The lazy way out would be to assign the IP addresses to your internal machines manually through YaST. You could just set your workstation to 192.168.0.3 and be done with it. Of course, you also would have to manually assign the netmask, default gateway (the internal IP of your router), and DNS server(s). Just make sure you have unique addresses on all your internal hosts. On NetBIOS, don't confuse NetBIOS with IP, they have nothing to do with each other. NetBIOS is used for Windows networking and is needed for samba and such, but not for IP. By the way, what brand is your router? Is it a Linksys or something similar? I use a Linksys switch/router at home for my firewall and for assigning DHCP to my lone internal windows machine, but I have my two SuSE boxen with fixed IPs. There was a time that I had it assign addresses to my SuSE boxen and I don't recall a problem but now I am rambling. 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
===== LPIC-1 N+ MCSE The difference between Linux and Microsoft is the difference between trust and anti-trust. __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com