Results 1 to 4 of 4
Is there any reference that gives a quick and dirty summary of the stats available in "netstat -s"? Specifically, under the "TcpExt" section there's a lot of really interesting stuff. ...
- 11-09-2010 #1Just Joined!
- Join Date
- May 2010
- Posts
- 3
Brief explanation or summary of "netstat -s" statistics?
Is there any reference that gives a quick and dirty summary of the stats available in "netstat -s"? Specifically, under the "TcpExt" section there's a lot of really interesting stuff. But - what does it all mean?? When I see "5 data loss events", what am I looking at? Sequence numbers that went unacknowledged? What are "congestion windows partially recovered"?
Any pointers to a general source of info would be great! Thanks,
- 11-09-2010 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
There is no simple answer to these questions. TCP/IP deals with data losses transparently to the application unless the connection is lost. This is normal. The purpose of this information in netstat is so if you think your network is underperforming, then a large amount of packet loss may indicate a connection problem. Normally, these subjects are the topics covered in an entire class on networking. How many weeks of study are you willing to devote to understanding this in detail?
One class I teach just scrapes the surface of this in a 4 credit-hour course.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 11-09-2010 #3Just Joined!
- Join Date
- May 2010
- Posts
- 3
I understand it's a huge topic, but at the moment I'm not looking for a full understanding of all the subtlety & nuance - I'm trying to see if there's anything I can use as a quick & dirty indicator of trouble.
Can I get anything out of these before I have a CCIE?
- 11-09-2010 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Read the man pages, do some googling, know that just a few errors is normal...

Best wishes to you. It isn't "rocket science", but there are a lot of nuances. Dropped packets over the internet are normal, as is congestion. Dealing with these are a part of the TCP/IP protocol suite. Over LAN's, they should be pretty infrequent, unless you have a REALLY overloaded network, in which case you should consider partitioning it into subnets so that traffic is isolated to the nodes that need it. Netstat and other tools will help you determine these situations.Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote
