Archer C2300 DHCP Issue in AP Mode
Archer C2300 DHCP Issue in AP Mode
Noticing some weird DHCP requests on my cisco router from my Archer C2300 and the C2300's system log.
I only use the C2300 in AP mode and use it to solely serve my wireless clients. My cisco router is the DHCP server with a lease time of 43200 (~30 days). However, as you can see below in the log, my C2300 is requesting a new dynamic IP every minute. Here's the kicker, I have given the AP a static IP from the cisco router. Can anyone explain why the AP is doing the dumb?
Noticed a small number of folks have asked this similarly in the past, however, it seems no one has drawn any conclusions.
Thanks in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Still seeing the above issue.
Also, to note, my 5 Ghz capability keeps ceasing to function. I thought it was due to overlapping signals, but using my analyzer, there is no signal, period. 5 Ghz just turns "off" and the configuration page shows it as on. When you perform troubleshooting 101, turn it off and back on, the 5 Ghz band reappears but doesn't allow anybody to connect no matter the frequency or options used. The only fix is to factory reset or simply restart the device for it to happen again in a few days. Going back to analyzing, once the device is restarted, I'm well over the floor of any other wireless bands in the area.
I thought this was amusing, a quote from TP-Link Forums: "We are aimed to provide a fast, stable, security product for our customers." Fast, yes; stable, no.
Total issues: 2
Fixes: 0
- Copy Link
- Report Inappropriate Content
Fixed. Factory reset for the 4th time and still had issues. Then, while still in the same session, tried no security for 5 Ghz band, then Auto/Auto, then no security, then new passwords, then WPA2/TKIP and presto, stopped getting the DHCP binding logs, my network router is no longer being spammed, and 5G works. I think a system function wasn't working with some of the options set a certain way and then after changing it about 20-30 times in a span of 15 minutes, I must have either found the right options to play nice with the C2300 or it self-corrected. After I factory reset this time, I changed everything back to how I originally had it with no issues. We'll see if 5G dies again in a few days. >.>
Edit: This still works as a temporary fix, but no permanent solution has presented itself. It would be nice if TP-Link would do something about this...
- Copy Link
- Report Inappropriate Content
thanks
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I have the same issue in AP mode.
- Copy Link
- Report Inappropriate Content
@kennyrogersjr Usually it is the last thing you will think at :) .
I unpluged the internet cable from the wan port and pluged it to an ethernet port. I have no log message for 10 minutes...
- Copy Link
- Report Inappropriate Content
I resolved this by creating a DHCP reservation for the mac address of the AP on the main router and then switching the AP from "Smart IP" to "Static IP". (reservation and static IP set to the same IP address).
- Copy Link
- Report Inappropriate Content
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.
Going back to Netgear Nighthawk now
- Copy Link
- Report Inappropriate Content
I think that the v2 fix addressing all the issues is *an* answer, but you'd think they would support the customer with a v1 firmware update or something. Thanks for the update to the thread!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3614
Replies: 16
Voters 0
No one has voted for it yet.