![](https://seccdn.libravatar.org/avatar/93cf6319a8961d144cf9d0dc09f5e319.jpg?s=120&d=mm&r=g)
On Thu, 2002-03-21 at 19:09, Robert C. Paulsen Jr. wrote: [snippety-doo-dah]
If you can't get to that web page, you probably need to reconfigure your networking. Perhaps the easiest way is to use YaST2 to set your network to get its IP address automatically via DHCP. The Linksys router acts as a DHCP server and will supply a good IP and the DHCP client on your SuSE system will set up the networking to work with the Linksys.
The first time you do this, you may need to issue the following as root:
rcdhclient restart
Wow, I wish I'd known about that last bit when I had my connection decide to go away (and it was YaST2 that did it to me, against my wishes...) Maybe 'rcdhclient restart' might have been the thing to save me from wiping my drive and installing SuSE 7.3 from scratch. Or not... I had made the horrible mistake of walking through a dial-up setup in YaST, so that I could see the same dialogs the my distant brother was seeing as he tried to do the same. Even though I exited before (what I thought was) the point that YaST would save the config, it saved it anyway and blew away my ethernet device (apparently stripping it bodily from the kernel) and taking the opportunity to also get rid of my (formerly working) sound configuration. Then, both YaST2 and YaST1 refused (gleefully and spitefully, it seemed at the time) to offer me any way to say "make ethernet-ness happen again". So, of course, I could never get to my D-Link box (similar to LinkSys). I got a few responses from this list (thanks, guys), but never saw any reference to 'rcdhclient restart' at that time. Oh well. Maybe someday I'll encounter a problem twice in a row, and can add a solution to my repertoire that doesn't involve total re-installation of Linux. :-) Aw, s**t, I'm whining again, aren't I. -- Kevin McLauchlan Chrysalis-ITS, Inc. "Ultimate Trust(TM)"