I loaded up OpenSuSE 11.4 on a HP DL360 G5 64 bit server. When the server boots up, I can connect via the wan or the local network segment. After some time, I will lose the WAN connection. If I ssh back into the computer from another computer the WAN connection can connect again for a period of time. The WAN connect is from the Internet. The firewall is off and so is AppArmor.
Please provide us with more details.
Are You using ifup or NetowrkManager ?
What is the output of :
/sbin/ifconfig
route -n
cat /etc/resolv.conf
Best regards,
Greg
[FONT=“Courier New”]:~ # /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:1F:29:69:D8:0E
inet addr:68.249.14.19 Bcast:68.249.14.23 Mask:255.255.255.248
inet6 addr: fe80::21f:29ff:fe69:d80e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6323 errors:0 dropped:0 overruns:0 frame:0
TX packets:3034 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:620828 (606.2 Kb) TX bytes:1441453 (1.3 Mb)
Interrupt:18 Memory:f8000000-f8012800
eth1 Link encap:Ethernet HWaddr 00:1F:29:69:D8:12
inet addr:68.249.14.19 Bcast:68.249.14.23 Mask:255.255.255.248
inet6 addr: fe80::21f:29ff:fe69:d812/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5391 errors:0 dropped:0 overruns:0 frame:0
TX packets:2539 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:669045 (653.3 Kb) TX bytes:558406 (545.3 Kb)
Interrupt:19 Memory:fa000000-fa012800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1088 (1.0 Kb) TX bytes:1088 (1.0 Kb)
:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
68.249.14.16 0.0.0.0 255.255.255.248 U 0 0 0 eth0
68.249.14.16 0.0.0.0 255.255.255.248 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 68.249.14.22 0.0.0.0 UG 0 0 0 eth1
:~ # cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
nameserver 206.141.193.55
nameserver 66.73.20.40
Please use code tags to wrap the output of the commands next time for better readability.
Posting in Code Tags - A Guide
You did not say whetver You’re using NetowrkManager or ifup. Why do You have tha same IP on both ethernet interfaces ?
Best regards,
Greg
I have a SLES 10 server with the same settings on that segment and it works just fine, but a different node IP address. I ran the commands and was I was logging off, I lost my network connection from putty to that server. I ran Windows 2008 R2 on the server with no problems. This is not a hardware problem.
Please tell us if You’re using NetowrkManager or not 
Check out this thread for reference :
Sometimes Suse loosing connection
Best regards,
Greg
I’m using ifup. The server is set to runlevel 3.
What are your settings in these files on SLES and openSUSE ?
/etc/sysconfig/network/ifcfg-eth0
/etc/sysconfig/network/ifcfg-eth1
Best regards,
Greg
cat /etc/sysconfig//network/ifcfg-eth-id-00:50:8b:e0:1c:\16
BOOTPROTO=‘static’
BROADCAST=’’
IPADDR=‘68.249.14.17’
MTU=’’
NETMASK=‘255.255.255.248’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
UNIQUE=‘FTXf.RADeXp5SjK4’
_nm_name=‘bus-pci-0000:03:05.0’
ETHTOOL_OPTIONS=’’
NAME=’’
USERCONTROL=‘no’
PREFIXLEN=’’
cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO=‘static’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=‘68.249.14.19/29’
MTU=’’
NAME=‘NetXtreme II BCM5708 Gigabit Ethernet’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘no’
I always can connect from my SLES 10 server to the OpenSuSE 11.4 server 100% of the time. The only network problems I am having is from a different network segment. I can 100% of the time connect to the SLES box from a different network segment.
The files look essentially the same and right to me. Maybe there is something different in the routing table on SLES ?
A wild guess would be that the kernel drivers for Your ehternet adapter in the openSUSE kernel are at fault.
Best regards,
Greg
Downloaded SLES 11 SP1 and still had the same problems. Looks like the ethernet driver has a bug in it. I downloaded the HP network driver, compiled and installed. The server seems to be working.
Thank You very much for the feedback.
Best regards,
Greg
I was wrong. The internal NIC card has a hardware problem. HP is sending me a new motherboard for my server. I should be back on line Monday.
I am a newbie to OpenSUSE so I apologize in advance if I should have started a new thread. Although, I am a newbie, I do have some experience with Linux. I have been experiencing a similar situation where the eth0 interface link drops and reconnects, especially when I am transferring large amounts of data. I would like to try to trace down the issue. Based on the threads I read, I am taking the liberty of posting some logs
I am using the GNOME Network Manager. I read somewhere that the KDE Network Manager was unreliable.
/var/log/NetworkManager snippet
May 13 16:59:14 linux-wr1n nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
May 13 16:59:17 linux-wr1n nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
May 13 17:02:53 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:02:55 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 17:03:11 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:03:14 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 17:19:10 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:19:13 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:52:33 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:52:36 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:52:57 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:53:00 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:53:46 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:53:49 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:54:15 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:54:19 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 8 -> 2 (reason 40)
May 13 19:54:19 linux-wr1n NetworkManager[2469]: <info> (eth0): deactivating device (reason: 40).
May 13 19:54:19 linux-wr1n NetworkManager[2469]: <info> (eth0): canceled DHCP transaction, DHCP client pid 18403
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 2)
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) starting connection 'Auto eth0'
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 13 19:54:21 linux-wr1n nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> dhclient started with pid 21303
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 13 19:54:21 linux-wr1n NetworkManager[2469]: <info> (eth0): DHCPv4 state changed nbi -> preinit
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> (eth0): DHCPv4 state changed preinit -> reboot
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> address 192.168.2.105
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> prefix 24 (255.255.255.0)
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> gateway 192.168.2.1
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> nameserver '209.18.47.61'
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> nameserver '192.168.2.1'
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> domain name 'socal.rr.com'
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
May 13 19:54:23 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 13 19:54:24 linux-wr1n NetworkManager[2469]: <info> Clearing nscd hosts cache.
May 13 19:54:24 linux-wr1n NetworkManager[2469]: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 13 19:54:24 linux-wr1n NetworkManager[2469]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
May 13 19:54:24 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) successful, device activated.
May 13 19:54:24 linux-wr1n NetworkManager[2469]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 13 19:54:25 linux-wr1n nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
May 13 19:54:27 linux-wr1n nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
/etc/sysconfig/network/ifcfg-eth0 output
BOOTPROTO='dhcp+autoip'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='82573V Gigabit Ethernet Controller (Copper)'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
USERCONTROL='no'
IFPLUGD_PRIORITY='0'
Let me know what I can do to make the connection reliable.
Thanks.
This looks like a hardware problem to me. Could You try a different port on the switch and a different ethernet cable ?
Best regards,
Greg
I have two eth ports and they are connected to the same switch and they both exhibit the same problems. I switch to ifup and same thing. Running 11.4 64 bit. I am backing up a 60 GB folder on a samba drive. Why do you think it is a hardware problem?
Because of this :
May 13 17:02:53 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:02:55 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 17:03:11 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:03:14 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 17:19:10 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 17:19:13 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:52:33 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:52:36 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:52:57 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:53:00 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:53:46 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
May 13 19:53:49 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now ON (device state 8)
May 13 19:54:15 linux-wr1n NetworkManager[2469]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
So maybe it’s a cable fault ? Did You check that as well ?
The other option is that I’m completely wrong and the problem lies somewhere else but please try a different cable first.
Best regards,
Greg
Greg,
Thanks for replying. However, I don’t believe it is a cable or switch port problem. I have a five port switch in my home office that provides connectivity to a HP NAS, a QNAP01 NAS, a network printer, and two ports on openSUSE workstation. I have transferred the 68 GB folder from a workstation from another part of the house to the QNAP server.
I tried something different. I attached a Linksys USB200M 10/100 Ethernet Adapter and the messages about “could not read the smb file” did not appear as frequent. Also, the link did not drop. For instance, last night, I transferred 10 GB before I got the error. Once the error appears, I get the error message more frequent. Today, toggled between the ifup and NetworkManager to get a IP address. Once I did that, I transferred 60 GB before I received a message that it could not read a SMB file.
What logs should I be checking?
Ok this does not look like a hardware problem now
Where does the samba server reside ? Could You check the logs of the samba server ?
If the server resides on openSUSE itself apparmor might be at fault.
Other than that on openSUSE I would check “/var/log/warn”.
Best regards,
Greg