Socket buffer overrun info from netstat

Socket buffer overrun info from netstat

Post by Siva Saravanan Jayarama » Thu, 27 Jul 2000 04:00:00

Im trying to get some information about UDP packet drops, specifically,
socket buffer overflows.

Netstat in freeBSD gives explicit information if packets are 'dropped due
to full socket buffers'

In Linux netstat just talks about UDP 'packet receive errors'.
I would guess that this statistic would include socket buffer overflows,
but I need to know for sure.

In case it doesnt, then can someone suggest an alternate tool to get that

I would appreciate it if you would cc me on ur replies.

        3273476 datagrams received
        0 with incomplete header
        0 with bad data length field
        0 with bad checksum
        66425 dropped due to no socket
        7667 broadcast/multicast datagrams dropped due to no socket
        320302 dropped due to full socket buffers
        0 not for hashed pcb
        2879082 delivered
        2901479 datagrams output
    75050 packets received
    8 packets to unknown port received.
    0 packet receive errors
    73905 packets sent


Socket buffer overrun info from netstat

Post by Carsten Ha » Fri, 04 Aug 2000 04:00:00

On Wed, 26 Jul 2000 12:16:09 -0700, Siva Saravanan Jayaraman

>Im trying to get some information about UDP packet drops, specifically,
>socket buffer overflows.

To make sure I get it right:
You want to seperate UDP from TCP, therefore something like
ifconfig -a, which gives you the number if packets dropped 'cause of
overrun, e.g.
eth0      Link encap:10Mbps Ethernet  HWaddr 00:40:05:12:C6:54
          inet addr:  Bcast: Mask:
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:2912854 errors:2048 dropped:0 overruns:0 frame:0
          TX packets:2706969 errors:30 dropped:0 overruns:1473 carrier:0
          Interrupt:15 Base address:0x340
really isn't enough?



1. socket buffer overrun??


I 'm sharing an Internet connection between 5 computers running Windows 98
and Redhat Linux. My gateway computer is a Linux box. Whenever I tried to
connect a Windows client to my Linux gateway or my Linux box to a Windows NT
server (which is my ISP) I only got very slow traffic speed of 50 - 60
bytes/sec though I have never had this problem before when I connected my
Windows machine to the Internet (with the same ISP, probably my ISP doesn't
support Linux !?). Here is the output from "netstat -s":

16979 total packets received
6238 forwarded
0 incoming packets discarded
353 incoming packets delivered
10486 requests sent out
17 fragments failed


15 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
echo replies: 15
79 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 79


120 active connections openings
0 passive connection openings
0 failed connection attempts
0 connection resets received
8 connections established
10329 segments received
10290 segments send out
43 segments retransmited
23 bad segments received.
100 resets sent


92 packets received
62 packets to unknown port received.
0 packet receive errors
100 packets sent


50 packets pruned from receive queue because of socket buffer overrun
16768 packets dropped from out-of-order queue because of socket buffer
overrun <-------------------

Has anyone experienced the same problem? Is there any sollution to this
problem or I have to come back to Microsoft stuff -(( ??

Nicole Nguyen

2. How to disable TCP's checksum

3. Need info about socket- and file-buffer architecture

4. Problem with fli4l

5. Buffer Overrun

6. Importance, or lack, of Marketshare?

7. receiver ring buffer overrun?

8. HELP!! I need a RH5.1 (in.ftpd) file

9. Buffer overruns on sio1 serial device?

10. Ring Buffer Overrun in NetBSD 1.3.1 Amiga

11. 5 additional buffer overruns in 2.5.48

12. Q: what is a serial buffer overrun?

13. Buffer overrun ?