VLAN Tagging issues

J

jtabish

Guest
I've setup 2 bridges and assigned them to a KVM, vmbr0 is for untagged traffic and vmbr40 is for tagged voip traffic. Untagged uses 192.168.1.0/24 and Tagged uses 192.168.3.0/24

The problem so far is I can't ping the KVM from inside or outside the host on the tagged interface network but all untagged networks are fine, however the host can ping any other ip within the tagged network subnet other then the one that is assigned inside of the KVM for that subnet but the untagged subnet works fine.

Also from within the KVM I can ping any ip inside of the tagged subnet and vise-versa.

I've done a tcpdump on the guest kvm and I can infact see pings reaching the box but seems there not being replied to on the tagged subnet interface.

I'm running FreePBX inside of that guest.
 
I've setup 2 bridges and assigned them to a KVM, vmbr0 is for untagged traffic and vmbr40 is for tagged voip traffic. Untagged uses 192.168.1.0/24 and Tagged uses 192.168.3.0/24

The problem so far is I can't ping the KVM from inside or outside the host on the tagged interface network but all untagged networks are fine, however the host can ping any other ip within the tagged network subnet other then the one that is assigned inside of the KVM for that subnet but the untagged subnet works fine.

Also from within the KVM I can ping any ip inside of the tagged subnet and vise-versa.

I've done a tcpdump on the guest kvm and I can infact see pings reaching the box but seems there not being replied to on the tagged subnet interface.

I'm running FreePBX inside of that guest.

I think this is not about Proxmox. Check your routing tables.
 
I've setup 2 bridges and assigned them to a KVM, vmbr0 is for untagged traffic and vmbr40 is for tagged voip traffic. Untagged uses 192.168.1.0/24 and Tagged uses 192.168.3.0/24

The problem so far is I can't ping the KVM from inside or outside the host on the tagged interface network but all untagged networks are fine, however the host can ping any other ip within the tagged network subnet other then the one that is assigned inside of the KVM for that subnet but the untagged subnet works fine.

Also from within the KVM I can ping any ip inside of the tagged subnet and vise-versa.

I've done a tcpdump on the guest kvm and I can infact see pings reaching the box but seems there not being replied to on the tagged subnet interface.

I'm running FreePBX inside of that guest.
Hi,
some people has issues with mixed traffic on one interface (tagged and untagged). I use only tagged vlans on an interface and this works without trouble.

Udo
 
I think you may be right and it might be a freepbx related issue cause it seems that it only happens when I assign the 2nd nic a address. Then again I haven't tested this with any other kvm's I have running by adding a 2nd nic and sending it tagged traffic.

Anyways my solution was to just send tagged traffic over 1 nic for now
 
Well I thought it may have been a mixed thing as well so I set both interfaces to use tagged vlans and the problem still persisted so I was able to determin that was not the issue here.

I'm going to just set this as a freepbx issue as its all I can figure out it being at the moment cause even tcpdump on the pbx box shows the ping requests coming but there just not being replied to so its something on the guest box it self causing the issue.
 
I use a bridge for each vlan and I run freepbx on a bridge that carries that vlan. It works wonderfully

Sent from my Nexus 5
 
Yes I was using 2 bridges, vmbr0 for untagged and vmbr1 for tagged traffic to my freepbx kvm but for whatever reason the tagged interface was not pingable from outside of the kvm but the network the tagged traffic belonged to was working within the kvm just fine for all other tagged devices of the same vlan yet I run pfsense so intervlan communication should be working just fine as it is with all other tagged vlans not associated with the freepbx box specifically.
 
I built some changes for proxmox and i will send it to proxmox. Tagging isn't easy if you using some bridges, so you must do following:

------------/-> vmbr0.100 -> vmbr0v100 -> VM2 (Tag 100)
eth0 -> vmbr0 -> VM1 (untagged)
------------\-> vmbr0.200 -> vmbr0v200 -> VM3 (Tag 200)

I changed the proxmox files to create this case automatically, it select the bridge an create a tagged device on this bridge and add a new bridge for the VMs. This change can be done in Network.pm to remove the other tagging mode with this. But it must be also changed the GUI, QemuServer, Qemu and to implement it both solution fully.
 
Last edited:
Well I thought it may have been a mixed thing as well so I set both interfaces to use tagged vlans and the problem still persisted so I was able to determin that was not the issue here.

I'm going to just set this as a freepbx issue as its all I can figure out it being at the moment cause even tcpdump on the pbx box shows the ping requests coming but there just not being replied to so its something on the guest box it self causing the issue.

Try to run tcpdump on both interfaces at the same time and I guess I are going to be surprised.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!