Date: Fri, 10 Oct 2025 02:17:08 -0400 From: Paul Procacci <pprocacci@gmail.com> To: Paul Procacci <pprocacci@gmail.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: FBSD 15 :: if_bridge help needed Message-ID: <CAFbbPui_Row=voSgcnGzmFOx=Pg6Vn7kVTjvyriTg6nNU3DCKQ@mail.gmail.com> In-Reply-To: <aOYeZ3jyN2lX5WXn@amaryllis.le-fay.org> References: <CAFbbPuiq1bZEMdsGvk=asfn8efszrb6pofa%2B4o86x=E4cLpdng@mail.gmail.com> <F13F0E41-39D5-48BA-A615-354C5A4B9D52@punkt.de> <aOYOvGARWUkFwpQu@amaryllis.le-fay.org> <CAFbbPuiX=uzsrH8u=2%2B0=dEmPU1cg7SX5AwYz=hXM=4KPCrE_A@mail.gmail.com> <aOYVVnEp9LfJk-R9@amaryllis.le-fay.org> <CAFbbPuhiLsWcjbVD9F_RH%2BQ%2B5b2BZcAnLK2h3AqiJjkcOkxaMQ@mail.gmail.com> <aOYZ2BzsGjwKaa6h@amaryllis.le-fay.org> <CAFbbPujAyu=Xy-CE-WM%2BHdUVcJ_yXC-M1OZPFugHa_S3P_s3EA@mail.gmail.com> <CAFbbPuhuDtOH7t=a8EtDxHhHsqZWfLUe5vsD0XsJG6KF%2BHYKfQ@mail.gmail.com> <aOYeZ3jyN2lX5WXn@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 8, 2025 at 4:18 AM Lexi Winter <ivy@freebsd.org> wrote:
>
> Paul Procacci wrote in <CAFbbPuhuDtOH7t=a8EtDxHhHsqZWfLUe5vsD0XsJG6KF+HYKfQ@mail.gmail.com>:
> > Problem fixed. I feel so ashamed.
> > While epair0b.60 was up ... epair0b wasn't.
> > A stupid stupid oversight.
> >
> > Thanks again for all the help and attention. And sorry for the noise.
> > I owe ya'll a beer if we ever cross paths.
>
> no worries, i'm glad you fixed it and i appreciate someone actually
> testing the new bridge code in a real environment :-)
So after being up till 4am last night and making a stupid mistake like
forgetting to bring up an interface, I still feel there's something
amiss but w/ something entirely different.
Without getting into the gory details... just a simple question.
Say I have lagg0.
Say I have bridge0 w/ vlanfilter enabled.
.. and say I place the lagg into that bridge via `ifconfig bridge0
addm lagg0 tagged 1843'.
The above by itself doesn't provide access to the host because well,
there's no ip or anything assigned anywhere.
It should however provide a trunk carrying vlan 1843 to the bridge0 interface.
Alright, so what's the correct method here for getting the host
assigned an ip within that 1843 vlan.
Is it:
a) create a lagg0.1843 interface and assign an ip
b) create a bridge0.1843 interface and assign an ip
I'm presuming `b' as I've seen a few example here and there suggesting that.
As for testing:
192.168.35.1 -- Remote host
192.168.35.154 - Machine in question
>From remote host: tcpdump -n -e -ttt -i igc1 host 192.168.35.154
00:00:01.063499 58:9c:fc:10:6f:fa > 60:be:b4:01:bf:0d, ethertype IPv4
(0x0800), length 98: 192.168.35.154 > 192.168.35.1: ICMP echo request,
id 5948, seq 8, length 64
So I'm seeing untagged packets arriving when they should be tagged.
Machine in question:
----------------------------------
root@xxx:~ # ifconfig bridge0; ifconfig bridge0.1843
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP>
metric 0 mtu 1500
options=10<VLAN_HWTAGGING>
ether 58:9c:fc:10:6f:fa
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
bridge flags=1<VLANFILTER>
member: lagg0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 6 priority 128 path cost 2000000 vlan protocol
802.1q tagged 1843
groups: bridge
nd6 options=9<PERFORMNUD,IFDISABLED>
bridge0.1843: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
metric 0 mtu 1496
options=0
ether 58:9c:fc:10:6f:fa
inet 192.168.35.154 netmask 0xffffff00 broadcast 192.168.35.255
groups: vlan
vlan: 1843 vlanproto: 802.1q vlanpcp: 0 parent interface: bridge0
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
Any thoughts on this?
~Paul
__________
:(){ :|:& };:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPui_Row=voSgcnGzmFOx=Pg6Vn7kVTjvyriTg6nNU3DCKQ>