From owner-freebsd-amd64@freebsd.org Tue Feb 16 10:23:13 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FE86AAA9CD for ; Tue, 16 Feb 2016 10:23:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2128B1309 for ; Tue, 16 Feb 2016 10:23:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1GANC2t065896 for ; Tue, 16 Feb 2016 10:23:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207208] ping has a problem with fragmented replies Date: Tue, 16 Feb 2016 10:23:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maxim@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 16 Feb 2016 12:03:05 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2016 10:23:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207208 --- Comment #4 from Maxim Konovalov --- 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.=