I have not tried using the static IP addresses from Windows since the DHCP seems to work fine. If I try to use static IP addresses and it doesn't work, I am not sure I will have learned anything, however (except that I need DHCP notwithstanding the static IP numbers). I think the problem relates to how the DSL modem works. It acts as a relay to a DHCP server. Somehow, the relay is not working with Linux (my theory anyway) but there do not seem to be many configuration options available to try to fix this. Static IP is a no-go. One interesting fact that may help decipher the problem: My netmask is reported by windows as 255.255.255.252 (rather than the usual .0). As a result, my ip address which I enter into yast as x.x.x.217 gets changed in the route statement to x.x.x.216 (yast seems to do this automatically and I assume (since I am too lazy to look at the binary translation) that the logical product of 216 and 252 is 217 ...) I wonder if the strange netmask is causing problems when I try to use static ip addresses. In particular, do I need to change the IP addresses of the nameservers so that the product of the nameserver IP address and .252 is equal to the nameserver IP address reported by windows? Do I completely not understand the purpose of the netmask? Ron Oliver wrote:

...

I recently got Telocity DSL service and love it -- at least from Windows 98 where I get SDSL speeds approaching 1MB/sec (yes, thats right, synchronous as in upload and download are each 1MB!!!). I am very happy but unfortunately am using Windows 98 as I cannot after 18 hours of trying get SUSE 6.3 to work correctly with my network connection. Please help if you can!!!

...

Note that I have actually been assigned a static ip address and the dsl modem has a static gateway address.

If you haven't yet, I suggest configuring Win98 with the static IP address, gateway, etc. and see if you can ping your way out to the world.

If static IP works from 98, I'd use that and eliminate DHCP entirely.

Also, although I don't have DSL, cablemodems typically require crossover Ethernet cables, so be sure to try the same cable with your SuSE and Windows boxes (if they're different boxes.)

Finally, if all else fails, simplify. I'd boot single-user, mount your filesystems read-write, load your NIC module (if needed), then do ifconfig and route by hand. That way, you minimize your chances of something messing with your network configuration.

If THAT doesn't work, simplify again--throw your PC out the window, and drink heavily.

If any of that works, be sure to post it; I didn't post this. -- Ron Oliver (mailto:roliver-suse@quantum-networks.com)

____________________________________________________________________ Get free email and a permanent address at http://www.amexmail.com/?A=1 -- 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/