From owner-freebsd-stable@FreeBSD.ORG Wed Oct 24 12:31:32 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA5DF3B3 for ; Wed, 24 Oct 2012 12:31:32 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (s1.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 5444B8FC08 for ; Wed, 24 Oct 2012 12:31:31 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id q9OCWqqx068658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Oct 2012 14:32:52 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <5087DFA1.7090001@omnilan.de> Date: Wed, 24 Oct 2012 14:31:29 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable Subject: every 2nd echo-request malformed when ping -s >4067 X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE123D7F3AAE59B77986FB575" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 12:31:32 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE123D7F3AAE59B77986FB575 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, while checking new mtu9k-setup, I discovered that ping has some odd behaviour. If I use payloadsize > 4067, every 2nd icmp-echo-request seems to be malformed: ping -s 4068 -D 10.5.49.65 1st: 12:21:09.048447 IP 10.5.49.126 > 10.5.49.65: ICMP echo request, id 46597, seq 0, length 4076 0x0000: 4500 1000 0f2d 4000 4001 a507 0a05 317e 2nd: 12:21:10.052891 IP 10.5.49.126 > 10.5.49.65: icmp 0x0000: 4500 1000 0f2d 0040 4001 e4c7 0a05 317e 3rd: 12:21:11.062900 IP 10.5.49.126 > 10.5.49.65: ICMP echo request, id 46597, seq 2, length 4076 0x0000: 4500 1000 0f2d 4000 4001 a507 0a05 317e 4th: 12:21:12.072915 IP 10.5.49.126 > 10.5.49.65: icmp 0x0000: 4500 1000 0f2d 0040 4001 e4c7 0a05 317e 5th: 12:21:13.082900 IP 10.5.49.126 > 10.5.49.65: ICMP echo request, id 46597, seq 4, length 4076 0x0000: 4500 1000 0f2d 4000 4001 a507 0a05 317e When payload is 4076, outgoing _every_ outgoing request begins with 4500 xxxx xxxx 4000 4001, while above we see every second request starting with 4500 xxxx xxxx 0040 4001. Does anybody know header composing off pat? Haven't seen these bits for quiet some time... Thanks, -Harry --------------enigE123D7F3AAE59B77986FB575 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlCH36EACgkQLDqVQ9VXb8gqywCgjo7J0HbTeyd66wdPv+d9gKMo jXEAoMQv3EQFeyCgDThAy8wcxbM7V9Vr =xLJf -----END PGP SIGNATURE----- --------------enigE123D7F3AAE59B77986FB575--