kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly
Mark Linimon
linimon at lonesome.com
Fri Jun 28 20:00:02 UTC 2013
The following reply was made to PR kern/179901; it has been noted by GNATS.
From: Mark Linimon <linimon at lonesome.com>
To: bug-followup at FreeBSD.org
Cc:
Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled
incorrectly
Date: Fri, 28 Jun 2013 14:55:38 -0500
----- Forwarded message from Bernd Walter <ticso at cicely7.cicely.de> -----
Date: Fri, 28 Jun 2013 12:15:14 +0200
From: Bernd Walter <ticso at cicely7.cicely.de>
To: linimon at freebsd.org
Cc: freebsd-bugs at freebsd.org, freebsd-net at freebsd.org
Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled incorrectly
User-Agent: Mutt/1.5.11
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
--
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
----- End forwarded message -----
More information about the freebsd-net
mailing list