VM does not receive an IP address via DHCP when connecting WLC 5508

[sseryaev]

I'm having a problem getting an ip address on a virtual machine. The VM is installed on my laptop, connected via a bridge. The laptop is connected via WIFI through WLC 5508.
DHCP up on cisco router 2951.
If I connect the laptop through a cable connection, everything works.
If I connect a laptop through another access point (Cisco Meraki MP33), everything works.
I can't figure out why the VM doesn't get an ip when connected via WLC 5508.
I have already spent a lot of time searching for a problem, a lot of forums and options for setting up WLC 5508.
Has anyone come across a similar issue, please help.

[sseryaev]

Macbook and other devices on the network receive IP correctly. As I wrote earlier, when connecting to another access point, the vm receives the IP in this configuration of my macbook.

Tomorrow I can answer the rest of the questions.

[sseryaev]

Hi.

[Flavio Miranda]

 i would like to see this tab

And for this tab, when you click WIRELESS it will list your AP or APs.  The AP´s hostname is a link. Click on the link to get inside the AP. And then, share the general tab

[sseryaev]

[marce1000]

  -  The WLC based  environment usually has more restrictive setups and policies e.g.  and or the problem is related to the network topology. You could try to give the VM an intended, as should be , ip address and see what happens if you try to ping (or traceroute) the intended DHCP server (e.g.). Also check the logs of the DHCP server when DHCP is tried (look for incoming requests from the VM).

 M.

[sseryaev]

If I set all the network parameters manually, everything works of course.
I also checked at home with the Linksys MX2000 router. There are no problems with getting an IP address.

Therefore, I am sure that the problem is on the Cisco 5508 controller.

[Rich R]

Agreed with @Flavio Miranda that you should disable DHCP proxy as per https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html#anc11
No need to put DHCP server IP on the interface - that is only used when DHCP proxy is enabled.
In bridging mode the DHCP is simply forwarded to the LAN so you  need DHCP server or relay on the LAN.

For the VM to work you also need "passive client" enabled:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/global_traffic_forwarding_configurations.html#passive-clients
Have you enabled that?

[sseryaev]

Hi.

Disabled dhcp proxy, enabled passive client. It did not help, vm does not receive an IP address.

[Rich R]

Does the VM DHCP discover/request get forwarded by the WLC?
If you run debugs on the client and VM MAC addresses what do you see?

[sseryaev]

Does the VM DHCP discover/request get forwarded by the WLC? - How can I check it? Please write in more detail. I don't have much experience with cisco.
If you run debugs on the client and VM MAC addresses what do you see? - I ran the debug, there is a screenshot above on the topic.

[Rich R]

Packet capture on the next hop router or switch will show you what packets are forwarded by the WLC.
Screenshots are not very useful - the output needs to be in a text file.  Did you run the debug on both client and VM MAC addresses?
You can use https://cway.cisco.com/wireless-debug-analyzer/ to provide a sanitised view of the debug.

[JPavonM]

I've never seen this scenario to work under Cisco WLAN Infrastructure, but it works with other vendors. Check this from a Cisco employee back in 2008.

The problem is that if you are bridging the connection from the VM (and not through a dedicated mapped WLAN USB dongle) the packets are received without any active association so they are discarded as tehre is only one IPv4 taht could be assocaited to that association id. Other vendors allow multiple IPv4 per association ID, other has something colled wireless bridging.