* Peter Breger
ka1ifq wrote: [...]
You are setting the card to use DHCP, are you running a DHCP server on your Linux box or your router?
Linux PC is set up as client only, connected via ethernet to a hardware router which does the DHCP serving
Do you see any errors or warnings when yast is completing its run, or in any of the log files?
Mmmh - where would I have to find these (you see I am new to Linux...) ... boot.msg has something to say, here is a short summary of what it has to say on network matters (sorry, cannot actually use file text cut and paste but have to retype laboriously in this mail on another Windows PC, [] encloses my own comment)
setting up network interfaces: lo IP address: 127.0.0.1/8 done eth0 device: 3Com [and all kinds of bla bla on hardware card] eth0 configuration: eth-bus-pci-0000:00:0f.0 eth0 (DHCP) . . . . . no IP address yet ... backgrounding. Warning: could not set up default route via interface. Command ip route replace to default via 192.168.1.1 returned: .RTNETLINK answers Network is unreachable Configuration line. default 192.168.1.1 - -
[then all kinds of other bla bla until it gets back to matter on hand]
eth0 dhcpcd is still waiting for data waiting eth0 interface could not be set up until now.
I have similar problems on occasion, my router looses dhcp and my local network goes down including access outside. Unplug the power cord from your router for > 2 minutes. Reconnect and issue as root, rcnetwork restart. ping an outside connection to check status, ping yahoo.com -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org