This is me explaining what I'm doing/conceptualizing my thinking. a tl;dr is at the bottom for the main problem I'm facing. I need to use packet tracer though as a requirement (it's a class project) above all else.

I have a distribution layer of switches (3560's in a Port-Channel w/ LACP) which I was wanting to attach to a L2 switch to one of them via a trunk. The DLS switch is running DHCP for the access network, I (wrongfully) thought that the DHCP packets from my client devices would seamlessly pass through the light weight access point, but that was not the case and why I'm here.

My initial design idea was to have all my IOT wireless devices be in the subnet on VLAN 10. This is me trying to isolate IOT devices from the rest of the network.

I tried to use the Home Gateway instead, but it wants distribute to clients a private class C network and have be the internet.

My Ultimate goal is to have IOT devices in a isolated vlan 10, while having the IoT server in the network as a representation of being an external network the IOT devices phone home to.

tl;dr: I have the configured wireless LAN controller, and the accompanying Light weight access point (LAP) is registered with my DHCP server. However, clients connecting to the LAP are not obtaining an IP from the DLS DHCP server, but the LAP does receive a DHCP address. Goal is to have IOT devices communicate with server in the 209.X.X.X network


WLC Management Configuration

No DHCP assignment to laptop

Light Weight Access Point Getting a DHCP address

  • The switch does not even see the Wi-Fi traffic, only the tunnel traffic, in Local Mode. With Flexconnect, the traffic is dumped on the switch in a VLAN, and you must make sure you created the VLAN with the global vlan <number> command, not just creating the SVI.
    – Ron Maupin
    Dec 4 '20 at 18:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.