uutommi wrote

The powerline extenders can't accept the static IP address assigned by the router.It only has a default IP 192.168.0.1 to manage it, if you are able to login to the management page, you can change it into the DHCP range of your router.

I probably wasn't clear enough. Before: I setup a 1.245/24 IP in the AP inside a VLAN where DHPC leases out 20.0/24. All great, AP was invisibile to discovery scans. Now: I do the same but the AP refuses to use an IP outside the 20.0/24. It works as it should but the AP is now, obviously, visible. I do not have problems, I'm just pointing out that after understanding the bug I was able to use it to add a tiny layer of security in my 802.1x WIFI. I would also need to add that using an IP inside the DHCP range is wrong as this may cause duplicate IPs. Instead you all should use an IP outside the DHCP range but still inside the subnet. Cheers.

I also have this problem too. So I have call technical staff to settle it. Now It is ok

I bought the WPA4220T kit in 2015, containing one PA4010 adaptor and two WPA4220 wifi extenders. My home router uses 192.168.1.1 as its IP address. Since the day I bought these things, I experienced network issues. The internet would stop working for all of the devices on my home network (at the same time). I complained to the ISP, I changed the home router ... and finally I worked out that the WPA4220s were causing the problem.

The WPA4220s need an IP address when they connect up to the network, but instead of using the DHCP protocol (like most other devices - phones, tablets, laptops, etc.) they just pick an IP address and go ahead and use it. In my case, often one of the WPA4220s was choosing 192.168.1.1 - i.e. the same address as my home router uses (and the address which every device on the home network uses in order to access the Internet).

After I figured out that these devices were actually breaking my network, I disconnected them and put them away. I just took them out of the cupboard (over 2 years later) and updated them all with the latest firmware ... but nothing has changed, and one of the WPA4220s promptly decided to use 192.168.1.1 and when it did it immediately broke internet access from my home network.

This is a fundamental design issue. The workaround suggested earlier in this thread is good if the devices power up (without knowledge of the IP range in use, so they operate somewhere differently and don't interfere with other devices) ... except that after a power cycle for the devices most likely all bets are off and they will randomly pick new addresses.

Failure to adhere to standards such as DHCP lead to my recommendation to AVOID THIS PRODUCT. TP-Link could fix this if they want, but given the amount of time which has passed since this product launched, and the continued existence of this thread, it seems safe to assume that they don't care.

Hi All,


TP-Link is aware of this issue. Following our research and investigation, we found that this issue due to some routers' default LAN IP is 192.168.1.1 which is the same as the TL-WPA4220_V1 default IP. So there will be IP address conflict when you first setup or reset the TL-WPA4220_V1. ( Our TL-WPA4220 will change its IP address after detecting IP address conflict, but there still will be a short IP address conflict. )
In order to help these customers who are affected by this reason our R&D have made a beta firmware ( TL-WPA4220_V1_180509_Beta ) to change the TL-WPA4220_V1 default IP from 192.168.1.1 to 192.168.0.254.
You can visit our official website try to download and upgrade the latest beta firmware to resolve this issue.

Note: After upgrading this firmware, you need manually reset this device to make it work.

For TL-WPA4220(EU/UK)_V1 : https://www.tp-link.com/en/download/TL-WPA4220_V1.html#Firmware

For TL-WPA4220(US)_V1 : https://static.tp-link.com/2018/201805/20180510/TL-WPA4220(US)_V1_180509(beta).zip

I pretty much believe this patch won't help, as this issue keeps happening even after changing subnet settings... however I found this somewhat useful as I can hide the AP from the VLAN, i give it a static IP outside the subnet while still allow me to serve wireless devices on the correct subnet ;)

By the way .254 is often taken... the fix should be to boot up a working DHCP first

With the current firmware you just assign a static IP outside your router DHCP pool (so no IP conflicts), reboot and that is it.

TP-Admin what about hardware version TL-WPA4220 v3.0 with firmware version 3.0.2 Build 20170725 Rel.69019 ? Is this fix included in this firmware ?
Thanks

tp-admin what about hardware version TL-WPA4220 v3.0 with firmware version 3.0.2 Build 20170725 Rel.69019 ? Is this fix included or shoul I get another version (that i dont see in your firmware page)

Thanks

Hello,

I have updated to this beta and now I cant pair my device anymore, how do I downgrade it ? the last files before this beta are
MAC-7420-v1.3.1-00-CS.nvm
and
4220_10_en50561update.pib

not BIN file like the beta firmware, so i cant downgrade

before updating to beta i noted exactly the firmware i was into:

Firmware Version:
1.2.8 Build 140401 Rel.49960n
MAC-QCA7420-1.3.0.2134-00-20151212-CS
PIB_422091_160421_003
Hardware Version:
WPA4220 v1 08C84015


HELP please!

I was able to pair with the beta firmware, now the problem is that i get "error obtaining ip address" tried resetting wifi and adding the network again but same error,s still want to know the downgrade procedure