From owner-freebsd-net@FreeBSD.ORG Fri Jun 28 20:00:05 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B4DE1EC0 for ; Fri, 28 Jun 2013 20:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A7898127B for ; Fri, 28 Jun 2013 20:00:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5SK05vO098649 for ; Fri, 28 Jun 2013 20:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5SK05AX098647; Fri, 28 Jun 2013 20:00:05 GMT (envelope-from gnats) Date: Fri, 28 Jun 2013 20:00:05 GMT Message-Id: <201306282000.r5SK05AX098647@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Mark Linimon Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Linimon List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 20:00:05 -0000 The following reply was made to PR kern/179901; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly Date: Fri, 28 Jun 2013 14:56:07 -0500 ----- Forwarded message from Bernd Walter ----- Date: Fri, 28 Jun 2013 20:58:52 +0200 From: Bernd Walter To: linimon@freebsd.org Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly User-Agent: Mutt/1.5.11 It is unrelated, but I have found the cause for it and filed kern/180065 together with a working patch. The reason is that the packets have no valid checksums when processed in ip6_input because of delayed checksum changes. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ----- End forwarded message -----