Date: Fri, 24 Jan 2020 03:12:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 243554] multicast packets not seen on PHY bridge member Message-ID: <bug-243554-227-X63stIX2RS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243554-227@https.bugs.freebsd.org/bugzilla/> References: <bug-243554-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554 --- Comment #3 from Kyle Evans <kevans@freebsd.org> --- Created attachment 211002 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211002&action=edit diff against releng/12.1 It looks similar to some of the other observability problems I've fixed in the past. While the conventional setup is that the bridge alone would get the IP and not igb1, I think being able to observe the packets in question on igb1 is still important for debugging purposes. There's also an incorrect looking comment in if_bridge.c that I'll dig into a little later; in bridge_forward(), we claim that tapping multicast/broadcast traffic isn't important because it will be reinjected into ether_input. I can't see how this is true. AFAICT these packets will travel bridge_broadcast() -> bridge_enqueue() -> if_transmit OR just bridge_enqueue() -> if_transmit, which will typically not involve ether_input. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243554-227-X63stIX2RS>