Hi there,
I'm currently evaluating VMWare Workstation 12 (14 doesn't work on my hardware ... and new hardware currently isn't an option ...) and I tried to get a VLAN-Trunk into a VM guest machine (Ubuntu 16.04 64 bit). The host machine is also running Ubuntu 16.04 64 bit (with 2xXeon4C with VT-X).
I want to put the guest machine into many different VLANs/subnets without having to bridge all the VLANs seperately on VMNet interfaces (eventually there will be more than the available 9 interfaces, btw.)
My problem now is that this simply doesn't work. When I bridge the host interface (which is connected to a trunk port) - let's say eth1 - into the guest machine and add VLANs there (i.e. ens32.104 etc.), the interfaces show up, have IP addresses etc. in the guest, but I can't ping the outside world (also not the host). When, on the other hand, I only bridge one specific VLAN (eth1.104 on the host) into the guest and configure it accordingly (ens32), everything works fine.
I noted from another post that VLAN tags might only be forwarded to the guest if the physical interface isn't used by the host itself. So I also tried with two NICs making sure that the physical interface being bridged into the guest (ETH0 this time) doesn't have an IP address assigned and that no VLANs are configured on ETH0 on the host machine (and yes, both interfaces - ETH0 and ETH1 - are connected to a trunk port on a Cisco switch). Still, alas, no success. The guest machine stays "isolated" with its VLANs (emulated device in the guest is an e1000, btw.)
Does anybody have any idea if this is supposed to work at all (complete VLAN-trunk into a guest with VMWare workstation) and if so how this can be accomplished?
Thank you very much in advance for any light you might be able to shed on this.
Sascha