Sometimes Suse loosing connection

English Network/Internet
1

Hello,

I’m dummy in linux world and maybe someone can help? Installed Opensuse 11.4 64bit on Hyper-V virtual machine all is working fine except sometimes lan connection is lost.

/etc/init.d/network restart

is not helping and I need manual reboot.
Why that? What’s problem?

In routes table I can see default gw.

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
178.16.16.192   *               255.255.255.192 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         178.16.16.193   0.0.0.0         UG    0      0        0 eth0
2

We need some more information to help You. Does this VM has internet access ? If yes please provide outputs of ping commands to 8.8.4.4 and for example lwn.net.

Are You using ipv6 ?

Are You using NetworkManager or ifup ?

Best regards,
Greg

3

Yes, VM is having access to internet.

xxx:~ # ping 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_req=1 ttl=55 time=42.8 ms
64 bytes from 8.8.4.4: icmp_req=2 ttl=55 time=42.7 ms
64 bytes from 8.8.4.4: icmp_req=3 ttl=55 time=42.6 ms
64 bytes from 8.8.4.4: icmp_req=4 ttl=55 time=43.7 ms
^C
--- 8.8.4.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 42.657/43.008/43.728/0.471 ms


xxx:~ # ping lwn.net
PING lwn.net (72.51.34.34) 56(84) bytes of data.
64 bytes from sb.lwn.net (72.51.34.34): icmp_req=1 ttl=45 time=203 ms
64 bytes from sb.lwn.net (72.51.34.34): icmp_req=2 ttl=45 time=204 ms
64 bytes from sb.lwn.net (72.51.34.34): icmp_req=3 ttl=45 time=204 ms
^C
--- lwn.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 203.995/204.124/204.283/0.387 ms

No, only IPv4. Configuration initial was made with YAST.

4

What I meant was the output of those commands when You don’t have the connection. In fact doing a traceroute might be even better :slight_smile:

Best regards,
Greg

5

Hello,

There is output form commands. What you expecting to see there ?
Can anyone help? >:(

http://img202.imageshack.us/img202/9035/capture1oy.png](http://img202.imageshack.us/i/capture1oy.png/)

6

I think the Destination Host Unreachable might mean it’s a Hyper-V problem. Do You have other VMs running as well ? Can they access internet while openSUSE can’t ?

Best regards,
Greg

7

Yes, I have other VM runing, but problems only with this installation. There is only one difference all others hosts are windows servers. It’s possible to find out why it’s happening and so it’s actually Hyper-V problem?
Thanks!

8

I’m sure there is but I know nothing about Hyper-V so I can’t help You with that :slight_smile:
Anyway if the windows hosts don’t lose the internet than I guess some interaction between Hyper-V nad openSUSE is to blame.

Can You answer my question about using ifup or NetworkManager ?
If not sure read this :
Novell Documentation

If You’re using NetworkManager switch to ifup and see if the problem persists.

Best regards,
Greg

9

Ok :slight_smile:

I’m using ifup. Do I need switch to network manager?
Thanks!

10

I think it should work better with ifup but if it’s causing problems trying NetworkManager won’t hurt. So yes please try this.

Another thing You might do is post the contents of your interface configuration file. Maybe there is an error there. The files are stored in /etc/sysconfig/network/
You need to paste the contents of the proper file here so it should be ifcfg-eht0 if the interface is called eth0 as shown by the terminal command ifconfig.

Best regards,
Greg

11

eth0 config

BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='xx.xx.xx.xx/26'
MTU=''
NAME='Virtual Ethernet Card 0'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='nfsroot'
USERCONTROL='no'
12

This might be the cause of your problems. Read this :
Chapter 23. Basic Networking

Section 23.4.1.2.5. Activating the Network Device

And try to do some tweaking.

Best regards,
Greg

13

Thank you very much :slight_smile:

14

You’re welcome. Keep us posted and tell us whetver You’ve solved your problem and what was the solution.

Best regards,
Greg

15

Guys from Microsoft forums was recommended one solution for Hyper-V and Linux. Use legacy network drivers instead of synthetic drivers. Only one thing there, legacy drivers are slower, but not crashing kernel.

16

Well in that case I would get rid of Hyper-V because there are no such problems on XenServer or VMware and Windows VMs work great on those as well :slight_smile:

Best regards,
Greg