I'm having the following problem. I have a notebook that associates to a WiFi (WLAN) netwok with a WLC 2106 that receive it's IP address from a DHCP server. When I turn on a virtual machine (with VMware o Virtual Box) inside that notebook, that VM doesn't receive an IP address from the DHCP server. The virtual network adapter that is inside the VM is configured as bridge mode, it is to say that it connects to the physical network through the notebook wireless adapter. Therefore, the AP and the WLC see the virtual machine and the notebook as they were two different clients, with two different MAC addresses but using the same physical network adapter. It's a very common scenario when you work with virtual machines.
The question is. Could be any configuration inside de WLC that doesn't permit to lease more than one DHCP IP address to the same physical network adapter. Because if I configure an static IP address inside the VM it works OK. The problem is only receiveing a DHCP address.
Solved! Go to Solution.
Starting in 220.127.116.11, we added support for non-cisco WGBs with the passive client feature on a wlan. This feature will also apply to VMware and virtual clients -- it is available on the 2100, 2500, 5500 WLCs, although it is not available on the 4400 series (WISM/3750) due to architecture limitations.
Guido, you can try enabling the passive client feature on your WLAN to see if this helps resolve the issue.
You're right, we introduced the passive client feature in 18.104.22.168. However, we enhanced this feature in 22.214.171.124 to include 3rd-party workgroup bridge support, which happens to also impact clients such as VMware and other virtual machines:
Autonomous AP architecture should not have this same issue -- I do not believe the MAC/IP address binding limitation is present.
If you are experiencing issues, I would urge you to open a TAC service request.
You could also run a packet capture on the AP switchport to see if the DHCP discover/requests from the VM client are making it on the wire.
I have a Cisco 897 with an integrated AP in autonomous mode. I've tried different software versions, but still I can't receive an IP address from the DHCP server with host virtualization and bridge mode as described above.
I've done a wireshark capture of it, and simply do not receive any reply to my DISCOVER packets. i do however see my DISCOVER reach the router (debug ip dhcp server). If I configure an IP address manually, it works.
Do you have any idea why or what I could be missing?
No, my issue isn't different IMO. I have a working AP where clients can bridge to the router (dhcp server) and get an IP address. Where it does not work is when I take one of my computers and install a virtual computer on it, configure its vNIC for bridging to the Wi-Fi NIC of the host and try to lease an IP address.
I hope this clearifies my issue.
I had the same issue and it looks that the AP in autonomous mode does not forward DHCP replies to the virtual computer. After some troubleshooting I found a solution (similar to chixson001), see https://supportforums.cisco.com/discussion/12237801/problems-dhcp-and-virtual-pc-connected-ap-autonomous-mode