Friday, June 07, 2024

Re: VLAN-tagging - follow-up

Hello Martin,

Make sure you adhere to the docs: https://www.openbsd.org/faq/faq6.html#Bridge
You need to rename vlan101 to the vether101 (for example) interface.

You will need a separate bridge interface per vlan if you want to keep layer 2 separated.

First try to test the bridge without pf, and then isolate the problem to pf.

On Fri, Jun 7, 2024 at 5:06 AM Martin <iio7@protonmail.com> wrote:
Are you supposed to "bridge" the vlan with the physical interface?

I have:

$ cat /etc/hostname.em0
up

$ cat /etc/hostname.vlan101
vnetid 101 parent em0
inet autoconf
up

In /etc/pf.conf I have replaced em0 with vlan101 for ext_if.

I get "No route to host" if I try to ping something, etc.

But if add:

$ cat /etc/hostname.bridge0
add vlan101
add em0
up

Then it works.

Was the bridge part missed in the previous emails about how to use
VLAN-tagging or am I missing something?



--
Wouter Prins
wp@null0.nl

No comments:

Post a Comment