WiFi Roaming issue on Modem TP-Link VR1210v

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

WiFi Roaming issue on Modem TP-Link VR1210v

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
WiFi Roaming issue on Modem TP-Link VR1210v
WiFi Roaming issue on Modem TP-Link VR1210v
2022-09-27 17:45:16 - last edited 2022-11-12 22:54:26
Model: Archer VR1200  
Hardware Version: V1
Firmware Version: 2.0.0 0.9 v6041.0 Build 210701 Rel.27192n

Hi everyone,

I’m once again here because I found another issue related to the Modem Router TP-Link Archer VR1210v that I am not able to solve.

 

The problem that I found is related to the WiFi connection, in particular not related to signal strength or coverage, but to how devices are associated and seen in the network when connected to WiFi.

 

To better explain the issue I describe my network topology first. My network is composed as follows (I insert a description, however, to better clarify which the configuration is, I also add a scheme below the description):

  • Internet is provided through Fiber Optic (GPON). The GPON cable goes into the Nokia OLT provided by the ISP.
  • The Nokia OLT is connected to the WAN port of the TP-Link Archer VR1210v Modem, which connects to the extranet using the PPPoE Protocol. This device (AP1) has both WiFi 2.4GHz and 5GHz enabled.
  • Two more APs are connected in the network. The first one (AP2) is the TP-Link Archer C2, the second on is a branded Technicolor.  Both the additional devices connects to the main Modem/Router via LAN ports (LAN to LAN). Those devices have both WiFi 2.4Ghz and 5GHz enabled, with the same SSID and AES encrypted password of the TP-Link Archer VR1210v (AP1) but different channels.

 

*In the scheme there are also the Network Switches, however they are not relevant in this case, since the issue just affects the devices connected via WiFi

 

I have no roaming problem, which means that devices properly disconnects and connects to the AP (an so, to the channel) with the Higher strength. However the issue is related to how the wireless device is identified in the network.

 

Here what usually happens:

  • Device 1 (that we can assume to be “DEV1” from now on) is connected to AP1. All works fine;
  • DEV1 moves, it disconnects from AP1 and it connects to AP2. All continues to work properly;
  • DEV1 moves again, it disconnects from AP2 and it connects back to AP1 once more. Here comes the issue:  the devices is connected, but it is not identified in the network.

 

To make an example of the wrong behavior of the modem, if I set MAC binding to this device (MAC address of this device bound to the Private IP), the devices is unable to navigate, it is like there is another device with the same MAC address already connected somewhere else. Furthermore this device is unable to find/reach other devices in LAN, while if it connects back to AP2 or to AP3 all returns to work properly. That’s why I assume that the cause of the issue is the TP-Link Archer VR1210v (AP1). It does not work only when the devices gets connected back to the AP1, while on other devices the issue does not happen.

 

I also noticed that when the device is connect via WiFi to AP1, the modem VR1210v considers it as a wireless device, when it’s connect to AP2/AP3 the modem VR1210v considers it as a wired device. Now, assuming that I consider this behavior as correct/normal, I was wondering: is it possible that the modem VR1210v does not update quickly the arp table and it is not able to detect that the device has been disconnected from other APs? However I tried to not change/reset the WiFi connection when the issues occurs to monitor how much time does it takes to work properly again. The corrects behavior is reset even days after the movement (not joking, It took also one day).

 

Could someone help me fixing this issue? I assume that if I disabled the WiFi on the Archer VR1210v, attaching another device (AP4) to provide WiFi in that zone, I would probably fix the issue. However it’s not a solution that I like at all: the WiFi on the Archer VR1210v is pretty good, It would be a pity to disable it, excluding that it would be a waste of power and a waste of space.

 

P.S. – Few Notes:

1. I already tried to change firmware, nothing changed;

2. The issue persists even if I use different SSIDs, when it comes back to AP1 the issue occurs;

3. tried more WiFi devices and both WiFi 2.4GHz and 5GHz. The issue always persists.

 

Thank you in advance

  0      
  0      
#1
Options
1 Accepted Solution
Re:WiFi Roaming issue on Modem TP-Link VR1210v-Solution
2022-11-12 22:54:11 - last edited 2022-11-12 22:54:26

  @DavmoNet 

 

Updates on the issue. I have contacted the TP-Link support via e-mail and they help me to fix the issue. I'm gonna resume all the relevant things that came out from the e-mail exchange. I start confirming that the issue reported is solved.

 

After reproducing in their Lab the issue reported, TP-Link's staff confirmed the issue so they provided me two beta firmwares. I tested both of them and I can confirm that they properly work (in realtion to the issue described). Below I report the firmwares links and their description.

 

*** BETA #1 ***

Beta Link: https://static.tp-link.com/upload/beta/2022/202210/20221019/Archer_VR1210vv1_0.9.0_2.0.0_(221017).zip

