Thank you all very much for the setup examples, very helpful!
On Fri, May 31, 2024 at 1:20 PM Zé Loff wrote:
> On Thu, May 30, 2024 at 10:12:12PM +, Martin 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
On Thu, May 30, 2024 at 10:12:12PM +, Martin 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
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
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
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
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
7 matches
Mail list logo
