Orbi WiFi 7 RBE973
Reply

VPN setup and shows connected, but on log file says backtrack occurred

nodaicrag
Aspirant

VPN setup and shows connected, but on log file says backtrack occurred

Hi, I setup a VPN from a home in the USA on my R6900 router. (I setup a different one from the USA and that works). Installed the Open VPN, downloaded the client certificate from the router, used noip.com for the Dynamic DNS, etc.

 

Now that I am in Thailand, I connect Open VPN and it shows green, as in shows connected to my home in California. But when I check whatismyip.com after connecting and Open VPN showing a green status, the address coming back to me is still showing it is Bangkok, Thailand. I checked the log and it says something about a backtrack after connecting:

 

">STATE:1496229740,CONNECTED,SUCCESS,,[MyIPaddress],12974,,
Wed May 31 21:22:45 2017 us=658136 PID_ERR replay-window backtrack occurred [1] [SSL-0] [0_0000112346678889999999>>>>>>>EEEEEEEEEEEEEEE] 0:46 0:45 t=1496229765[0] r=[-1,64,15,1,1] sl=[18,46,64,528]
Wed May 31 21:23:03 2017 us=80967 PID_ERR replay-window backtrack occurred [2] [SSL-0] [00_0111111111345666666666666666666666666666666666666666666666666] 0:324 0:322 t=1496229783[0] r=[0,64,15,2,1] sl=[60,64,64,528]"
 
I had an earlier post about connecting to VPN the first time. I am not sure if this is related to the IP subnet thread I posted before: https://community.netgear.com/t5/Nighthawk-WiFi-Routers/VPN-R7900-Connected-to-home-but-no-internet/...
Which is why I also just posted another thread about remote management, because I can't access the router from Thailand to change the IP Subnet.
 
Any ideas? Thank you
Model: R6900|Nighthawk AC1900 Smart WiFi Router
Message 1 of 3

Accepted Solutions
nodaicrag
Aspirant

Re: VPN setup and shows connected, but on log file says backtrack occurred

Spoke with Netgear tech support and issue is resolved. I am now able to to connect to my VPN and stream Netflix. Under the section of VPN, after selecting the radial button for "All sites on the internet and home network," I was able to connect. 

 

For those wanting to connect to their Netgear VPN, learn from my trial and errors:

1) Under setup > Lan Setup = make sure you change the value of the 192.168. X .1

2) Advanced Setup > VPN setup > Clients will use this VPN to access All sites on the internet and home network 

3) Download client (I am using Windows 10) and connect with Open VPN

 

View solution in original post

Message 3 of 3

All Replies
nodaicrag
Aspirant

Re: VPN setup and shows connected, but on log file says backtrack occurred

I am able to now connect remotely to my router, but the VPN is still not working. When I connect OpenVPN, the status shows green and connected, but after I test the iP address, it is still showing my ip address from Thailand, not California. Here is a portion of the log if anyone can help:

 

