Hi Evan,

if you only use static IP addresses in your LAN/network then EVERY client has to manually set a different static IP, too (plus Gateway, plus Primary IP). Frankly, this is not very smart :) because typically a WiFi client (e.g. mobile phone, tablet) selects the SSID of the EAP and gets a dynamic IP from the DHCP server (typically a cable or DSL router).

Make sure that the EAP225's Network settings are static with a valid IP address in the correct Subnet (typically 255.255.255.0) and that Gateway and primary DNS have the IP address of your internet router. Example:

Internet Router: 192.168.0.1 with "no DHCP"

EAP225 AP: IP=192.168.0.2 (Subnet 255.255.255.0; Gateway 192.168.0.1; Primary DNS 1928.168.0.1) - SSID "xyz"

Mobile phone-1: you have to add SSID manually including all network settings like for the EAP. Without correct IP, gateway and DNS no internet connection.

and...frankly, I am not sure whether this works at all. Therefore I strongly recomment to enable your router's DHCP server. If you want you can make the EAP's address a static one, but then you have to make sure that you don't have overlapping IP ranges for the DHCP (static/dynamic).

Good luck!

Cheers, Manfred

Evan.m wrote

That is why I can't understand how the EAP gives out 192.168.1.254 when i have entered 192.168.1.250 as gateway. 

An EAP does not give out DHCP leases. The gateway setting in the EAP's web UI is just for the EAP, nothing else (for example, if the Omada EAP Controller is in another network, the EAP needs to know how to reach it through a gateway). Thus, just set the gateway to the real IP of the actual gateway (192.168.1.250). It might be the TL-ER6120 which provides a wrong gateway IP to DHCP clients, but definitely not the EAP, which has no DHCP server.