Hurry! Find the perfect gift today! Everyone gets our best deals on any smartphone!
Charliemon's profile

Contributor

 • 

2 Messages

Thursday, November 15th, 2018 8:32 PM

DHCP partially working for wifi connections via external access point

I have a Pace 5268AC AT&T router that is connected in the basement.  It did not provide adequate wifi coverage.  So I purchased a TP-Link EAP225 access point that I put on the ceiling of the main living area and hardwired it to port 3 of the 5368AC.  I then disabled the wifi radio in the 5268AC.

My wifi devices authenticate and connect to the EAP225 perfectly. I can go into the EAP225 management interface and see them connected.  But here is the problem, most of the devices never receive an IP address from the 5269AC DHCP server.  I have had only a few connected at once.

Is there a limit on the number of IP addresses on a single port?  Or is this a DHCP issue?

Community Support

 • 

225.4K Messages

5 years ago

Hi, @Charliemon.

This is likely a DHCP issue between the TP-Link and the Gateway. Are you able to get anything to work if you connect a device via LAN to the EAP225?

It may also be a viable option to use IP Passthrough on your Gateway to the EAP225.

John, AT&T Community Specialist

Contributor

 • 

2 Messages

5 years ago

Thanks John for your response. I do not believe passthrough mode is the
answer. And I cannot connect a wired device to the EAP225. Here is a
little more information.

The EAP225 is not a wireless router. It is an Access Point. It only has
one ethernet port that is used to connect it to the router, in this case the
AT&T Pace 5268AC. It does not have its own DHCP server.

If I put the EAP225 in passthrough, it would expose all connected wireless
devices to the Internet by bypassing the 5268AC firewall. And what DHCP
server would it use?

I currently have 10 devices that have authenticated to the EAP225 and only 6
were given IP addresses. These 6 work fine. The other 4 do not. That is
why I am looking at a DHCP problem. I am also doing a dive into the 4
devices that do not get an IP address to see if the problem is on the client
end.
Not finding what you're looking for?