Not connecting to our office VPN network using Jio 5G SIM after updating firmware of MR200
Issue Description:
There is a issue with MR200 router where my laptop is not able to connect to VPN using Jio 5G-enabled SIM.
Someone please help.
Background:
Initial problem was I could not get internet from my MR200 router with Jio SIM. So, as suggested by Tp-Link Support team India and this thread (https://community.tp-link.com/en/home/forum/edit/reply?sourceId=604130), I updated the firmware. After updating the firmware, restored it to factory settings and then I reconfigured the settings from scratch. Got the internet from my Jio SIM now. So, the initial problem was solved.
But, I am facing different problem now. The problem is I am unable to connect to my office VPN. The TacitineVPN client follows 2-factor authentication. Once I enter password, that's it - it is stuck on authentication screen and not completing. It keeps on showing like "MANAGEMENT: >STATE: 1718720577, WAIT,,,,"
My findings:
(1) Inserted the Same 5G-enabled Jio SIM into a mobile, turned on Mobile hotspot. Connected Laptop to mobile hotspot thru WiFi and connected to VPN successfully. So, no problem wih Jio SIM.
(2) Inserted a 5G-enabled Vi SIM into router, created another profile for Vi (PDP type: IPv4 & IPv6). Internet works fine. Connected laptop to router thru WiFi and connected to VPN successfully as usual. So, no problem when I use 5G-enabled Vi SIM with the beta firmware.
Thus, it seems like the problem is only with MR200 settings or a bug in beta firmware.
Troubleshooting Done so far:-
Multiple router restart, reset router, use Vi SIM, try different APN settings (PDP type, Authentication type, etc.).
Router info:
Model: Archer MR200(EU) V5.20
Firmware Version: 1.0.0 0.9.1 v0001.0 Build 230815 Rel.58049n_Beta
Hardware Version: Archer MR200 v5 00000001
Dial-up settings used for Jio SIM:
WAN Interface
Mobile Data: ON
Data Roaming: ON
NAT: ON
Network Mode: 4G Preferred
Band: Auto
Dial-up Settings
Network Search: Auto
Profile Name: Jio5Gto4G
PDP Type: XLAT
APN Type: Dynamic (tried static too. No use)
Username: <empty>
Password: <empty>
Authentication Type: CHAP (tried none too. No use)
Laptop used:
Dell Latitude, Windows 10.
VPN client used:
VPN client version: Tacitine SSL VPN GUI v11.10.0.0
Protocol: UDP.
Authentication type: 2-factor authentication using Google Authenticator android app.
MTU: 1500.
VPN client's log:
Mon Jun 24 14:26:23 2024 TacitineSSLVPN 2.4.5 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 24 2019
Mon Jun 24 14:26:23 2024 Windows version 6.2 (Windows 8 or greater) 64bit
Mon Jun 24 14:26:23 2024 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10
Enter Management Password:
Mon Jun 24 14:26:23 2024 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Mon Jun 24 14:26:23 2024 Need hold release from management interface, waiting...
Mon Jun 24 14:26:23 2024 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'state on'
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'log all on'
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'echo all on'
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'bytecount 5'
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'hold off'
Mon Jun 24 14:26:23 2024 MANAGEMENT: CMD 'hold release'
Mon Jun 24 14:26:30 2024 MANAGEMENT: CMD 'username "Auth" "vpn"'
Mon Jun 24 14:26:30 2024 MANAGEMENT: CMD 'password [...]'
Mon Jun 24 14:26:30 2024 MANAGEMENT: CMD 'password [...]'
Mon Jun 24 14:26:30 2024 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Jun 24 14:26:30 2024 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Mon Jun 24 14:26:30 2024 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Mon Jun 24 14:26:30 2024 MANAGEMENT: >STATE:1719219390,RESOLVE,,,,,,
Mon Jun 24 14:26:30 2024 TCP/UDP: Preserving recently used remote address: [AF_INET]122.187.65.82:1197
Mon Jun 24 14:26:30 2024 Socket Buffers: R=[65536->65536] S=[65536->65536]
Mon Jun 24 14:26:30 2024 UDP link local: (not bound)
Mon Jun 24 14:26:30 2024 UDP link remote: [AF_INET]122.187.65.82:1197
Mon Jun 24 14:26:30 2024 MANAGEMENT: >STATE:1719219390,WAIT,,,,,,
Screenshot of Jio settings:
Request:
This is serious issue and has to be resolved on priority. I couldn't believe a product which I purchased just an year ago no longer supports India's major telecom provider Jio properly. The router is sitting useless now.
Somebody please help.