Intermittent network issues

For the past week i have been having intermittent network issues. Things like slow loading of web pages and even complete disconnect at time. When it disconnects its returns to normal after about a minute. At first I thought it was a faulty network card but I replaced it with another one and the problem remains. As of now I am using network manager to manage my connections instead of traditional mode.

Here is the results of ifconfig -a:

# ifconfig -aeth3      Link encap:Ethernet  HWaddr 00:12:17:4D:DE:70  
          inet addr:10.0.0.142  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:237733 errors:0 dropped:291 overruns:0 frame:16
          TX packets:174848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1871 txqueuelen:1000 
          RX bytes:190534460 (181.7 Mb)  TX bytes:15450644 (14.7 Mb)
          Interrupt:18 


lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:77 errors:0 dropped:0 overruns:0 frame:0
          TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17183 (16.7 Kb)  TX bytes:17183 (16.7 Kb)


vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

One thing I did notice was that there are dropped packets, and before I changed out the NIC there were quite a few RX errors.

ethtool tells me this:

 ethtool eth3
Settings for eth3:
	Supported ports:  TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Speed: 100Mb/s
	Duplex: Half
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown
	Supports Wake-on: pg
	Wake-on: g
	Current message level: 0x00000037 (55)
			       drv probe link ifdown ifup
	Link detected: yes

ethtool -S eth3
NIC statistics:
     tx_bytes: 15528537
     rx_bytes: 190631093
     tx_broadcast: 590
     rx_broadcast: 27872
     tx_multicast: 169
     rx_multicast: 0
     tx_unicast: 174642
     rx_unicast: 211031
     tx_mac_pause: 0
     rx_mac_pause: 0
     collisions: 1873
     multi_collisions: 259
     aborted: 0
     late_collision: 0
     fifo_underrun: 0
     fifo_overflow: 0
     rx_toolong: 0
     rx_jabber: 0
     rx_runt: 15
     rx_too_long: 0
     rx_fcs_error: 15


lspci yields:

# lspci
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub
00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01)
00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV44 [Quadro NVS 285] (rev a1)
05:02.0 Ethernet controller: Linksys Gigabit Network Adapter (rev 12)
05:04.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
05:04.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
05:04.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)

System is running Opensuse 11.4 with kernel 2.6.37.6-0.20

Any advise would be appreciated. Thank you all.

When I run the ethtool terminal command, here is what I get (Its been a shorter time since I restarted than you):

james@linux-c100:~> /usr/sbin/ethtool -S eth0

NIC statistics:
     tx_packets: 14609
     rx_packets: 15467
     tx_errors: 0
     rx_errors: 0
     rx_missed: 0
     align_errors: 0
     tx_single_collisions: 0
     tx_multi_collisions: 0
     unicast: 14236
     broadcast: 822
     multicast: 409
     tx_aborted: 0
     tx_underrun: 0

It seems that the collision number for you stands out to me and could be due to a cabling problem of some sort perhaps?

Possible Causes of Ethernet Errors **
**
Collisions:
Signifies when the NIC card detects itself and another server on the LAN attempting data transmissions at the same time. Collisions can be expected as a normal part of Ethernet operation and are typically below 0.1% of all frames sent. Higher error rates are likely to be caused by faulty NIC cards or poorly terminated cables.

Single Collisions: The Ethernet frame went through after only one collision

Multiple Collisions: The NIC had to attempt multiple times before successfully sending the frame due to collisions.

CRC Errors: Frames were sent but were corrupted in transit. The presence of CRC errors, but not many collisions usually is an indication of electrical noise. Make sure that you are using the correct type of cable, that the cabling is undamaged and that the connectors are securely fastened.

Frame Errors: An incorrect CRC and a non-integer number of bytes are received. This is usually the result of collisions or a bad Ethernet device.

FIFO and Overrun Errors: The number of times that the NIC was unable of handing data to its memory buffers because the data rate the capabilities of the hardware. This is usually a sign of excessive traffic.

Length Errors: The received frame length was less than or exceeded the Ethernet standard. This is most frequently due to incompatible duplex settings.

Carrier Errors: Errors are caused by the NIC card losing its link connection to the hub or switch. Check for faulty cabling or faulty interfaces on the NIC and networking equipment.

I also wonder if you might not download and make a openSUSE 12.2 LiveCD and check out if the newer kernel helps you out any?

Thank You,

