Powerline adapter looses connectivity (running DHCP server?)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Powerline adapter looses connectivity (running DHCP server?)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hardware Version :
Firmware Version :
ISP :
Hi All,
I recently got TL-WPA8630P kit and it works great (most of the time). It's hardware version 2.0 and running latest firmware 2.0.3 build 20171018.
But every now and then, at what would appear as random times, it stops passing traffic to my router. I can ping other powerline adapters in my setup, including the one that is physically connected to my router, but not router itself at 10.0.0.1, and thus can't access the internet or the local network outside of the powerline setup. There's no indication of any problem from LED lights on the boxes or anything. It looses connectivity like that for minute or two, after which comes back to normal.
I did noticed however, that the "outage" correlates with following entry into the System Log of the powerline device:
11 days 20:26:51 DHCPS INFO DHCP server started
11 days 20:28:26 DHCPS INFO DHCP server stopped
Now, firstly I do not understand why the powerline adapter have DHCP server (i'm using my router as DHCP) and secondly, how can I permanently disable it (or stop this behaviour).
Any help would be most appreciated.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@craxior Im having the exact same issue too
@Solla-topee Is there a way to disable it to fix the issue?
- Copy Link
- Report Inappropriate Content
Good day.
Thank you very much for all your concern about this case.
May I know the model number of your power-line adapter?
How about the current hardware and firmware version?
There are some suggestions:
How to manually configure the DHCP server on the power-line adapter:
1. Log into the power-line adapter: https://www.tp-link.com/support/faq/1417/
2.Then Go to Device Settings > LAN Settings.
Choose static IP
(for example, if the main router LAN IP is 192.168.0.1, DHCP IP address pool is 192.168.100-254)
You could input 192.168.0.2 for power-line adapter;
subnet mask 255.255.255.0
Default gateway 192.168.0.1
Primary DNS 8.8.8.8
secondary DNS 8.8.4.4
- Copy Link
- Report Inappropriate Content
Has this solved the issue for anyone?
- Copy Link
- Report Inappropriate Content
Finally I found my issue
I was using a kmtronics device at the end of my powerline extender (wired), it seemed the kmtronics was not able to obtain an ip.
I put a router between the extender and the kmtronics and it fixed my issue.
- Copy Link
- Report Inappropriate Content
@TP-Link this would be an option, if only my powerline adapter had those settings available.. mine (which is a TL-WPA7510 v1) doesn't show DNS settings at all, so no luck so far..
I also tried upgrading to the latest firmware, but nothing changes..
I'm lucky that my main router is quite stable and doesn't go down that often, but in the past I had more problems with this behaviour..
- Copy Link
- Report Inappropriate Content
Thank you very much for your kind feedback.
And there are several beta firmware for EU versions.
And if anyone had the same DHCP issue, please have a try and feel free to update here with further improvements.
https://community.tp-link.com/en/home/forum/topic/207438?replyId=540592
thanks a lot for your understanding and support.
- Copy Link
- Report Inappropriate Content
@TP-Link I have the same problem, as also reported here : https://community.tp-link.com/en/home/forum/topic/207438?page=3 . I have now left a review of the router on Amazon referring this, and the other link, so potential customers can see what problems they may experience.
- Copy Link
- Report Inappropriate Content
I've worked out what my issue was..
My router was set up to release dchp addresses between 50 and 100. The TP-Link was creating 254. As soon as I changed the 100 to 255, everything started working again.
I hope that helps someone.
- Copy Link
- Report Inappropriate Content
Well, I found that looking at 2 identical devices in hardware and firmware version I had the problem only on one.
Then I decided to revert the problematic one to factory reset and it didn't work, then I tried to backup the good one, restoring it on the bad one.
That seems to made the trick. Now I'm waiting to understand if it works undefinitely.
@TP-Link should consider releasing a firmware version that fix the DHCP server flag since it was available in earlier versions of it and, probably, it has not been considered in the latest firmware versions by latest firmware developers...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 14488
Replies: 19
Voters 1