Change Host ip management in order to have VLAN tagged on it ?

[atec666]

Is it possible to do that with WEBGUI ?
because if i do what it is in the wiki, it gave me a Type : unknow. But VLAN is working perfectly.
But i can't access VM or CT console : Why ? is it normal ?

i need to isolate proxmox hypervisor from CT, VM (user network) mut not see hypervisor etc (we have an admin netowk for hypervisor).

The only way to do that is to put management ip and his nic on a VLAN. (vlan aware not working very welling with tagged switch) my switch is tagged : like below

VLAN on the Host

To allow host communication with an isolated network. It is possible to apply VLAN tags to any network device (NIC, Bond, Bridge). In general, you should configure the VLAN on the interface with the least abstraction layers between itself and the physical NIC.

For example, in a default configuration where you want to place the host management address on a separate VLAN.

Example: Use VLAN 5 for the Proxmox VE management IP with traditional Linux bridge
auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno1.5 inet manual

auto vmbr0v5
iface vmbr0v5 inet static
address 10.10.10.2
netmask 255.255.255.0
gateway 10.10.10.1
bridge_ports eno1.5
bridge_stp off
bridge_fd 0

auto vmbr0
iface vmbr0 inet manual
bridge_ports eno1
bridge_stp off
bridge_fd 0

 

[atec666]

Is this type of config supported by promox ? (host management on VLAN)

 

[taurus]

hello everyone,
i'm also trying to segment my network with vlans.
but i have the same problem as atec666.



and in none of the VMs or LXC containers i get the VLANs to run.
neither via the VLAN TAG nor via VLAN configuration within the guest.

what am I doing wrong?
on the switch the connected port is tagged and not untagged

 

[Moayad]

Hi,

and in none of the VMs or LXC containers i get the VLANs to run.
neither via the VLAN TAG nor via VLAN configuration within the guest.

what am I doing wrong?
on the switch the connected port is tagged and not untagged

This is an bug we will fix it soon.

https://bugzilla.proxmox.com/show_bug.cgi?id=2711


But you can change name vmbr0v10 to vmbr10 should works

 

[taurus]

Hi,

This is an bug we will fix it soon.

https://bugzilla.proxmox.com/show_bug.cgi?id=2711

But you can change name vmbr0v10 to vmbr10 should works

Sorry Moayad, I had not seen the other forum post.

but now it runs as desired:



thank you very much