Based on Release: Archer VR1210v v1_2.0.0 0.9 v6041.0 Build 220304 Rel.6349n (https://static.tp-link.com/upload/firmware/2022/202203/20220315/Archer%20VR1210v%20v1_2.0.0%200.9%20v6041.0%20Build%20220304%20Rel.6349n.zip)

Description: This is the Beta related to the latest version available today (12/11/22) on their official website for TP-Link VR1210v. The Beta adds tothe Release version the fix to the WiFi Roaming intranet issue (reported in this thread). However this version (even the release one) has some issues I found (after a while speed drops to a maximun of 250 Mbps, Port Forwarding Range issue, etc.) so I downgraded to the previous firmware Therefore I ask them to fix the issue of WiFi Roaming also on the previous firmware which brings me to Beta #2.

 

*** BETA #2 ***

Beta Link: https://static.tp-link.com/upload/beta/2022/202210/20221024/Archer_VR1210vv1_0.9.0_2.0.0_UP(221024).zip

Based on Release: Archer_VR1210v_v1_2.0.0_0.9_v6041.0_Build_210701_Rel.27192n (https://static.tp-link.com/firmware/2021/202107/20210722/Archer_VR1210vv1_2.0.0_0.9_v6041.0_Build_210701_Rel.27192n.zip)

Description: This is the Beta related to the version of the official release version of July 2021. This one adds the WiFi roaming fix to the best version (in my opnion) of the firmware for this device. I recommend this Beta. I'm still using it and it works perfectly.

 

I hope this could be useful for someone.

 

If you need don't hesitate to reply to this post.

 

Last thing: Thank you so much TP-Link's Staff for the support and help.

Recommended Solution
  0  
  0  
#7
Options
6 Reply
Re:WiFi Roaming issue on Modem TP-Link VR1210v
2022-09-27 21:10:02 - last edited 2022-09-27 21:50:57

I've monitored the situation a little more tonight. Here what I've found. I guess that the issue could be related to this.

 

I use always static IPs so it's easy for me to identify all the devices of the network. I took my smartphone (static private IP 192.168.1.50) and I decided to move the smartphone in various point of the house, checking step-by-step what happens.

 

Here's the steps and behaviour:

1) Modem TP-Link VR1210v is rebooted. Once restarted my smartphone is near the modem, so it connects to this device. If I check the list of Wireless Devices connected and reported in the "Basic" version of "Network Map" tab (the example of the tab I'm referring to is reported below), in the list I find 192.168.1.50, which is my smartphone, like I said previosly. All works fine. My smartphone is able to identify and reach all the devices into the LAN (I used and FTP server for testing).

 

2) I move my smartphone near the AP3. It disconnects from AP1 and connects to AP3. All continues to work just fine. I can stil identify devices into LAN (My FTP server is still reachable). If I check the "Wireless Client" list, the IP 192.168.1.50 is no longer there. Now, it appears in the "Wired Client" list, which I assume to be okay.

 

3) I move my smartphone back near the AP1. It disconnects from AP3 and connects to AP1 (I know for sure, since I use static channels for each AP so it's easy to me to see which channel, and so which AP, the smartphone is using). Suddently the IP 192.168.1.50 disappears from the "Wired Clients" list but it does not appear in the list "Wireless Client" either, even if it's connected to this AP and even if it is able to connect to internet (speedtested). And here come the troubles: If I try to reach other LAN devices, I fail, since the devices do not respond to my smartphone anymore (or better, I assume the router does not send packets to my smartphone anymore since it does not consider the IP 192.168.1.50 as connected to the network). This situation continues even for days, if I don't reboot the modem/router manually.

 

4) Without changing or rebooting anything, I move my smartphone near the AP2. It disconnects from AP1 and connects to AP2. Now IP 192.168.1.50 appears again in the "Wired Clients" list and all works fine once more. I can reach other network devices (Now I can connect to my FTP server). I tried to move near AP3 without come back to AP1, IP 192.168.1.50 still appears in the "Wired Clients" list and all works fine.

 

5) I move my smartphone back near the AP1, It disconnects from AP2 or AP3 and connects back to AP1. Once again IP 192.168.1.50 disappears from "Wired Clients" but it did not appears in the list "Wireless Clients". Once again my smartphone is unable to communicate with other LAN devices.

 

