WiFi Only Connection issues on TL-WPA4220 V4 (EU)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

WiFi Only Connection issues on TL-WPA4220 V4 (EU)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
WiFi Only Connection issues on TL-WPA4220 V4 (EU)
WiFi Only Connection issues on TL-WPA4220 V4 (EU)
2021-04-21 21:16:53
Model: TL-WPA4220  
Hardware Version: V4
Firmware Version: TL-WPA4220(EU)_V4_210222

Hi all,

 

My setup are two PLC TL-WPA4220 V4 (EU) both with the last firmware (2021-02-22) and different WiFi SSID names. One of the powerlines is directly connected to the gateway router.

 

With the last firmware update, 2021-02-22, the wired drops praticcaly vanished and rarilly I lose connection and when it happens is for a short period. So, concerning the AV600 protocol the last firmware was an improvement.

 

The problem comes to the WiFi connection. For some reason my Android and my Windows 10 devices take a lot of time until become connected to the network and the Internet. They also strugle to get the IP via DHCP, and when they do the access to the Internet and even to the gaeway router takes forever. My gateway router has the address 192.168.31.8 and as you can see below it takes minutes until ping gets the first response! Then it works fine, is just the starting phase...

 

C:\Users\Rui>ping -t 192.168.31.8

Pinging 192.168.31.8 with 32 bytes of data:
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.28: Destination host unreachable.
Reply from 192.168.31.8: bytes=32 time=1003ms TTL=64
Reply from 192.168.31.8: bytes=32 time=6ms TTL=64
Reply from 192.168.31.8: bytes=32 time=7ms TTL=64
Reply from 192.168.31.8: bytes=32 time=14ms TTL=64
Reply from 192.168.31.8: bytes=32 time=12ms TTL=64
Reply from 192.168.31.8: bytes=32 time=24ms TTL=64
Reply from 192.168.31.8: bytes=32 time=14ms TTL=64
Reply from 192.168.31.8: bytes=32 time=5ms TTL=64
Reply from 192.168.31.8: bytes=32 time=6ms TTL=64
Reply from 192.168.31.8: bytes=32 time=15ms TTL=64
Reply from 192.168.31.8: bytes=32 time=6ms TTL=64
Reply from 192.168.31.8: bytes=32 time=10ms TTL=64
Reply from 192.168.31.8: bytes=32 time=7ms TTL=64
Reply from 192.168.31.8: bytes=32 time=10ms TTL=64
Reply from 192.168.31.8: bytes=32 time=5ms TTL=64
Reply from 192.168.31.8: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.31.8:
    Packets: Sent = 61, Received = 41, Lost = 20 (32% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 1003ms, Average = 71ms
Control-C
^C
C:\Users\Rui>

 

In my opinion the problem is a network problem at the level of TCP/IP protocol, I have all parental and mac controls disabled so is nothing of that that is blocking the WiFi connection, nor the AV600 protocol because I never got any interruption while using my Smart TV connected to the same Powerline via Ethernet. So it must be the WiFi connection to the netwoork were the problem is.

 

Any solutions on the horizont for this?

 

BTW, Reliability is more important than Features, it doesn't matter to have more if the basic stuff doesn't work correctly.

 

Thanks

  2      
  2      
#1
Options
2 Reply
Re:WiFi Only Connection issues on TL-WPA4220 V4 (EU)
2021-04-23 09:19:09

@ruiseixas 

Thank you for your detailed post yes As the problem is quite abnormal we'd like to follow up your case via email (with forum ID ' 261962 '  in email subject)

Please check your inbox later ~

  1  
  1  
#2
Options
Re:WiFi Only Connection issues on TL-WPA4220 V4 (EU)
2021-04-24 04:24:57 - last edited 2021-04-27 09:37:04

@Solla-topee 

 

Hi,

 

After some tests I think I have discovered the real problem. I come to the conclusion that the "Wi-Fi Move" is the culprit, even when disabled it isn't truly disabled and this "Wi-Fi Move" thing works as a Roaming feature that is always in the way between the Wireless and the network. Basically when a client device connects to one of these Bricks (TL.WPA4220) it's "grabbed" by the "Wi-Fi Move" even when disabled, and then if for some reason the same client device connects to another Brick its access to the network is denied and we get the failed pings listed in the Original Post, only after a couple of minutes the grab ends and the client device gets access to the network and becomes able to ping again!

 

The previous description is for the case of disabled "Wi-Fi Move", but when it's explicitly enabled things work well, this means that this mode when enabled is capable of ungrab devices and thus let them access the network when switch Bricks (TL.WPA4220). To prove this I unplug the remote Brick and wait to see how all client devices would do the transition to the gateway Brick. To my surprise all devices struggled to get their IPs, meaning that the gateway Brick didn't got the required ungrab message from the unplugged brick and thus blocked all devices for a while making them struggle to get their own IP.

 

So, in conclusion, because the "Wi-Fi Move" feature is in reality always enabled, the only way to use multiple Bricks (TL.WPA4220) as WiFi AP is to explicitly enable the "Wi-Fi Move" in order to the ungrab messages be given allowing the respective client devices to have free access to the local network.

 

The ideal solution would be to be able to truly disable this "Wi-Fi Move" thing and have absolutely no barrier between the client devices and the local network.

 

Thanks and best regards.

 

UPDATE: This is due to the Roaming feature introduced in the 2019 firmware that can't be disabled. To solve it just install the old 2018 version of the firmware!

  0  
  0  
#3
Options

Information

Helpful: 2

Views: 886

Replies: 2

Related Articles