Date: Tue, 05 Oct 2021 01:54:05 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 243554] multicast packets not seen on PHY bridge member Message-ID: <bug-243554-7501-YwRLbA1x1V@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243554-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-243554-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554 --- Comment #8 from James Blachly <james.blachly@gmail.com> --- (In reply to Patrick M. Hausen from comment #7) >You must not put IP addresses on bridge member interfaces. All addresses must go on the bridge. > This is documented in the handbook page for bridging: > https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-bridging >> If the bridge host needs an IP address, set it on the bridge interface, not on the member interfaces. > I don't know if this already fixes your problem or if there is still a bug preventing multicast from working, but your setup is definitely wrong if you have an IP address on a member interface. So that I am 100% clear, are you suggesting the following: 1. Physical interface, say, igb0 exists and passes traffic on the lan 2. User desires to create bridge for use with bhyve 3. User/bhyve accessory software creates bridge, adding igb0 as member and tap0...N for M Virtual machines 4. User should REMOVE IP from igb0 and ADD IP to the bridge (does not have one by default) ? > Kristof Provost has confirmed that putting an IP address on a member IF breaks multicast! Can you point me to this? Regards -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243554-7501-YwRLbA1x1V>