Homelab

380 readers

9 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

[email protected]

Should I assign all VLANs on a single port? (alien.top)

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

7 comments fedilink hide all child comments

First Homelab in the making and it’s been an wonderful process learning everything. I am using a Protectli 4 port device running pfSense, an 8 port UniFi managed switch and a Raspberry Pi Cluster for now. I have an IoT VLAN created for these devices on a singular port on top of my already configured LAN setup by default. If I decide to create more VLANs, which I’m sure I will, what interfaces should I assign them too. I am having a hard time finding literature on when to create a VLAN and if you do should you put multiple on one interface or create them on separate interfaces. Like igc0 has my IoT VLAN and LAN should my other VLANs go there or like igc2 for example. Sorry for the long message just curious about industry standards and best practices.

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

[–] [email protected] 1 points 11 months ago

Router -> all vlans (trunked / tagged) into managed switch, then you do the routing there. Thats how its done usually.

You can then assign ports of a switch to only accept/output a single vlan directly (untagged), so the devices dont need to be vlan aware. Or you output only needed vlans as tagged, for example for an accespoint or server.

You can do the same in virtual nerworks like inside proxmox, all vlans on one bridge and then set the VMs to single vlan