@Solla-topee hi, thanks for your reply and further information.

Unfortunately, I will not be able to test the beta firmware as I have removed the TP-Link kit from my network and replaced it with a Wi-Fi mesh system.

I could not afford any further interruptions to my daily work.

@Solla-topee  Good Morning.

It's a joke?:

After so many years using your products, I finally had to register.

I've been regretting changing my main router, a TD-W8980, for a few years since I installed it, configured it, and forgot about it. And then install as a wi-fi repeater. Like the TL-PA4020 PLCs that permanently replaced it, along with the TL-WPA8630P that I acquired years ago to complete my lan network. I've been thinking for a long time about the possibility that when the time comes to update my devices, I will purchase a high-end router or even business devices from TP-Link. But after following this case I'm not so sure anymore.

Ignoring that enabling a DHCP on a network, without any mechanism to disable it, seems reckless to me to say the least and that assigning the static IP address does not solve the problem (I have always had it like this), the latest firmware is dated 2017 !!!, And the only thing you have been able to get in all this time is a beta one that not even loads well and changes the password of the device? How much time have I wasted installing OpenWRT and unofficial firmwares that didn't fix the problem, and now more time wasted with the manufacturer? It's amazing guys !!! Keep going.  I'm going to reset the plc ... again

Device reset and configured with a static ip (as always, minus the mac table, I'm afraid to load anything).

To whoever happens the same as me when re-recording the beta firmware, resetting the device resets the admin password to the default "admin", the user does not appear in the login screen, nor does he have the option to create a new one.

But what has impressed me:

no sign of the option to disable it, and it keeps getting up when it feels like it.

We'll see tonight how many times I have to get up while watching a family movie. Let's see if we're lucky and we don't end up getting bored by interruptions and go to sleep.

Hello @Solla-topee
Are you questioning what I say? I have read all your posts, including the one about the internet access problem. The one who I think you have not read the requests of your clients is you. The screenshots that I have attached previously, but it is not shown because I deleted the data, you already have an updated one in case you don't believe me, are with the static ip configured in TL-WPA8630P, ALWAYS IN STATE LIKE THIS. My TL-WPA8630P has always had the static ip.

The problem with your "smart DHCP" is precisely that, that it serves IPs to the computers with automatic configuration, but not only that, when I configure the devices in my house with a fixed ip and your "Smart DHCP" no detect up mi router, your dhcp configures the TL-WPA8636P as a gateway and DNS although it does not change the static ip leaving them with no internet access.

Your equipment, even after configuring it with a fixed ip, continues to start DHCP as you can see in the previous screenshot, and continues to generate DHCP traffic to my router: .

My subnet is 192.168.76.224/27, all ips are reserved in the dhcp of my router (Asus RT-AC88U), including 192.168.76.249/27 which uses the tl-wpa8630p as static ip. I unistalled our beta firmware:

After so long, what you have to do is implement the option to disable it in the GUI, as it appears in your explanation of how your Smart DHCP works,

and not try to correct the "malfunction" of the service by making serve people of beta testers. By the by, I have been unemployed for a year and a half.

Please, Stop hanging around and implement the option so that users can disable your "Smart DNS", in this model and in the most modern ones where it also seems to fail as I read in the forum.

@Solla-topee 

sorry, the screenshot shows an ip request from a device connected to the 2.4 wireless network of the TL-WPA8630P. That traffic is correct

Hi,

Today I tried to resolve the internet issues at my elderly neighbors place.

Eventually coming to the conclusion that there was a dhcp/default gateway issue. When statically assigning the IPV4 settings through the control panel of Windows everything was working fine. When letting Windows auto decide the connection details it is instantly marked as a 'limited' connection. Also several other devices such as iPads and iPhones show the same behaviour.

The problem is completely random and when the error occurs the default gateway (found with ipconfig) shows the address of the TP link instead of the main router. Even after setting the IP settings of the TP link itself to static.

The unit is a WPA-8630 (non P) V2 EU. I checked for updates in the GUI, but it stated 2.0.2 was the latest available. In the solution of this topic beta firmware files are available but only for the P model. I tried the beta firmware provided here on my unit, and it only gave me an error message of an unsupported update file? Is there also a non P beta firmware available?

The topology is simple enough: Genexis 7840 fiber modem/router (Dutch provider Caiway) -> WPA8630EU.

Thanks.

@MortuuS  Correct, this is what I was trying to convey in my previous post.

Not only does it assign configuration in the computers with automatic configuration, in addition to those with manual configurations, the output of the ipconfig command shows the ip configured manually but the data of dns, dhcp and gateway show the ip of the wpa8639, so it leaves the device manually configured with no internet connection. This is serious, I had not seen it before.