Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
reports under the "Network Link Access Properties" unit that it observed 2 duplicate & 1 redordered packet on the upload bandwidth test, and 49 duplicate & 60 reordered packets on the downoad test. During a few long-term pings i've left running from my site to various others on the internet, it is rare but i have seen a "DUP!" message there as well.
Would this be cause for concern? And if so, what would be the possible cause/solution? My router is a PC running ArchLinux, with an Intel I350 T4 quad-port PCIe NIC handling the WAN/LAN interfaces.
Depends on how often you experience it and if you're the receiver asking for or the sender of copies. What does this return:
Code:
ifconfig -a; netstat -s
Quote:
Originally Posted by psycroptic
And if so, what would be the possible cause/solution?
The kernels network stack will automagically attempt to compensate using a host of measures that are part of TCP/IP like congestion control but as to the solution this may or may not be yours to implement where adverse network conditions are beyond your realm of influence as you can't control or compensate for problems caused by the likes of traffic shaping, route problems, hardware glitches in routers or firewalls, etc, etc. For more see for example http://www.tcpipguide.com/index.htm.
Ip:
185399320 total packets received
3 with invalid headers
179467111 forwarded
0 incoming packets discarded
5859842 incoming packets delivered
181628186 requests sent out
2 dropped because of missing route
372 fragments dropped after timeout
19836 reassemblies required
9708 packets reassembled ok
372 packet reassembles failed
54 fragments received ok
139 fragments created
Icmp:
2991 ICMP messages received
2406 input ICMP message failed.
InCsumErrors: 135
ICMP input histogram:
destination unreachable: 2332
timeout in transit: 19
echo requests: 489
echo replies: 16
77430 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 76601
time exceeded: 275
echo request: 65
echo replies: 489
IcmpMsg:
InType0: 16
InType3: 2332
InType8: 489
InType11: 19
OutType0: 489
OutType3: 76601
OutType8: 65
OutType11: 275
Tcp:
22 active connections openings
18 passive connection openings
0 failed connection attempts
8 connection resets received
1 connections established
146512 segments received
217040 segments send out
138 segments retransmited
0 bad segments received.
2219 resets sent
Udp:
184186 packets received
3405 packets to unknown port received.
0 packet receive errors
1582 packets sent
0 receive buffer errors
0 send buffer errors
UdpLite:
TcpExt:
1 invalid SYN cookies received
8 ICMP packets dropped because they were out-of-window
12 TCP sockets finished time wait in fast timer
270 delayed acks sent
Quick ack mode was activated 5 times
49752 packets directly queued to recvmsg prequeue.
237006 bytes directly in process context from backlog
85898170 bytes directly received in process context from prequeue
9900 packet headers predicted
61918 packets header predicted and directly queued to user
57292 acknowledgments not containing data payload received
5707 predicted acknowledgments
9 times recovered from packet loss by selective acknowledgements
Detected reordering 1 times using FACK
1 congestion windows recovered without slow start by DSACK
1 timeouts in loss state
13 fast retransmits
3 forward retransmits
3 retransmits in slow start
3 other TCP timeouts
TCPLossProbes: 107
TCPLossProbeRecovery: 100
5 DSACKs sent for old packets
110 DSACKs received
2 connections reset due to unexpected data
3 connections aborted due to timeout
TCPDSACKIgnoredNoUndo: 100
TCPSackShiftFallback: 75
IPReversePathFilter: 10
TCPRcvCoalesce: 340
TCPOFOQueue: 3553
TCPAutoCorking: 73835
TCPSynRetrans: 1
TCPOrigDataSent: 171943
IpExt:
InTruncatedPkts: 1
InBcastPkts: 14310
InOctets: 174614653790
OutOctets: 338940895012
InBcastOctets: 4259341
InNoECTPkts: 203426130
InECT1Pkts: 111861
InECT0Pkts: 190854
InCEPkts: 41036
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
