- #Vmware player the network bridge is not running upgrade
- #Vmware player the network bridge is not running pro
In the rest of the capture, all the traffic from the virtual machine is going out of the host adapter with the MAC address of the host machine. However, it then gets no communication with the wireless network. Our DHCP server will then happily give out a different IP address to the VM and the VM picks this up and configures it. Looking at the DHCP request grabbed on the host (from Wireshark), they have a source MAC address being that of the burned-in address of the real wireless card but with the client MAC address of the VM in the DHCP request itself. Looking at the DHCP request in the VM (using tcpdump at the Linux shell), the messages go out with the source MAC address of the packet being the virtual MAC of the VM and the client MAC address in the DHCP request itself being the same. However, the VM fails to communicate with the network (I can't ping the gateway or otherwise communicate). I'm connecting to an 802.1X based network (eduroam) and this time I can DHCP the VM and receive a different IP address to the host machine, so no address clash there (although the clash was what was reported to us at the time).
#Vmware player the network bridge is not running pro
I can't remember what tests I did at the time, but I've just had another look at this on a MacBook Pro running 10.8.5 and VMware 6.0.0 Professional with an Ubuntu Linux 12.04.2 LTS VM in bridged mode. Has something changed (perhaps tightening up a hole) or is this a coincidence?
#Vmware player the network bridge is not running upgrade
The user reports the problem starting since the upgrade to 6.2 - I can't find anything in the release notes to 6.2 which describe a behaviour change. Is there somewhere I can look to see the specific problem?
I remember reading that Bridge Mode was incompatible with the "enforce-dhcp" option - I'm guessing because the virtual MAC address doesn't match the outside MAC address and there are problems with the ARP requests probing if the IP address is already in use.Īm I still right in thinking that? I can't find anything specifically about it in the ArubaOS 6.2 documentation, so I'm not sure where I read it. The problem goes away when the VM's networking is switched from Bridge Mode to NAT/Shared Mode. This happens on Parallels Desktop (the user) and VMware Fusion (me). Last week we upgraded to 6.2.1.2 and have had a user report (and we've observed) an IP address clash reported on the VM running Windows: the clashing MAC address is that of the host computer (according to the Windows Event Log).
We enabled "enforce-dhcp" in our AAA profiles when we upgraded to ArubaOS 6.1 around March 2012.
0 kommentar(er)
