Discussion:
[Bug 247912] [if_bridge] IPv6 ndp does not work across local bridge members
b***@freebsd.org
2021-04-23 05:48:57 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

Martin Birgmeier <***@aon.at> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|12.1-RELEASE |12.2-RELEASE
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 05:57:11 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

--- Comment #19 from Martin Birgmeier <***@aon.at> ---
I'd like to come back to this issue.

Basically, I am (still :-)) not assigning the IP addresses to the bridge
interface. The major reason for this is that I am assembling/disassembling the
bridge and its member interfaces as needed, and I do not want to always have to
fiddle with reassigning IP addresses from the member interfaces to the bridge
and vice versa.

Which brings me to my point: In normal networking parlance a bridge knows
nothing about ISO layer 3 and therefore not about IP. Much less it gets an IP
address assigned (let us not digress to smart managed devices). So I believe
that we have a design issue here: In FreeBSD we are talking about a "bridge"
but in reality it is kludge used to tie some interfaces together. Or at least
it is not a bridge in the traditional networking sense.

How difficult would it be to redesign the bridge abstraction in FreeBSD to more
closely resemble a real layer 2 bridge?

-- Martin
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 10:35:12 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

Lutz Donnerhacke <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org

--- Comment #20 from Lutz Donnerhacke <***@FreeBSD.org> ---
There are two bridge implementations in FreeBSD. The classical one you are
using. And the netgraph one ng_bridge, which is much simpler. If you have a
problem with the classical one, would you mind to give the ng_bridge a try? You
may assign ng_eiface virtual interfaces to it, if necessary.

I'm just curious to know which part of the classical bridge is the problematic
part.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 13:45:24 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

--- Comment #21 from Martin Birgmeier <***@aon.at> ---
Hi Lutz,

It seems I would need FreeBSD 13 for this, right? - I am still at 12.2

-- Martin
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 13:57:35 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

--- Comment #22 from Lutz Donnerhacke <***@FreeBSD.org> ---
The ng_bridge(4) node type was implemented in FreeBSD 4.2.

I bet it will work in 12.x, too.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 14:24:59 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

--- Comment #23 from Martin Birgmeier <***@aon.at> ---
Isn't https://reviews.freebsd.org/D24620 needed for this?
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-23 14:33:57 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912

--- Comment #24 from Lutz Donnerhacke <***@FreeBSD.org> ---
Oh, it might be necessary for bhyve VMs. I'm not familiar with this part. I
thought about connecting "real" interfaces like eiface inside the VM.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...