Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Feb 2016 10:23:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-amd64@FreeBSD.org
Subject:   [Bug 207208] ping has a problem with fragmented replies
Message-ID:  <bug-207208-6-bGCARvlNux@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207208-6@https.bugs.freebsd.org/bugzilla/>
References:  <bug-207208-6@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207208

--- Comment #4 from Maxim Konovalov <maxim@FreeBSD.org> ---
Hello,

> # netstat -sp ip
> ip:
>         0 fragments received
{...]
>         22 datagrams that can't be fragmented
>
[...]

The above looks suspicious.  Here is what it should be:

# netstat -sz >/dev/null
# netstat -sp ip | grep frag
        0 fragments received
        0 fragments dropped (dup or out of space)
        0 fragments dropped after timeout
        0 output datagrams fragmented
        0 fragments created
        0 datagrams that can't be fragmented
# ping -qc 1 -s 2500 80.113.23.178
PING 80.113.23.178 (80.113.23.178): 2500 data bytes

--- 80.113.23.178 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev =3D 59.983/59.983/59.983/0.000 ms
# netstat -sp ip | grep frag
        2 fragments received
        0 fragments dropped (dup or out of space)
        0 fragments dropped after timeout
        1 output datagram fragmented
        2 fragments created
        0 datagrams that can't be fragmented

To test ip fragmentation withoug NAT you can simple run

ping -s 32000 -c1 127.0.0.1

and check stats above.

I still think that your NAT is culprit.

--=20
Maxim Konovalov

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207208-6-bGCARvlNux>