On 10/15/2012 02:36 PM, joescott4t wrote:
>
> For the past week i have been having intermittent network issues. Things
> like slow loading of web pages and even complete disconnect at time.
> When it disconnects its returns to normal after about a minute. At first
> I thought it was a faulty network card but I replaced it with another
> one and the problem remains. As of now I am using network manager to
> manage my connections instead of traditional mode.

–snip–
>
> Any advise would be appreciated. Thank you all.

Did you also change the cable?

On 2012-10-15 21:36, joescott4t wrote:

> One thing I did notice was that there are dropped packets, and before I
> changed out the NIC there were quite a few RX errors.

I would suspect the cabling.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Yes I believe you guys are on to something. I did notice that when i plugged my computer directly into the network jack in the wall I was getting a steady blinking green light, and an occasional amber blink on the NIC. However, I do have a switch involved that is normally connected to the wall jack and then to my computer. When I plug my computer into the switch I notice the the amber light is now more active and the green light has changed to an occasional flicker on the NIC. The switch is a netgear 10/100 Fast Ethernet. I did replace it with another exact model but the issues remained. Its was working fine for over a year I am not sure what changed. Here is the output of ethtool after I changed the cables and the switch:

ethtool -S eth3
NIC statistics:
tx_bytes: 32055586
rx_bytes: 381216262
tx_broadcast: 1155
rx_broadcast: 52022
tx_multicast: 331
rx_multicast: 41
tx_unicast: 360254
rx_unicast: 421913
tx_mac_pause: 0
rx_mac_pause: 0
collisions: 3210
multi_collisions: 436
aborted: 0
late_collision: 0
fifo_underrun: 0
fifo_overflow: 0
rx_toolong: 0
rx_jabber: 0
rx_runt: 24
rx_too_long: 0
rx_fcs_error: 24

Got to ask what else makes up your network and how are their cables? If you need a network switch, that means there is more to your network that just a single PC. Your numbers for collisions look no better after your changes to me.

Thank You,

On 15/10/12 22:46, joescott4t wrote:
>
> Yes I believe you guys are on to something. I did notice that when i
> plugged my computer directly into the network jack in the wall I was
> getting a steady blinking green light, and an occasional amber blink on
> the NIC. However, I do have a switch involved that is normally connected
> to the wall jack and then to my computer. When I plug my computer into
> the switch I notice the the amber light is now more active and the green
> light has changed to an occasional flicker on the NIC. The switch is a
> netgear 10/100 Fast Ethernet. I did replace it with another exact model
> but the issues remained. Its was working fine for over a year I am not
> sure what changed. Here is the output of ethtool after I changed the
> cables and the switch:
>
> ethtool -S eth3
> NIC statistics:
> tx_bytes: 32055586
> rx_bytes: 381216262
> tx_broadcast: 1155
> rx_broadcast: 52022
> tx_multicast: 331
> rx_multicast: 41
> tx_unicast: 360254
> rx_unicast: 421913
> tx_mac_pause: 0
> rx_mac_pause: 0
> collisions: 3210
> multi_collisions: 436
> aborted: 0
> late_collision: 0
> fifo_underrun: 0
> fifo_overflow: 0
> rx_toolong: 0
> rx_jabber: 0
> rx_runt: 24
> rx_too_long: 0
> rx_fcs_error: 24
>
>

Just to ask the obvious, have you checked if you have set up a loop on
the switch? Can you/have you disconnected items from the switch (all but
the computer would be a start) to see if there is any change?


PeeGee

MSI m/b 870-C45, AMD Athlon II X3 445, 4GB, openSUSE 12.1/11.4 x86_64
dual boot + XP Home in VBox
Asus m/b M2NPV-VM, AMD 64X2 3800+, 2GB, openSUSE 11.3 x86_64/XP Home
dual boot
Asus eeePC 4G (701), Celeron M353, 2GB, openSUSE 11.3 on SSD

Just a note I had a mouse once chew the wires in the wall in a network setup! So yep things can change. :slight_smile:

The only devices that I have on there are a Windows PC and a IP phone. I still have quite a few RX failures, but now I have another problem. I cannot boot into gnome. :frowning:

If you can’t get Gnome to work, I request that you start another message thread on that problem to get the maximum exposure and possible help. Make sure to put in as much explanation as you can.

Thank You,

And that I did. http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/479808-unable-login-gnome-desktop.html