Timeline for Bridging Ethernet Interface on OpenBSD and Other Problems
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2023 at 8:36 | comment | added | Zé Loff |
@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.
|
|
| Mar 5, 2023 at 14:20 | comment | added | jwillikers | A veb is a newer form of bridge that appears to be more performant: kernelpanic.life/hardware/openbsd-veb-vs-bridge-benchmarks.html | |
| Jun 29, 2022 at 18:02 | comment | added | user474102 | 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 | |
| Jun 29, 2022 at 10:57 | history | answered | Zé Loff | CC BY-SA 4.0 |