Hi,
I have a PVE host with a network trunk to it, that is causing me issues with VMs running on VLAN1.
I know running things on VLAN1 is not ideal, but there are some legacy items that cant be moved right now - long story.
The rest of the VLANs are working just fine, and the VMs there can communicate across VLANs and such - but just not the VMs running on VLAN1.
This is the interfaces config:
I tried with both VLAN1 tagged and untagged on the VMs, but that didnt really change anything.
What am i doing wrong?
I have a PVE host with a network trunk to it, that is causing me issues with VMs running on VLAN1.
I know running things on VLAN1 is not ideal, but there are some legacy items that cant be moved right now - long story.
The rest of the VLANs are working just fine, and the VMs there can communicate across VLANs and such - but just not the VMs running on VLAN1.
This is the interfaces config:
Code:
root@dk1pve02:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface enx7cc2c6464727 inet manual
iface enp3s0 inet manual
auto vmbr0
iface vmbr0 inet static
bridge-ports enx7cc2c6464727
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 1-4094
auto vmbr0.10
iface vmbr0.10 inet static
address 192.168.10.22/24
gateway 192.168.10.1
iface wlp4s0 inet manual
I tried with both VLAN1 tagged and untagged on the VMs, but that didnt really change anything.
What am i doing wrong?