Ron Cordell wrote:

I really want to find out what is going on with the scripts and where things are getting clobbered, because I suspect that you are correct when you say that is what is happening. I want to eventually get VPN masq'ing working, but that may take a while.

Just today, I got IP masquerading working with 6.2 and dhclient. After much time spent fighting my own inexperience, I also tracked down a bug in the /sbin/init.d/dhclient script which runs at boot time. This bug caused /sbin/dhclient to be called with eth0 as a parameter when it should have been eth1. The fix was to change if test -n "$if" ; then startproc -q /sbin/dhclient $NETDEV || return=$rc_failed echo -e "$return" fi to if test -n "$if" ; then startproc -q /sbin/dhclient $if || return=$rc_failed echo -e "$return" fi Other than that, the noteworthy difficulties were: 1. A problem reported earlier on this mailing list by Bernie Gardner hit me as well. I installed a new network card, but Yast would not enable me to revise the network base configuration. Workaround: edit rc.config directly, and remember to run SuSEconfig manually after each edit. 2. When errors occurred during the boot, they scrolled off my screen before they could be read. I learned about dmesg, but it didn't record all of the relevant messages. Anyone got a good way of dealing with this? 3. dhclient runs in the background, and it doesn't get a reply from the DHCP server for about 20 seconds. In the meantime the system continues booting and calls route, which determines that the default router is inaccessible and returns an error status. Eventually dhclient sets up routing OK, but the error message during boot is annoying. -- Scott Turner p.turner@computer.org http://www.ma.ultranet.com/~pkturner -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/