Very last behavior I notice: if i bind the MAC address with the IP address, once connected back to AP1 download speed quickly drops near 0 Mb/s, while upload speed remains the same. So I assume (correct me if I'm wrong) that it's effectively the router which refuses to send packets to my smartphone.

 

Someone knows how to fix this or at least what could be the cause?

  0  
  0  
#2
Options
Re:WiFi Roaming issue on Modem TP-Link VR1210v
2022-09-28 07:29:37

  @DavmoNet

Hey, are all AP 1+2+3 Archer VR1210V?

I doubt it is because Archer VR1210v together with its two APs are not actually truly mesh roaming products.

A better way would be to replace these two extended APs with Deco. For me I use RT-66U with 2*M9, everything seems fine.

I would also suggest to contact their technical support to see whether there would be a beta firmware since I used to see a similar issue on VR600, not your VR1210v though.

 

  1  
  1  
#3
Options
Re:WiFi Roaming issue on Modem TP-Link VR1210v
2022-09-28 16:24:59 - last edited 2022-09-28 16:26:38

  @Heidi_Alp

 

Thank you for your feedback.

 

I answer to all the points:

- No, the devices are not all VR1210v. just the first one (the one which provides internet to the others) is the VR1210v. the other two APs are the TP-Link Archer C2 and a branded Technicolor.

- Yes, I know that those devices are not "OneMesh" devices. But this would not be related to the issue. The only difference is that OneMesh would guarantee a smoother switching between the devices, which is not a poblem for me since for how I desinged the network switching already happens quite well.

- I know that Deco would be a better solution. But it does not change the fact that I would still use the modem TP-link Archer VR1210v since I need it for provide the network and especially to provide VoIP. So, this AP should just remain with the WiFi disabled, which i consider to be a pity, since radio signal is good.

 

Last thing about beta firmware: I'll certain write to the support but I also ask here. Does someone know if the are beta firmware for the Archer VR1210v or where I can find them?

 

Thank you

  2  
  2  
#4
Options
Re:WiFi Roaming issue on Modem TP-Link VR1210v
2022-10-05 23:05:12 - last edited 2022-10-05 23:07:56

  @DavmoNet 

 

There's a newer FW version for your VR1210v - here. Upgrade and test if any difference. You can revert back to your current version if needed.

Here's how to upgrade the FW manually.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#5
Options
Re:WiFi Roaming issue on Modem TP-Link VR1210v
2022-10-06 21:58:05

Thank you for the advice but I know there's a newer firmware available: I used that for a while and I can say it's no use... It is affected by the same issue of the WiFi roaming reported above and some other issues (you can find my previous thread about Port Forwarding range) which forced me to revert back to the firmware version I'm referring to right now.

 

Bad to say, the firmware of this modem/router has revealed to be a failure. Didn't expect that, usually TP-Link's products have never let me down. I'm surprise this happen for the Archer VR1210v. I assume that's because this device is available in Italy only and maybe there has not been so much troubleshoots / feedback from the users, like other devices which are available worldwide.

 

However, I'm in contact with the TP-Link support. I hope they could help me solve all of this. Obviously I'll update this thread when and if they let me know of to solve the issues, just in case someone else with my same problems could easily troubleshot.

 

Oh, If you or someone other else has some other suggestions feel free to let me know. I appreciate that. Even though the official support is helping me, it doesn't mean that, in the meantime, I'm not trying something to fix it by myself, if possible.

 

Thank you for yur help  @terziyski 

  2  
  2  
#6
Options
Re:WiFi Roaming issue on Modem TP-Link VR1210v-Solution
2022-11-12 22:54:11 - last edited 2022-11-12 22:54:26

  @DavmoNet 

 

Updates on the issue. I have contacted the TP-Link support via e-mail and they help me to fix the issue. I'm gonna resume all the relevant things that came out from the e-mail exchange. I start confirming that the issue reported is solved.

 

After reproducing in their Lab the issue reported, TP-Link's staff confirmed the issue so they provided me two beta firmwares. I tested both of them and I can confirm that they properly work (in realtion to the issue described). Below I report the firmwares links and their description.

 

*** BETA #1 ***

Beta Link: https://static.tp-link.com/upload/beta/2022/202210/20221019/Archer_VR1210vv1_0.9.0_2.0.0_(221017).zip

Based on Release: Archer VR1210v v1_2.0.0 0.9 v6041.0 Build 220304 Rel.6349n (https://static.tp-link.com/upload/firmware/2022/202203/20220315/Archer%20VR1210v%20v1_2.0.0%200.9%20v6041.0%20Build%20220304%20Rel.6349n.zip)

Description: This is the Beta related to the latest version available today (12/11/22) on their official website for TP-Link VR1210v. The Beta adds tothe Release version the fix to the WiFi Roaming intranet issue (reported in this thread). However this version (even the release one) has some issues I found (after a while speed drops to a maximun of 250 Mbps, Port Forwarding Range issue, etc.) so I downgraded to the previous firmware Therefore I ask them to fix the issue of WiFi Roaming also on the previous firmware which brings me to Beta #2.

 

*** BETA #2 ***

Beta Link: https://static.tp-link.com/upload/beta/2022/202210/20221024/Archer_VR1210vv1_0.9.0_2.0.0_UP(221024).zip

Based on Release: Archer_VR1210v_v1_2.0.0_0.9_v6041.0_Build_210701_Rel.27192n (https://static.tp-link.com/firmware/2021/202107/20210722/Archer_VR1210vv1_2.0.0_0.9_v6041.0_Build_210701_Rel.27192n.zip)

Description: This is the Beta related to the version of the official release version of July 2021. This one adds the WiFi roaming fix to the best version (in my opnion) of the firmware for this device. I recommend this Beta. I'm still using it and it works perfectly.

 

I hope this could be useful for someone.

 

If you need don't hesitate to reply to this post.

 

Last thing: Thank you so much TP-Link's Staff for the support and help.

Recommended Solution
  0  
  0  
#7
Options