From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 28 18:59:11 2013 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33A30D47; Fri, 28 Jun 2013 18:59:11 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id A6FFE1F9F; Fri, 28 Jun 2013 18:59:10 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id r5SIwwT2062840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 28 Jun 2013 20:58:58 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id r5SIwq79009269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jun 2013 20:58:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id r5SIwqVj071395; Fri, 28 Jun 2013 20:58:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id r5SIwq3C071394; Fri, 28 Jun 2013 20:58:52 +0200 (CEST) (envelope-from ticso) Date: Fri, 28 Jun 2013 20:58:52 +0200 From: Bernd Walter To: linimon@freebsd.org Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly Message-ID: <20130628185852.GA45651@cicely7.cicely.de> References: <201306240359.r5O3xO0g012449@freefall.freebsd.org> <20130628101514.GX45651@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130628101514.GX45651@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: ticso@cicely.de List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 18:59:11 -0000 On Fri, Jun 28, 2013 at 12:15:14PM +0200, Bernd Walter wrote: > On Mon, Jun 24, 2013 at 03:59:24AM +0000, linimon@freebsd.org wrote: > > Old Synopsis: [patch] Multicast SO_REUSEADDR handled incorrectly > > New Synopsis: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly > > > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > > Responsible-Changed-By: linimon > > Responsible-Changed-When: Mon Jun 24 03:59:05 UTC 2013 > > Responsible-Changed-Why: > > Over to maintainer(s). > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=179901 > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > I don't know if this is related or a different bug, but the same > mentioned commits are suspicious for us. > We had been running with our own IPv6 software into the same REUSEADDR > problem and changed to REUSEPORT as this is how it is done in mcastread > from mcast-tools port. > Don't know where we originally got the REUSEADDR from, probably a Stevens > book. > So far binding works with this change in our software. > However we only receive packets from network and not packets from > the host itself. > We use multicast to notify multiple processes on multiple machines, > including the machine itself. > To reproduce: > - use two hosts > - start mcastread on each of them on an interface with shared LAN > - send via mcastsend on one host > - packets are received on the other host, but not with the mcastread > on the same host 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.