Solution Powerline Extender Acting as the DHCP server
This Article Applies to:
TL-WPA7510, TL-WPA9610, TL-WPA8730/8630(P) V2, WPA4220 V3, etc.
Problem Description/ Phenomenon:
What is Smart DHCP, and How does Smart DHCP work? Visit TP-Link Smart DHCP Makes Network Configuration Simple.
Some users may find that after the power outage or router’s rebooting, even after router’s internet is back and up running, client devices still get IP address from powerline extender, and cannot connect to the internet.
Note: if router loses internet and then goes back afterwards, powerline extender will do a scan automatically, if it detects another DHCP Server is running, it will disable its own automatically (when powerline units remain paired), and the devices will get IP address from main router then access the internet through that.
Troubleshooting Suggestions:
1. Double check if the main router’s internet is actually back ON and working fine.
To confirm this, wire a computer or laptop to another LAN port of the router using an Ethernet cable, leave the main powerline adapter connected to the LAN port of the router as well, check if you can access the internet successfully on the computer or laptop. If yes, that means the router's DHCP server is up and running; If not, you will need to check what's wrong with the router after the reboot or power outage.
2. Make sure the powerline adapter and extender are still paired (house LEDs are ON), show us the IP address on the clients devices. Compare that when the internet is good and when it is not.
How to check the IP address on a computer: https://www.tp-link.com/support/faq/669/.
If your model is not listed or the issue persists, please report back with the information below to help locate the issue.
Or send a support email to TP-Link technical support with title ‘[Forum ID 265692] Powerline Extender Acting as the DHCP server’ to get further assistance:
1. How did you find out powerline device's DHCP server does not work properly? Did you often reboot main router or is there often power outage in your house?
2. Does router’s internet work fine at that moment?
3. LED status on both powerline units.
4. Brand and Model of router, the network topology, for example:
ISP modem --- Router Archer C7 --- PA8010 .... <powerline> ...WPA8630P --- Asus laptop model X.
5. Model & OS of devices that connected to wireless powerline unit.
6. Model number & firmware and hardware version of your powerline KIT, update the firmware if it is not the latest version:
How to update the firmware of the powerline adapter using the tpPLC Utility: https://www.tp-link.com/support/faq/1091/
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Njd4 It looks like the v2.1 models of the WPA8630P(UK) uses the UK version of the firmware, and the v2.0 models use the EU firmware. I managed to install the EU firmware. @njd4 I assume you have v2.1 models?
- Copy Link
- Report Inappropriate Content
I've not been able to test the beta firmware yet, since I have not been at my neighbors yet since.
Tomorrow morning I'll be there once again. But I'm hessitant of flashing this beta firmware that doesn't resolve the issue completly just yet.
Since there is no way back to the option of custom firmware since the partition layout has changed in newer firmwares according to the support pages of OpenWRT.
The custom firmware will most definitely resolve this particular issue, but I assume that would cause trouble if they were to need any warranty in the future. So this is a last resort option I would like to keep open.
Any sight on when a new (beta) firmware will be available that resolves this issue fully? Or maybe even one that gives the user direct control over the DCHP server itself, instead of 'smart' DHCP..
- Copy Link
- Report Inappropriate Content
@dunxd Sorry, Assumed i'd get an email when someone comments or replies.. Yes I believe mine is the 2.1 version. First one died completely and so was replaced under warranty a year or so ago so probably a bit newer.
- Copy Link
- Report Inappropriate Content
The DHCP issue seems better (if only it didn't start it at boot shortly, and the setting would survive reboots/powercycles)
We did, however, notice (frequent) connectivity problems from time to time after the upgrades:
- Wifi connection stays strong and stable
- Network connectivity fails, both DNS and page reloads fail
the connectivity restores itself automatically after <1 minute. No other setings in the network were changed except the FW update.
IP adresses were already fixed.
I wonder if anybody else has seen something like this....
We also came to a conclusion with the owners of this network:
It will be a few months until I visit this location again, if there is no stable firmware without DHCP by the end of the year I will buy another brand of gear and all TP-Link devices will be thown in the thrash.
PLEASE solve this simple issue by making a FW build that DOES NOT CONTAIN DHCPS. Simple.
You can offer both versions in case you insiste on this (WRONG) claim that DHCPS is needed in your product.
EDIT: editing post to clarify that when connectivity is lost, this is both LAN and WAN, so I cannot even reach the LAN side of the router!
thanks
- Copy Link
- Report Inappropriate Content
@peturdainn Hello,
Thank you for further feedback on the beta. To delve into the issue further, we'd like to follow up your case via email, please check your inbox later, thanks.
- Copy Link
- Report Inappropriate Content
@Solla-topee When will the final firmware be available for the TL-WPA8631P V3?
- Copy Link
- Report Inappropriate Content
I have installed the beta firmware for my TL-WPA4220 V5 which is 1.0.1 Build 210209 Rel.62933n (6985)
A) Is older than my previous one downloaded from the official download page: 1.0.1 Build 210305 Ref 64377n
B) It doesn't solve the DHCP issue.
What's going on?
- Copy Link
- Report Inappropriate Content
@Louen Hello,
WPA4220 V5 Beta firmware is to turn off DHCP function after set up static IP. While use the beta, after reboot PLC, DHCP may start again.
So it is recommended to keep WPA4220 powered on while test that beta, and see if that help with stability, if not, can you help confirm some case detail like the phenomena, network topology as requested and we will look into the issue further, thank you.
- Copy Link
- Report Inappropriate Content
I cannot believe after years this issue is still not solved. Just implement an option DISABLING THE DHCP SERVER COMPLETELY.
I have a WPA7510 KIT EU V2, and it's crippling. My typical failure use case:
1. general power outage
2. power comes up again
3. all network devices start to boot AT THE SAME TIME
4. TP-Link starts acting as a DHCP Server <- THIS IS A BIG NO NO!
5. Other embedded devices get a dynamic IP from the TP-Link
6. TP-Link cannot connect to the internet (of course!), the main router is still not operational
7. All embedded devices fail
8. Router comes up
9. Network is totally messed up, most embedded devices do NOT recover
Imagine a network with multiple network segments, VLANs, Wireless APs, etc, each segment with its own allocated DHCP server in a router (!), and you can see TP-Link wreaking havoc.
The only way to "fix" this for me is to power everything down, remove TP-Link physically from the sockets, power everything up, plug in the TP-Link physically in their sockets.
This is extremely annoying and time consuming, and usually involves connecting a laptop with a fixed network cable to multiple device in turn to try and fix the issue.
A NIGHTMARE FOR SYSTEM MANAGEMENT!
And all because TP-Link engineers think they have found a "smart" DHCP solution. Well, it's the most stupid network design decision ever made! You can tell that to your engineers. And that's coming from someone who has experience designing (embedded) network solutions. You should relabel and sell it as "Stupid DHCP", because that's what it is". Then at least customers know what to expect, that would be fair.
- Copy Link
- Report Inappropriate Content
@pipi I copy you.
I think they created a DHCP solution by default, to help in the configuration process, which makes a lot of sense.
But what I cannot utterly understand is why they don't do a worthy effect, to put in their interface a simple button with a DISABLE DHCP label.
Probably the DHCP is hardcoded in their embedded system, so it cannot be "dynamically" removed. So basically what they are doing with this pseudo-patch is "rewriting" the uplink information with static data, so, by default, the DHCP is not configured when the system boots.
This is a 101 on laziness, after years of having this issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 49957
Replies: 200