Date: Tue, 05 Oct 2021 09:35:06 +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-ATx279NFXq@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=3D243554 --- Comment #9 from Patrick M. Hausen <pmh@hausen.com> --- > 4. User should REMOVE IP from igb0 and ADD IP to the bridge (does not hav= e one by default) Yes! Yes! Yes! All IP addresses MUST be on the bridge interface and not on any member. FreeNAS/TrueNAS has been doing it wrong for years. The problem is with dynamically generated bridge interfaces of course. Most TrueNAS users won't notice, because there is not much in IPv4 that rel= ies on multicast. So it works, most of the time. With IPv6 things get interesti= ng ... If you plan to use VNET jails or VMs with tap and bridge, best practice is = to statically create the bridge at boot time via cloned_interfaces and configu= re IP accordingly. Then point your VM/jail orchestration tool at the existing bridge instead of having it create a new one. > > [ ... statement by Kristof ...] > Can you point me to this? Private conversation, but you can of course just ask him. That single statement in the handbook essentially says it all - but by far = not prominently enough, IMHO. Kind regards, Patrick --=20 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-ATx279NFXq>