#Why I have so many rx errors?

12 messages · Page 1 of 1 (latest)

exotic timber
#

arch2600 ~]$ ethtool -S enp9s0
NIC statistics:
tx_packets: 1174792
rx_packets: 536338
tx_errors: 0
rx_errors: 9634
rx_missed: 0
align_errors: 5076
tx_single_collisions: 0
tx_multi_collisions: 0
unicast: 535942
broadcast: 6
multicast: 390
tx_aborted: 0
tx_underrun: 0
[@arch2600 ~]$ ethtool -i enp9s0
driver: r8169
version: 6.18.2-arch2-1
firmware-version: rtl8168g-2_0.0.1 02/06/13
expansion-rom-version:
bus-info: 0000:09:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

Settings for enp9s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: off
master-slave cfg: preferred slave
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: d
Link detected: yes

sweet helm
#

You may want to test your Ethernet cable and find out at which point between the Switch/Router and your PC/Laptop you don't get all pairs connected

exotic timber
#

I set that manually to 100, because I though 1000 was the problem

#

but not

#

my cable might be bad

#

I can't find a replacement so far

#

I only have this many issues with Dota 2 , normal download, torrent , etc works

sweet helm
#

Or some stong server in your network that is guaranteed have a working (proper) connection

#

You can do this by using this sudo ping -f 10.180.0.10 -c 65536

The output should look something like this:

rajala1404@archlinuxgayming ~> sudo ping -f 10.180.0.10 -c 65536
PING 10.180.0.10 (10.180.0.10) 56(84) bytes of data.
 
--- 10.180.0.10 ping statistics ---
65536 packets transmitted, 65536 received, 0% packet loss, time 7164ms
rtt min/avg/max/mdev = 0.062/0.103/3.367/0.031 ms, ipg/ewma 0.109/0.103 ms

The important part is the packet loss. In your local network you would expect 0% packet loss if you have packet loss something is either wrong with the target device or (more likely) the connection

#

The command will send 65536 packets really fast (the -f parameter does that) to the target IP