Question 1: If you have a static IP why would you want to use dhcp? How I got dhclient to work (on BigPond Cable, Sydney) was to: - uninstall dhclient package from suse 6.2, it is dhclient version 2 and it is buggy - download dhclient version 3 from isc.org site - compile and install dhclient version 3 - go into YaST and set up your eth0 with an IP, gateway, and netmask and activate the eth0. I chose 192.168.1.0 environment (do NOT use setup 'dhcpclient' for the card) - reboot - your card comes up with LAN settings of course - run : 'dhclient eth0' (do NOT run /sbin/init.d/dhclient start) - you are contacting dhcp server and now you hopefully get a response and your card's settings get switched over to a new IP, gateway, netmask etc.... you should be surfable now *enjoying his holidays at Pearl Beach, Central Coast N.S.W., Australia* mk

From: Jeffery S.Norman <jeffery_norman@usa.net> To: suse-linux-e@suse.com

I am told by Telocity, which makes the modem and provides the DSL service, that Red Hat works "out of the box" with their service. Why not SuSE??!!!

Note that I have actually been assigned a static ip address and the dsl modem has a static gateway address. I have also tried configuring SuSE for a straight static TCP/IP connection (by using Yast to enter the ip address, gateway address, and netmask all as reported by winipcfg) instead of dhclient or dhpcdp. To no avail ....

______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- 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/