Search results

@cyrus104, I'm now back to my original network configuration which includes the vlan aware bridge. In my current setup I have two network ports which are bonded and used in the guest bridge. If you're looking to use the physical port directly in your bridge you can probably bridge_ports line to...

The switch port sends all vlans to the host machine. I do wonder about what may have happened on the network however. The last work which took place was a firmware upgrade and a firewall update. At this point it certainly sounds like something wonky/embarrassing may be going on. Let's review...

I just tried this with VLAN AWARE disabled. No dice. I'm thinking I may try to build a fresh node and see if I get any different results there. If this were to work I still wonder which way would be the best practice: Original configuration, or this configuration with the vlan aware disabled?

I thank you for trying. I have not yet tested a network configuration without VLAN aware. I'll give it a go this evening.

Okay, i'm now on 5.4.27-1-pve. No change in guest vlan connectivity. As a side note: For the past few tests I had been using a vm which was created on VLAN 8 specifically for testing these connectivity issues. I don't recreate the VM for each test. I'm not sure if that would have much of an...

TEST 1: Adjust vid range on bridge configuration Edit /etc/network/interfaces bridge_vids 2-4094 -> bridge_vids 2-10 Started a guest VM on VLAN 8 OBSERVATIONS: Guest VM did not get assigned and IP by the local DHCP server After manually assigning an IP to the same NIC, guest VM could not...

NICs: Intel 82574L TEST: I added the following to /etc/network/interfaces bridge_vids 2-4094 OBSERVATIONS: [NO CHANGE] New VMs have no connectivity I noticed that I can create VMs which connect to VLAN 5. I expect this is because of the vmbr0.5.

Hello, I recently upgraded to 6.1 and noticed that none of my new VMs can connect to any VLAN. There were no changes to the network environment. (this is my homelab - fyi) Kernel: 5.3.18-3-pve Proxmox: 6.1-8 Here are some things I've tried: Booting an older kernel Physically disconnecting...