confusion over VR400 v2 firmware upgrade

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

confusion over VR400 v2 firmware upgrade

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
confusion over VR400 v2 firmware upgrade
confusion over VR400 v2 firmware upgrade
2024-02-24 20:15:46
Model: Archer VR400  
Hardware Version: V2
Firmware Version: Current 0.6.0 0.9.1 v0070.0 Build 200713 Beta.34548n

Hi

 

My router says I have the latest firmware (as above).  The support site download shows the latest as 'Archer VR400(EU)_V2_220126, published 2022-01-14.

The downloaded file is Archer_VR400V2_0.4.0_0.9.1_up_boot(220126)_2022-01-26_14.19.07.zip which seems to be a lower version no. but a later date.

 

I looked into firmware updates because I use the VPN server and Android clients are now saying 'Server TLS too low'

 

Help!

  0      
  0      
#1
Options
3 Reply
Re:confusion over VR400 v2 firmware upgrade
2024-02-25 21:50:11

  @swimman 

 

You can go ahead and update your VR400 with the latest FW release from the support site manually.

It is recommended to have the latest stable FW release on your device for best experience.

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  
#2
Options
Re:confusion over VR400 v2 firmware upgrade
2024-02-28 23:40:53

  @swimman 

Thanks.  I have updated firmware successfully (after remembering to extract the .bin file).   I am disappointed though that the Open VPN sever still has the old deprecated security settings and my Android client still rejects connection.  The suggested beat software to fix is fir VR400v3, not v2.

  0  
  0  
#3
Options
Re:confusion over VR400 v2 firmware upgrade
2024-02-28 23:50:31 - last edited 2024-03-01 05:44:21

  @swimman 

 

Unfortunately v2 FW is from the beginning of 2022 and probably a new FW release should fix this if TP-LInk is willing to issue such.

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  
#4
Options