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
Hi @peturdainn thank you for the further feedback, I would regularly record and forward the new cases and feedback to appropriate team. I also suggest sharing the same feedback with our engineer directly through your existing support email TKID210826775.
- Copy Link
- Report Inappropriate Content
@Solla-topee I have TL-WPA7617 1.0 EU Hardware with 1.0.2 Build 210909 Rel.62151n (6985) I don't know if i have last version that can disable Smart DHCP by setting Static IP Address or not, because checking the date I can see the Beta have an after date
TL-WPA7617_V1(EU) Beta:
TL-WPA7617(EU)_V1_20211108_Beta
I set static IP Address in my WPA7617 and I can see DHCP Stops, but sometimes I can see trying to stars DHCPS and assign a wrong IP to my decice. Constantly I suffer disconnections from my device and I'm going to drive me crazy
14 INFO 0days, 00:00:09, DHCPC: Start DHCPC
15 INFO 0days, 00:00:12, DHCPS: Recv DISCOVER from XX:XX:XX:XX:XX:XX.
16 INFO 0days, 00:00:13, DHCPS: Send OFFER with ip 192.168.2.200.
17 INFO 0days, 00:00:13, DHCPS: Recv REQUEST from XX:XX:XX:XX:XX:XX.
18 INFO 0days, 00:00:13, DHCPS: Send ACK to 192.168.2.200.
19 INFO 0days, 00:00:30, DHCPC: Recv OFFER from server 192.168.2.1 with ip 192.168.2.68
20 INFO 0days, 00:00:30, DHCPS: Dhcps stop
21 INFO 0days, 00:00:51, DHCPC: Recv OFFER from server 192.168.2.1 with ip 192.168.2.68
22 INFO 0days, 00:01:15, DHCPC: Recv OFFER from server 192.168.2.1 with ip 192.168.2.68
The disconnections sometime happens after two days and other after half an a day. The solution its to load beta firmware or do I have the last version? In this last case please I think we need a solution for all this disturbing DHCP traffic.
Thanks in advance
- Copy Link
- Report Inappropriate Content
Hello @Alber11
Thank you for providing the case details.
1. the log shows PLC Smart DHCP works fine:
' 14 INFO 0days, 00:00:09, DHCPC: Start DHCPC
15 INFO 0days, 00:00:12, DHCPS: Recv DISCOVER from XX:XX:XX:XX:XX:XX.
16 INFO 0days, 00:00:13, DHCPS: Send OFFER with ip 192.168.2.200.'
This seems to be the log when PLC boots up, client requests an IP address, and PLC offer an IP to client so PLC and Client are the same subnet.
'19 INFO 0days, 00:00:30, DHCPC: Recv OFFER from server 192.168.2.1 with ip 192.168.2.68
20 INFO 0days, 00:00:30, DHCPS: Dhcps stop '
PLC gets DHCP offer from router the DHCP server, and stops its own DHCP.
2. The official driver is not embedded with the function turning off DHCP and from the log it does not seem to be a DHCP related issue. If there was any unstable issue on TL-PA7617 (EU)V1 Build 210909 before you set up static IP, you may start a new thread here , and providing some case details like network topology with model of router, Powerline Led/ House Led when issue happens, how often, how to recover, so we could look into that further.
3. You could still try the TL-WPA7617(EU)_V1_20211108_Beta if you want to turn DHCP off.
- Copy Link
- Report Inappropriate Content
You say the logs show Smart DHCP works, because the PLC and client are on the same subnet, but that is not at all the marker of it working. It just guarantees that the client can communicate with the PLC. But the poster stated that this behaviour is causing problems - I assume because the client could not reach the gateway to the internet. The vast majority of the time the clients on the network do not need to contact the PLC (i.e. access it to configure it) - they just need it to pass the traffic on in the same way as an unmanaged switch.
All Smart DHCP does is create an additional problem should the intended DHCP server go down. The intended DHCP server going down is often a temporary issue, or it could even be intended. Smart DHCP lurking around with no documentation or means to disable it is absolutely not helpful as the last three years of posting on this issue surely makes clear.
Surely in all this time it would have been possible to create a UI that allows users to say whether or not they want this quirky, non standard, hard to understand feature. Or fix the bug of configuring static IP on the PLC failing to turn it off and issuing it to non-beta versions of firmware to all affected models.
- Copy Link
- Report Inappropriate Content
Hello @dunxd
Some clarification here:
' 14 INFO 0days, 00:00:09, DHCPC: Start DHCPC‘
From time stamp, this is the log of 0.09s just after RE boost up.
'20 INFO 0days, 00:00:30, DHCPS: Dhcps stop '
And 0.3s after RE boots up PLC turn off its smart DHCP, this is what I said smart DHCP works fine.
'the PLC and client are on the same subnet' I think this is why smart DHCP exists, for PLC web management.
I could not deny it seems that smart DHCP is causing some trouble from previous posts and feedback, and some beta were made, so far our team are still on the way making some new beta which allows turning DHCP off completely.
- Copy Link
- Report Inappropriate Content
Same problem here, brought the network down for an hour before determined that the router was thinking the TL-WPA8630 was the gateway and DHCP server.
Has there been a firmware release/beta for the TL-WPA8630 (non-P) V2 US version?
- Copy Link
- Report Inappropriate Content
Hello @sigwx
Just noticed you use TL-WPA8630 V2 US version, I will double-check if there is a US version beta.
Can I know the model of router, and network topology? How does router act when it detects the smart DHCP you may share some logs on router, thank you.
- Copy Link
- Report Inappropriate Content
Just take a look at how long ago this issue was raised and then ask if you think TPlink care about doing what was suggested and I'd suggest generally agreed with to provide a switch to disable DHCP.
They haven't done it and are simply avoiding doing it in the hopes they will release another device and continue to take money from customers trying to find solutions to problems TPLink created.
Recommend to cut losses and bin TPLink and don't buy their stuff again.
- Copy Link
- Report Inappropriate Content
@Solla-topee
I tried using a Linksys WRT32x and Linksys WRT1900ACS. Both cases, ended up having to unplug all the WPA8630 (I have 2 V2 and 1 V1) before networking would come up correctly.
Best description is a star topology. One of the ethernet ports of the router goes to a PA8010 then I have the WPA8630 around the house to extend wifi to different areas.
- Copy Link
- Report Inappropriate Content
@sigwx my syslog server. All ips asigned manualy in the DHCP server in my asus, and configured in all devices one to one, included wpa8630p :P . No associated devices or making requests to wpa8630p. Is shameful.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 49928
Replies: 200
Voters 2