Thu Jun 08 00:18:58 2017 us=758043 Key [AF_INET]67.169.72.17:12974 [0] not initialized (yet), dropping packet.
Thu Jun 08 00:18:59 2017 us=7804 PUSH: Received control message: 'PUSH_REPLY,route 192.168.3.0 255.255.255.0,route-delay 5,route-gateway dhcp,ping 10,ping-restart 120,route 192.168.3.1 255.255.255.0 192.168.3.1,route 3.0.0.0 255.0.0.0 192.168.3.1,route 4.0.0.0 255.0.0.0 192.168.3.1,route 8.0.0.0 255.0.0.0 192.168.3.1,route 9.0.0.0 255.0.0.0 192.168.3.1,route 14.0.0.0 255.0.0.0 192.168.3.1,route 16.0.0.0 255.0.0.0 192.168.3.1,route 18.0.0.0 255.0.0.0 192.168.3.1,route 23.0.0.0 255.0.0.0 192.168.3.1,route 47.128.0.0 255.128.0.0 192.168.3.1,route 54.0.0.0 255.0.0.0 192.168.3.1,route 184.0.0.0 255.0.0.0 192.168.3.1,route 69.0.0.0 255.0.0.0 192.168.3.1,route 204.245.0.0 255.255.0.0 192.168.3.1,route 173.224.0.0 255.255.0.0 192.168.3.1'
Thu Jun 08 00:18:59 2017 us=8301 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jun 08 00:18:59 2017 us=8301 OPTIONS IMPORT: route options modified
Thu Jun 08 00:18:59 2017 us=8301 OPTIONS IMPORT: route-related options modified
Thu Jun 08 00:18:59 2017 us=8301 Data Channel MTU parms [ L:1590 D:1450 EF:58 EB:411 ET:32 EL:3 ]
Thu Jun 08 00:18:59 2017 us=8801 Data Channel Encrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Thu Jun 08 00:18:59 2017 us=8801 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jun 08 00:18:59 2017 us=8801 Data Channel Decrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Thu Jun 08 00:18:59 2017 us=8801 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jun 08 00:18:59 2017 us=8801 interactive service msg_channel=532
Thu Jun 08 00:18:59 2017 us=17805 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=7 HWADDR=68:17:29:f2:d5:3c
Thu Jun 08 00:18:59 2017 us=19305 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
Thu Jun 08 00:18:59 2017 us=19305 OpenVPN ROUTE: failed to parse/resolve route for host/network: 192.168.3.0
Thu Jun 08 00:18:59 2017 us=19305 open_tun
Thu Jun 08 00:18:59 2017 us=23811 TAP-WIN32 device [NETGEAR-VPN] opened: \\.\Global\{91786683-DFC3-4C8F-AE25-34B6DA408151}.tap
Thu Jun 08 00:18:59 2017 us=24811 TAP-Windows Driver Version 9.21
Thu Jun 08 00:18:59 2017 us=24811 TAP-Windows MTU=1500
Thu Jun 08 00:18:59 2017 us=25810 Successful ARP Flush on interface [4] {91786683-DFC3-4C8F-AE25-34B6DA408151}
Thu Jun 08 00:18:59 2017 us=827470 Extracted DHCP router address: 192.168.3.1
Thu Jun 08 00:19:01 2017 us=399037 PID_ERR replay-window backtrack occurred [1] [SSL-0] [0_00011111112222222222______] 0:28 0:27 t=1496855941[0] r=[-2,64,15,1,1] sl=[36,28,64,528]
Thu Jun 08 00:19:04 2017 us=31257 TEST ROUTES: 15/15 succeeded len=15 ret=1 a=0 u/d=up
Thu Jun 08 00:19:04 2017 us=31257 MANAGEMENT: >STATE:1496855944,ADD_ROUTES,,,,,,
Thu Jun 08 00:19:04 2017 us=31257 C:\WINDOWS\system32\route.exe ADD 192.168.3.1 MASK 255.255.255.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=33257 ROUTE: route addition failed using service: The parameter is incorrect. [status=87 if_index=4]
Thu Jun 08 00:19:04 2017 us=33257 Route addition via service failed
Thu Jun 08 00:19:04 2017 us=33257 C:\WINDOWS\system32\route.exe ADD 3.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=34759 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=34759 C:\WINDOWS\system32\route.exe ADD 4.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=36760 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=36760 C:\WINDOWS\system32\route.exe ADD 8.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=42266 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=42266 C:\WINDOWS\system32\route.exe ADD 9.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=46769 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=46769 C:\WINDOWS\system32\route.exe ADD 14.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=50773 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=50773 C:\WINDOWS\system32\route.exe ADD 16.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=54778 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=54778 C:\WINDOWS\system32\route.exe ADD 18.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=58775 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=58775 C:\WINDOWS\system32\route.exe ADD 23.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=64782 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=64782 C:\WINDOWS\system32\route.exe ADD 47.128.0.0 MASK 255.128.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=68280 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=68280 C:\WINDOWS\system32\route.exe ADD 54.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=70281 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=70281 C:\WINDOWS\system32\route.exe ADD 184.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=72285 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=72285 C:\WINDOWS\system32\route.exe ADD 69.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=74785 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=74785 C:\WINDOWS\system32\route.exe ADD 204.245.0.0 MASK 255.255.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=77287 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=77287 C:\WINDOWS\system32\route.exe ADD 173.224.0.0 MASK 255.255.0.0 192.168.3.1
Thu Jun 08 00:19:04 2017 us=79289 Route addition via service succeeded
Thu Jun 08 00:19:04 2017 us=79289 Initialization Sequence Completed
Thu Jun 08 00:19:04 2017 us=79289 MANAGEMENT: >STATE:1496855944,CONNECTED,SUCCESS,,67.XXX.XX.X,12974,,
Thu Jun 08 00:19:23 2017 us=376026 PID_ERR replay-window backtrack occurred [2] [SSL-0] [00_0000000000000000001111111111122222222333333333344444444444444] 0:150 0:148 t=1496855963[0] r=[-2,64,15,2,1] sl=[42,64,64,528]
Thu Jun 08 00:19:27 2017 us=377257 PID_ERR replay-window backtrack occurred [4] [SSL-0] [000__00000000000000000000000000000000000111111111111111111111111] 0:349 0:345 t=1496855967[0] r=[-1,64,15,4,1] sl=[35,64,64,528]
WRWWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWWRRWRWRWRWRWWWWWWRRWRWRWRWRRRRRRRRRRWRWRWRWrWrWrWrWrWrWrWrWRwRwRwRwRwRwRwRwRwrWrWRwrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWrWRwrWrWrWrWrWrWrWrWrWRwRwRwRwrWrWrWrWRwRwrWrWrWrWrWrWrWrWrWrWrWrWrWRwrWrWrWrWRwrWrWrWrWrWrWrWrWRwRwRwrWrWrWRwrWrWrWRwrWrWrWRwrWrWRwRwRwrWrWrWrWr...WrWRwrWrWrWrWrWrThu Jun 08 00:20:24 2017 us=275788 TCP/UDP: Closing socket
Thu Jun 08 00:20:24 2017 us=276288 C:\WINDOWS\system32\route.exe DELETE 3.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=280290 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=280290 C:\WINDOWS\system32\route.exe DELETE 4.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=285794 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=285794 C:\WINDOWS\system32\route.exe DELETE 8.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=288798 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=288798 C:\WINDOWS\system32\route.exe DELETE 9.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=292299 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=292799 C:\WINDOWS\system32\route.exe DELETE 14.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=295301 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=295301 C:\WINDOWS\system32\route.exe DELETE 16.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=298303 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=298303 C:\WINDOWS\system32\route.exe DELETE 18.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=300806 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=300806 C:\WINDOWS\system32\route.exe DELETE 23.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=302806 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=303306 C:\WINDOWS\system32\route.exe DELETE 47.128.0.0 MASK 255.128.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=305310 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=305808 C:\WINDOWS\system32\route.exe DELETE 54.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=308311 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=308810 C:\WINDOWS\system32\route.exe DELETE 184.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=311812 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=311812 C:\WINDOWS\system32\route.exe DELETE 69.0.0.0 MASK 255.0.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=315814 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=315814 C:\WINDOWS\system32\route.exe DELETE 204.245.0.0 MASK 255.255.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=318816 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=318816 C:\WINDOWS\system32\route.exe DELETE 173.224.0.0 MASK 255.255.0.0 192.168.3.1
Thu Jun 08 00:20:24 2017 us=322319 Route deletion via service succeeded
Thu Jun 08 00:20:24 2017 us=322319 Closing TUN/TAP interface
Thu Jun 08 00:20:24 2017 us=343333 TAP: DHCP address released
Thu Jun 08 00:20:24 2017 us=343833 SIGTERM[hard,] received, process exiting
Thu Jun 08 00:20:24 2017 us=343833 MANAGEMENT: >STATE:1496856024,EXITING,SIGTERM,,,,,
WrWrWRwrWrWrWRwrWRwRwRwRwRwrWRwrWrWrWrWrWrWrWRwRwrWRwrWRwrWrWrWrWrWrWrWRwrWRwrWrWRwRrRwrWRwRwRwRwRwRwRwRwrWrWrWRwRwRwRwRwRwrWrWrWrWRwrWrWrWrWRwrWrWrWrWRwRwrWrWRwrWRwRwRwrWrWrWrWrWrWrWrWrWrWRwRwRwrWrWrWrWr

Message 2 of 3
nodaicrag
Aspirant

Re: VPN setup and shows connected, but on log file says backtrack occurred

Spoke with Netgear tech support and issue is resolved. I am now able to to connect to my VPN and stream Netflix. Under the section of VPN, after selecting the radial button for "All sites on the internet and home network," I was able to connect. 

 

For those wanting to connect to their Netgear VPN, learn from my trial and errors:

1) Under setup > Lan Setup = make sure you change the value of the 192.168. X .1

2) Advanced Setup > VPN setup > Clients will use this VPN to access All sites on the internet and home network 

3) Download client (I am using Windows 10) and connect with Open VPN

 

Message 3 of 3
Top Contributors
Discussion stats
  • 2 replies
  • 7094 views
  • 0 kudos
  • 1 in conversation
Announcements

Orbi WiFi 7