Giving VLANs a readable name?

[nielsbasjes]

I installed the Proxmox VE on a physical system in my homelab last week for the first time (so I'm a noob in this tool stack).
I know quite a bit about networking, but I'm not a networking expert/professional.
I've used both VMWare ESXi and XCP-NG for quite some time to do experiments in my homelab, a collegue recommended me to try this out.

When I want to try a tool which I want to be isolated;
- I create a VLAN in my Unifi setup with firewalling and routing.
- Then because I let my VM server see all VLANs I can then define a "port group in ESXi" or "network in XCP-NG", link this to a specific vlan number and give it a human readable name.
- Then while creating a VM I then only have to attach the network interface of the VM to this named network.

Key point here; I do not have to remember the VLAN id because I have been able to give it a readable name.

Now for Proxmox VE; all the tutorials and documentation I have seen so far requires me to remember the actual VLAN id when creating a VM.

My question: Is there a way so I can create a named network/vlan that makes it easier to select the right network?

 

[janus57]

Hello,

My question: Is there a way so I can create a named network/vlan that makes it easier to select the right network?

why not putting this in the "comment" section of the interface ?

Best regards,
janus57

 

[spirit]

I installed the Proxmox VE on a physical system in my homelab last week for the first time (so I'm a noob in this tool stack).
I know quite a bit about networking, but I'm not a networking expert/professional.
I've used both VMWare ESXi and XCP-NG for quite some time to do experiments in my homelab, a collegue recommended me to try this out.

When I want to try a tool which I want to be isolated;
- I create a VLAN in my Unifi setup with firewalling and routing.
- Then because I let my VM server see all VLANs I can then define a "port group in ESXi" or "network in XCP-NG", link this to a specific vlan number and give it a human readable name.
- Then while creating a VM I then only have to attach the network interface of the VM to this named network.

Key point here; I do not have to remember the VLAN id because I have been able to give it a readable name.

Now for Proxmox VE; all the tutorials and documentation I have seen so far requires me to remember the actual VLAN id when creating a VM.

My question: Is there a way so I can create a named network/vlan that makes it easier to select the right network?

you can use the sdn feature at datacenter level, and created a vlan zone with named "vnets".

 

[nielsbasjes]

you can use the sdn feature at datacenter level, and created a vlan zone with named "vnets".

Thank you!

I created a vlan zone simply called "Networks"
Then while creating a VNet when I hook it into this "Networks" zone it asks for the vlan tag.
I did not create a subnet in any of them because I want Unifi to be in the lead there.
Then in the network interface dialog of a VM I simply see "vmbr0" and all the VNets I have defined as possible Bridge values.

I have done some testing and this is exactly what I wanted.