On Sun, 2005-10-23 at 23:34 +0100, Stephen Boddy wrote:
On Sunday 23 October 2005 23:12, Doug McGarrett wrote:
Doug McGarrett wrote: <munch> I rebooted Suse. No joy, no network.
Here's what I have done further. I now have the Linspire mail program on line, so I have 2 computers working. But I do NOT have networking on the Suse box. I was able to ping the ethernet hardware with a loopback code-- 127.0.0.1--and that worked OK. (I have also figured out how to get to YaST from the desktop, and how to add its icon there.)
The loopback has nothing to do with a physical network interface. pinging that means nothing.
If anyone needs to know what ifconfig or lsmod have to say, you'll have to tell me what to look for. I could probably type in the ifconfig output,
Well until you do, we don't even know if the interface (eth0) is there! Enter:
# /sbin/ifconfig -a
in a shell (don't type the #) and report the first two lines of each interface here. I expect to see eth0, lo and sit0.
sit0? I have no sit0 interface, what does it refer to? What makes it necessary to have an sit0 interface? On my laptop I have eth0, lo and wlan0. No sit0. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998