Recent content by harry0

Perhaps also worth noting that if I set port 28 (eno1) to TAGGED, I can access the host on .206, .207 and .208, but not on .209 - this seems to make sense since .209 is the Linux VLAN operating through vmbr1, which is not VLAN aware.

I have a very simple networking setup, as below: auto lo iface lo inet loopback iface eno1 inet manual #port 28 auto eno2 iface eno2 inet manual #port 27 auto vmbr0 iface vmbr0 inet static address 192.168.5.206/24 gateway 192.168.5.1 bridge-ports eno1...

OK, I worked this out eventually - for anyone coming here with a similar problem, I had to remove the IP address from the bridge to get the node to use the VLAN interface. I don't think this is intuitive behaviour when both interfaces have different IPs? Ideally, I would have liked to be able to...

As additional info, TCPdump shows packets getting to the bridge when I activate tagged mode on the relevant switch ports: root@pve:~# tcpdump -i vmbr0 -n -e vlan 10 13:56:11.044406 18:3e:ef:c9:16:ff > ec:b1:d7:8b:1e:30, ethertype 802.1Q (0x8100), length 66: vlan 10, p 0, ethertype IPv4...

I did a little more experimenting and changed the VLAN id to 11 (which is unused / no other devices) and I can still access the gui and SSH from VLAN 10 via the IP assigned to the VLAN (192.168.5.206) while the port is an untagged member of VLAN 10, which I would not expect to have been able to...

I've recently set up a Proxmox node with a pretty straightforward networking setup - 2x LACP bonded 10GbE interfaces with a handful of VLANs. I have set up my interfaces as below: auto lo iface lo inet loopback auto eno1 iface eno1 inet manual auto eno2 iface eno2 inet manual auto bond0...