Re: VLAN-tagging, how?

Add to hostname.vlan101 as well:

autoconf
up

Remove dhcp/autoconf from hostname.em0 but make sure there is an 'up' in there.

If you are using a macro like $ext_if in pf, just change from em0 to vlan101 and all your external interface rules will work like they did before.

Cheers

Sent from my iPhone

> On 31 May 2024, at 1:28 PM, Martin <iio7@protonmail.com> wrote:
>
> Would this be adequate?
>
> /etc/hostname.vlan101
> vlandev em0 vnetid 101
>
> em0 is the physical interface connected to the fiber box,
> it is then setup to get an IP via DHCP.
>
> Does vlan101 need to be addressed in PF in any way or are
> the rules which currently work for em0 enough?
>
>> Sorry for the non-inline text.
>>
>> OpenBSD makes this super simple and it is well documented. The flow is to bring up your physical interface and then use that as a parent for your pseudo vlan interface.
>>
>> man ifconfig
>>
>> Move down to the VLAN section and it is well described to provide you with the options you need.
>>
>> Any clarification just yell out. Cheers.
>>
>> Sent from my iPhone
>>
>>>> On 31 May 2024, at 8:15 AM, Martin iio7@protonmail.com wrote:
>>>
>>> I am currently using a home made router with OpenBSD which is connected
>>> directly to my ISP's fiber router. The OpenBSD router is setup with a
>>> fixed IP on the WAN port and I do internal NAT etc.
>>>
>>> In about a month a new ISP is going to provide internet via the fiber
>>> and they are changing the equipment.
>>>
>>> What they have told me is that in order to use my own router, the
>>> router has to support VLAN tagging.
>>>
>>> The statement I got was:
>>>
>>> "We send traffic out on VLAN 100 so your router needs to be tagged to
>>> 100. Then all it has to do is to get an IP via DHCP."
>>>
>>> I have not done any VLAN stuff before and I am unsure exactly how to do
>>> this.
>>>
>>> Is this possible and how exactly is that done?
>>>
>>> Thanks.
>