Sakapuss wrote

Model :

Hardware Version :

Firmware Version :

ISP :

Hi,

I have a Archer c2300 setup in AP mode with static IP. Even though DHCP is off and ip is static, it keeps sending DHCP requests to my main router every 30 seconds.

Anybody else noticed this behavior?

Thanks.

Hi,

I got the same issue.

My router had a static ip, I didn't notice network problem.

But I just want to understand why ?

Thanks

Experienced same issue... the C2300 in AP mode did DHCP request every 12 seconds while in "Smart IP" mode.  I resolved it by creating a DHCP reservation on the main Router C2300 for the mac address of the AP and then on the AP switched to Static IP. And voila... the continuous flood of DHCP refreshes has stopped.

Good luck !

@Sa

kapuss 

@adenhaan I can also verify this solution solves the flooding issue. The AP DHCP for internal functions is still unusable though.

@Sakapuss 

Here is the unacceptable answer from TP-Link support for a router under warranty.

Never, it was mentioned that we cannot use a fixed IP address on the router. I have never seen that on other brands. So, from TP-Link, you need to purchase a new one, hoping it will be an Archer C2300 V2.

Having DHCP request logs is not normal when you set a fixed IP address and all those continuous request are slowing down the performance of the router.

Also getting time from internet or firmware checks will not work.

I have exactly the same problem with a C2300 v1 running the latest firmware (2.0.3 which is quite old, from 09/2018).

While in Access Point mode, it keeps sending DHCP requests every ˜10 seconds even if the IP address is static.

Changing IP address from Static to Dynamic and then back to Static solves the problem, but it is temporary. Rebooting the router the issue appears again and the device starts flooding the network with DHCP requests again.

Making the IP Dynamic and reserving it on the main router does have the same effect (temporarily solves the problem until the next reboot/power cycle).

This is clearly a defect in the firmware, something that TP-Link should fix, but a more recent firmware is only available for the “v2” and the “v1” seems to be abandoned.

Shame on you TP-Link to treat your products and customers like this.

PS: I am crossposting this on purpose since TP-Link is ignoring this issue since this product was launched - see also another threads about the this exact same (and unsolved) problem at:

https://community.tp-link.com/en/home/forum/topic/105793 (this topic)

https://community.tp-link.com/en/home/forum/topic/156045

https://community.tp-link.com/en/home/forum/topic/183706

https://community.tp-link.com/en/home/forum/topic/98158