Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • To answer your questions. The terminology I have seen in reference to grouping LAN interfaces in projects like opnsense and openwrt is bridging. The idea was to have ports 1 to 4 in the same IP range with port 5 handling a separate range for an AP. The OpenBSD documentation in my first link shows that a bridge would accomplish this and then mentions that PF can then filter on the bridge. Perhaps a trunk may be closer to what I want. Ultimately the goal is for communication between LAN devices and segregation of the AP devices. I know I’ll eventually have to add pf rules to segregate the AP Commented Jun 29, 2022 at 18:02
  • A veb is a newer form of bridge that appears to be more performant: kernelpanic.life/hardware/openbsd-veb-vs-bridge-benchmarks.html Commented Mar 5, 2023 at 14:20
  • @jwillikers yes, but there are more differences that just performance, it isn't a different implementation of the same thing. Crucially, veb works on Layer 2, while bridge works on Layer 3. This means that members of veb bridges become independent from the network stack and are "taken over" by the bridge. See the man page for veb for details. Commented Mar 6, 2023 at 8:36