@d0ugmac1 I have two separate controller environments setup while trying to get everything configured correctly.

• The EAP220 environment uses Controller version 2.5.4.
• The EAP245 environment (with only 2 test APs) is using Omada Controller 4.5 A36.

Even without the controller and trying to use an AP in standalone mode with a single SSID will still see the IP addressing issues where a client gets the correct IP but about 2 minutes later the client reverts to a private IP of 169.x.x.x.

  @d0ugmac1 We have been testing various scenarios and think that the issue is related to VLAN tagging and how the TRUNKS are setup. We are going to have to go on site and do some more testing,

So far we have one EAP245 in stand-alone mode that has a single SSID with VLAN disabled. With this configuration the clients receive the correct IP addresses and are able to maintain those addresses. We will defintely have to do some more testing but we believe we are on the correct track.

For the record, the clients used for these tests are 8 laptops in our lab and are the same models that most of the on-site clients are using. We are working to integrate the new APs into the existing networks so they are on the same VLANs and hooked into the same switches and everything.

I will update this thread with what I figure out.

  @rlcorlew Old EAP has a special default VLAN setting, it will create a "big VLAN" according to your first SSID VID and transfer Internet data to all wireless clients. But tplink fixed it many years ago.

Tplink still have this "bug" on their SoHo products and there is a FAQ about how to use it.

https://www.tp-link.com/us/support/faq/418/

  @Somnus we are using Cisco switches and much newer WAPs than what this article is talking about.

For people who find this thread later, it looks like we have received one bad WAP and one good WAP since only one is now exhibiting this odd behavior. I am going to try and update the firmware on both EAP245 WAPs and see if that helps any.