No Internet Access Frequently Occurs When Distributing Addresses from Mobility Express's DHCP

[Translator]

Thank you very much.
We are building a wireless LAN network using AP3802i's Mobility Express.

We use Mobility Express's internal DHCP to distribute IPv4 addresses to each client.
Wireless APs and clients can be connected, but there is a problem with frequent "no internet access" after connecting.

The default gateway for all DHCP scopes is "Mobility Express".
The VLANs between the wireless AP and the router match, and I think that the trunk port configuration is also fine.

We're trying to configure some SSIDs.
If the security type of WLAN security is "Personal (WPA2 or 3)", it can be connected, but "No Internet access" does not disappear or it is disconnected in a short time.
If the security type is WPA2Enterprise, it can be connected to the WAN without any problems after connection and authentication.

I tried running the "Client Debugging" in Network Summary > Access Points > Client > Client Tests in the Mobility Express admin screen, but only while debugging, the problem did not reproduce and I could connect to the WAN successfully.
If you try to connect later or connect from another client, you will see "no internet access" again.

If the default gateway for the DHCP scope is "Mobility Express", NAT appears to be done on the master AP, but there is an appearance of a problem here.
Please let us know how to cancel it.

[marce1000]

   - Ref : https://www.cisco.com/c/en/us/support/docs/wireless/mobility-express/210531-Mobility-Express-Internal-DHCP.html
                  >...The default gateway for all DHCP scopes is "Mobility Express".
     Strange , you would need to set that to the default gateway of the particular WLAN/VLAN-subnet , 

 M.

[Rich R]

Agreed with Marce - the ME WLC is not a router.  I don't even recommend using it for DHCP but it will work if you have no other option (like a server, switch or router).

Mobility Express only supports Flexconnect local switching so all routing and switching should be on the local network.  The ME WLC only provides control plane functions, not packet routing.  You should never direct client traffic towards the AP.  The clients should be using the local network router as their default gateway.

[Translator]

Thank you very much.
I know that Mobility Express is not a router.

As you wrote, you need to have a local router in order to increase SSID.
We wanted to connect to the WAN with SSIDs for employees and customers, but adding to the local router, in addition to the Mobility Express and access points, was too complex and too expensive to handle.

This time, we have just acquired a used access point, so we will dispose of it and introduce a third-party product.
Thank you for teaching me.

[MHM Cisco World]

first check DHCP Pool in SW 
second check the NAT 

that two points need to check when there is no Internet 

MHM