From owner-freebsd-bugs Fri Jan 21 10:20: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 42027154CC for ; Fri, 21 Jan 2000 10:20:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA62926; Fri, 21 Jan 2000 10:20:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 21 Jan 2000 10:20:04 -0800 (PST) Message-Id: <200001211820.KAA62926@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ruslan Ermilov Subject: Re: kern/16240: ICMP error generation fails to correctly insert IP ID on returned packet Reply-To: Ruslan Ermilov Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16240; it has been noted by GNATS. From: Ruslan Ermilov To: Kannan Varadhan Cc: kannanv@research.bell-labs.com, Garrett Wollman , freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/16240: ICMP error generation fails to correctly insert IP ID on returned packet Date: Fri, 21 Jan 2000 20:15:19 +0200 On Fri, Jan 21, 2000 at 12:12:53PM -0500, Kannan Varadhan wrote: > Excuse me for being stupid here, but what does ping from SCO hosts have > to do with how freebsd behaves? Here's a different synopsis of the bug: > Ping from SCO differ in that SCO sets DF bit in ICMP packets, which triggers the same bug as you observe (the bytes in ICMP response packets appear in the host order). -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message