Selfhosted

39484 readers

429 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Opnsense and one ethernet port (lemmy.sdf.org)

submitted 7 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

Hi,

I believe with just one port for opnsense (on a min-pc) we can still do vlans (with tagging I believe?) but how effective is that for segregating and isolating proxmox machines?

Say I want to keep a VPN machine isolated, from other virtual machines? How would you do that? Do you have any tips for running such a system?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 7 months ago* (last edited 7 months ago) (1 children)

Your opnsense will have WAN (ethernet port) and your LAN side will be all virtualized. There's no problem having VLAN 10 with 192.168.10.0/24 for your main vms and then VLAN 20 with 192.168.20.0/24 for your VPN machine. Setup deny rules in the firewall to stop the VLANs from communicating.
If this is inside your current home network you will end up with double NAT though.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

If the opnsense interface on the WAN VLAN has a public routable IP address there shouldn't be a problem with double NAT. Double NAT should only be a problem if they have a crappy ISP that's using CGNAT.

Edit: never mind, I reread your comment. We're saying the same thing essentially.