61
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Jan 2024
61 points (96.9% liked)
Selfhosted
40330 readers
167 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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I think two NICs is required to do VLANing properly? Not 100% sure.
Nope - Proxmox lets you create VLAN trunks, just like a physical switch.
Edit: here's one of my Proxmox server network configs.
Huh, cool, thank you! I'm going to have to look into that. I'd love for some of my containers and VMs to be on a different VLAN from others. I appreciate the correction. 😊
No worries mate. Sing out if you get stuck - happy to provide more details about my setup if you think it'll help.
Thanks for the kind offer! I won't get to this for a while, but I may take you up on it if I get stuck.
Is there a reason to do this over just giving the nic for the vm/container a vlan tag?
You still need to do that, but you need the Linux bridge interface to have VLANs defined as well, as the physical switch port that trunks the traffic is going to tag the respective VLANs to/from the Proxmox server and virtual guests.
So,
vmbr1maps to physical interfaceenp2s0f0. Onvmbr1, I have two VLAN interfaces defined -vmbr1.100(Proxmox guest VLAN) andvmbr1.60(Phsyical infrastructure VLAN).My Proxmox server has its own address in vlan60, and my Proxmox guests have addresses (and vlan tag) for vlan100.
The added headfuck (especially at setup) is that I also run an OPNsense VM on Proxmox, and it has its own vlan interfaces defined - essentially virtual interfaces on top of a virtual interface. So, I have:
enp2s0f0(physical)vmbr1(Linux bridge)vmbr1.60(Proxmox server interface)vmbr1.100(Proxmox VLAN interface)vtnet1(OPNsense "physical" nic, but actually virtual)vtnet1_vlan[xxx](OPNsense virtual nic per vlan)All virtual guests default route via OPNsense's IP address in vlan100, which maps to OPNsense virtual interface
vtnet1_vlan100.Like I said, it's a headfuck when you first set it up. Interface-ception.
The only unnecessary bit in my setup is that my Proxmox server also has an IP address in vlan100 (via
vmbr1.100). I had it there when I originally thought I'd use Proxmox firewalling as well, to effectively create a zero trust network for my Proxmox cluster. But, for me, that would've been overkill.No, you can do more than 1 VLAN per port. It's called a trunk