From owner-freebsd-net@FreeBSD.ORG Thu May 14 03:40:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DB1B106568A for ; Thu, 14 May 2009 03:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2DE8FC14 for ; Thu, 14 May 2009 03:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4E3e3Tm002797 for ; Thu, 14 May 2009 03:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4E3e3Qm002796; Thu, 14 May 2009 03:40:03 GMT (envelope-from gnats) Date: Thu, 14 May 2009 03:40:03 GMT Message-Id: <200905140340.n4E3e3Qm002796@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Chris Buechler Cc: Subject: Re: kern/127528: [icmp]: icmp socket receives icmp replies not owned by the process. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chris Buechler List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 03:40:03 -0000 The following reply was made to PR kern/127528; it has been noted by GNATS. From: Chris Buechler To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/127528: [icmp]: icmp socket receives icmp replies not owned by the process. Date: Wed, 13 May 2009 23:08:05 -0400 A brief addition to Seth's update on this issue, which should provide adequate detail. We switched from fping to the stock FreeBSD ping, and it made the issue better, but we're still seeing problems with FreeBSD's ping. In many circumstances it never appears, in others it's very easy to replicate. There isn't any commonality between environments that can replicate it, it happens across many types of NICs, using VLANs and not, etc. We should be able to arrange access to one of the systems that can routinely replicate the problem for an interested FreeBSD developer. We're in a bit over our heads here and not sure how to troubleshoot further. thanks, Chris