Ok, i am on SUSE 10.3 abd encounter network problem:
sometimes i am able to use my network and internet (all eth interfaces, no DSL modems). but usually and suddenly the network fall down. often after a reboot, but during random connection attempts too (example, when i try Yahoo! France, it worked 2 seconds before, but it could simply crash the network).
in these situation, i am able to ping my own interface, but neither the gateway, nor another computer on the LAN.
using yast2, i try ifup mode and networkmanager (that i don’even understand), but it works and don’t work randomly! same with “ifconfig eth0 up | down”
on windows, i have no problem with the netword card!
First thing to do when it happens again would be to check your network settings. On your next issue open a terminal console and do the following;
’ su - ’ and enter root’s password
'ifconfig eht0 ’ this will give you information on current ip address end link error status - I’m assuming eht0 is the network card you always use.
’ route ’ this will display your main gateway and should be pointing to your router, try pinging the router… are you getting a reply?
’ cat /etc/resolv.conf ’ this prints the entries of your dns resolving… it should list valid dns server entries, if there is nothing in it there is a first issue.
That should give you a good start…
Also important: Which version of openSUSE are you using? And what hardware do you have (mainly network card).
This bit shows your interface is up but it has no ip address (else it would have been mentioned there)
The rest also shows your pc has no network configuration (default gateway is missing in the route table).
Your driver seems fine and if it’s a static ip configuration you want to make go into YaST > Network Devices.
There you can;
In the TAB Overview : Edit your network card settings and give it the static IP - lets say 192.168.0.20 (I understand you don’t have a dhcp server running?)
In the TAB DNS : looking at the resolv.conf you’ve already set it, but check the DNS settings
In the TAB Routing : enter your gateway ip to Internet (this is your router or modem ip address, which is probably 192.168.0.1?)
After you’ve set these save the settings by applying and retry if Internet is reachable.
but it shows that too:
"Hewlett Packard Company NC373i Integrated multifunction Gigabit Server Adapter (Not Connected).
The cable is plugged and works fine, i tested it!
randomly, the interface (managed by NetworkManager) turns the status of the network interface as “connected” or “not connected”, even if the cable is plugged, and i don’t know why!
on the systray, the program “kNetworkmanager” says now that wired interface is not available, and the networkcard LEDs turns on and off randomly. i thought its was the Network card whisch sucked, but with two other new, it is the same phenomenon!
‘ethtool eth0’ (run as root using ‘su -’) should show if the nic “sees” a connection.
You should see speed & duplex as well as a line stating ‘Link detected: yes’
If not it could be a driver issue… if there is no link please post the output of ’ hwinfo --network '.
As means of going a step back and start afresh you can try clearing out your current nic config files, rebooting and reconfiguring the nic using YaST.
For this you need to remove all the ifcfg-ehtx and ifcfg-wlanx files (leaving template and lo alone)
The files are in /etc/sysconfig/network/
Again, you have to be root to delete the files (and only delete ifcfg-eth* and ifcfg-wl*) and reboot. If that works you can switch to knetworkmanager and go on from there.
edit: it might be easier opening konqueror with root rights : enter ’ kdesu konqueror ’ on a normal console.
Then reconfigure using YaST.
…
edit2: I would suggest to configure using ifup first as this is the most direct way to setup you nic.
Also, if you are not already running the 64bit version of openSUSE I would suggest you do so as 32 bit is not supported on that hardware as far as I know, could well be that is why the driver is not picking up a link.
If this is a new setup you are doing, I would suggest going for openSUSE 11.0 (depending on what you want to do with the server), especially seeing it’s the G5 series. I think openSUSE 11.0 will squeeze more out of it performance wise.
You could try a LiveCD first to see if network support is ok.
Anyway, first step would be trying the firmware updates by using the firmware CD.
edit : that you didn’t find any ifcfg-wl* files is because there is no wlan (wireless) nic in your server, so that is ok!
hi i have a similar Problem…
I have installed Suse 10.3 64Bit Version on my PC (Hardware is only a Mainboard from MSI(945GCM5 V2) and a DVD Device and A ATA Hard Disk (for System files) and a SATA Device for Data).
I installed all and it worked quite fine… Then i disconnected the 2 hard disk and connected another ATA Device to test something with Windows XP.
I changed back to the Old Hardware Configure ration with the 2 Disks…
Now i couldn’t Connect to the Network; i even can’t ping my router…
It all worked fine bevor i tested windows xp…
I reinstalled Linux but i still have the Problem…
hwinfo --network tells me that no Link was found… I changed the Network cable but its ok… i think my network settings are ok(i’ll edit it in this post later). My router (fritzbox) works fine (i have 2 other PC’s configured with static ip’s OS:windows xp and windows 2k). even the fritzbox screen doesnt show a connected cable…
Can it be that Windows Changed Something in the Hardware Settings on my Board?
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.178.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.178.1 0.0.0.0 UG 0 0 0 eth0
There are 2 things that make me a little confused…
in the route table the first entry? i dont have any target with 192.168.178.0
in the resolv.conf is the entry search right?? i used fritz.box in the Yast2 settings–>network adapter under the Domain entry…
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.178.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.178.1 0.0.0.0 UG 0 0 0 eth0
There are 2 things that make me a little confused…
in the route table the first entry? i dont have any target with 192.168.178.0
That’s your LAN. It’s saying for any address in the subnet 192.168.178.x, use the interface eth0. It’s implicitly entered as a route when the interface is activated.
in the resolv.conf is the entry search right?? i used fritz.box in the Yast2 settings–>network adapter under the Domain entry…
Maybe not, but probably makes no difference. The search entry means that if you use a hostname like foo (with no period), then the search will also try foo.fritz.box. Whether your nameserver knows about this domain is a different matter. Maybe your fritz box uses this as its domain, or did you make a guess? I don’t know.
hm i just tried it with “fritz.box” because in the yast2 i have to make an entry in the Domain field and as i don’t now what to enter i first used my windows Workgroup (keller) and changed it latter into my routers name(fritz.box)… just to see if it would work — but it doesn’t…
Hm then i’ll look again after cable and router… but the point is it worked a few days ago (bevor i tried that windows xp stuff)
thx for fast replay
i check my cable and router (maybe the 2last ports are not working (i didn’t use them for about 3jears)i mean maybe…)
i will post if i have something new
IF your network device is on the motherboard, and you have booted XP, then you can try this:
Shut down the PC, unplug the wall power lead, press the power button on the PC.
Wait a few moments, then replace wall power lead and restart Suse.
Seems that with onboard devices, some hardware settings don’t clear with a normal powerdown because a standby voltage is present in the motherboard. So, a full power off and true cold start is required to clear.
