Hello -
I’ve read thru many threads on issues folks have had with Remote Access behind a VPN. I’m using NordVPN and Plex Media Server on Win10. I’ve created the below section within one of the openvpn configuration files and not having any luck with remote access functioning. Any help is appreciated.
PLEX over WAN routes
route 67.55.92.183 255.255.255.0 192.168.0.1
route 50.63.202.0 255.255.255.0 192.168.0.1
Log File:
Sat Dec 09 22:20:38 2017 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jan 31 2017
Sat Dec 09 22:20:38 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Sat Dec 09 22:20:38 2017 library versions: OpenSSL 1.0.2k 26 Jan 2017, LZO 2.09
Enter Management Password:
Sat Dec 09 22:20:38 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25368
Sat Dec 09 22:20:38 2017 Need hold release from management interface, waiting…
Sat Dec 09 22:20:39 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25368
Sat Dec 09 22:20:39 2017 MANAGEMENT: CMD ‘state on’
Sat Dec 09 22:20:39 2017 MANAGEMENT: CMD ‘log all on’
Sat Dec 09 22:20:39 2017 MANAGEMENT: CMD ‘hold off’
Sat Dec 09 22:20:39 2017 MANAGEMENT: CMD ‘hold release’
Sat Dec 09 22:20:40 2017 MANAGEMENT: CMD ‘username “Auth” "jason.boehm@me.com"’
Sat Dec 09 22:20:40 2017 MANAGEMENT: CMD ‘password […]’
Sat Dec 09 22:20:40 2017 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Sat Dec 09 22:20:40 2017 NOTE: --fast-io is disabled since we are running on Windows
Sat Dec 09 22:20:40 2017 Outgoing Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication
Sat Dec 09 22:20:40 2017 Incoming Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication
Sat Dec 09 22:20:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]173.254.255.139:443
Sat Dec 09 22:20:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Dec 09 22:20:40 2017 Attempting to establish TCP connection with [AF_INET]173.254.255.139:443 [nonblock]
Sat Dec 09 22:20:40 2017 MANAGEMENT: >STATE:1512879640,TCP_CONNECT,
Sat Dec 09 22:20:41 2017 TCP connection established with [AF_INET]173.254.255.139:443
Sat Dec 09 22:20:41 2017 TCP_CLIENT link local: (not bound)
Sat Dec 09 22:20:41 2017 TCP_CLIENT link remote: [AF_INET]173.254.255.139:443
Sat Dec 09 22:20:41 2017 MANAGEMENT: >STATE:1512879641,WAIT,
Sat Dec 09 22:20:41 2017 MANAGEMENT: >STATE:1512879641,AUTH,
Sat Dec 09 22:20:41 2017 TLS: Initial packet from [AF_INET]173.254.255.139:443, sid=8f019e60 62594d67
Sat Dec 09 22:20:41 2017 WARNING: this configuration may cache passwords in memory – use the auth-nocache option to prevent this
Sat Dec 09 22:20:41 2017 VERIFY OK: depth=1, C=PA, ST=PA, L=Panama, O=NordVPN, OU=NordVPN, CN=us641.nordvpn.com, name=NordVPN, emailAddress=cert@nordvpn.com
Sat Dec 09 22:20:41 2017 Validating certificate key usage
Sat Dec 09 22:20:41 2017 ++ Certificate has key usage 00a0, expects 00a0
Sat Dec 09 22:20:41 2017 VERIFY KU OK
Sat Dec 09 22:20:41 2017 Validating certificate extended key usage
Sat Dec 09 22:20:41 2017 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sat Dec 09 22:20:41 2017 VERIFY EKU OK
Sat Dec 09 22:20:41 2017 VERIFY OK: depth=0, C=PA, ST=PA, L=Panama, O=NordVPN, OU=NordVPN, CN=us641.nordvpn.com, name=NordVPN, emailAddress=cert@nordvpn.com
Sat Dec 09 22:20:41 2017 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sat Dec 09 22:20:41 2017 [us641.nordvpn.com] Peer Connection Initiated with [AF_INET]173.254.255.139:443
Sat Dec 09 22:20:42 2017 MANAGEMENT: >STATE:1512879642,GET_CONFIG,
Sat Dec 09 22:20:42 2017 SENT CONTROL [us641.nordvpn.com]: ‘PUSH_REQUEST’ (status=1)
Sat Dec 09 22:20:42 2017 PUSH: Received control message: ‘PUSH_REPLY,redirect-gateway def1,sndbuf 524288,rcvbuf 524288,dhcp-option DNS 78.46.223.24,dhcp-option DNS 162.242.211.137,route-gateway 10.7.7.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.7.7.147 255.255.255.0,peer-id 0,cipher AES-256-GCM’
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: timers and/or timeouts modified
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: --sndbuf/–rcvbuf options modified
Sat Dec 09 22:20:42 2017 Socket Buffers: R=[65536->524288] S=[65536->524288]
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: --ifconfig/up options modified
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: route options modified
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: route-related options modified
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: peer-id set
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: adjusting link_mtu to 1659
Sat Dec 09 22:20:42 2017 OPTIONS IMPORT: data channel crypto options modified
Sat Dec 09 22:20:42 2017 Data Channel Encrypt: Cipher ‘AES-256-GCM’ initialized with 256 bit key
Sat Dec 09 22:20:42 2017 Data Channel Decrypt: Cipher ‘AES-256-GCM’ initialized with 256 bit key
Sat Dec 09 22:20:42 2017 interactive service msg_channel=960
Sat Dec 09 22:20:42 2017 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 I=12 HWADDR=38:d5:47:7d:27:2a
Sat Dec 09 22:20:42 2017 open_tun
Sat Dec 09 22:20:42 2017 TAP-WIN32 device [Ethernet 2] opened: \.\Global{5A3FAD7C-5FCE-4216-B0C7-4DC8EC63FA9D}.tap
Sat Dec 09 22:20:42 2017 TAP-Windows Driver Version 9.21
Sat Dec 09 22:20:42 2017 Set TAP-Windows TUN subnet mode network/local/netmask = 10.7.7.0/10.7.7.147/255.255.255.0 [SUCCEEDED]
Sat Dec 09 22:20:42 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.7.7.147/255.255.255.0 on interface {5A3FAD7C-5FCE-4216-B0C7-4DC8EC63FA9D} [DHCP-serv: 10.7.7.254, lease-time: 31536000]
Sat Dec 09 22:20:42 2017 Successful ARP Flush on interface [11] {5A3FAD7C-5FCE-4216-B0C7-4DC8EC63FA9D}
Sat Dec 09 22:20:42 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Dec 09 22:20:42 2017 MANAGEMENT: >STATE:1512879642,ASSIGN_IP,10.7.7.147,
Sat Dec 09 22:20:47 2017 TEST ROUTES: 3/3 succeeded len=2 ret=1 a=2 u/d=up
Sat Dec 09 22:20:47 2017 C:\WINDOWS\system32\route.exe ADD 173.254.255.139 MASK 255.255.255.255 192.168.0.1
Sat Dec 09 22:20:47 2017 Warning: route gateway is ambiguous: 192.168.0.1 (3 matches)
Sat Dec 09 22:20:47 2017 Route addition via service failed
Sat Dec 09 22:20:47 2017 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.7.7.1
Sat Dec 09 22:20:47 2017 Route addition via service succeeded
Sat Dec 09 22:20:47 2017 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.7.7.1
Sat Dec 09 22:20:47 2017 Route addition via service succeeded
Sat Dec 09 22:20:47 2017 MANAGEMENT: >STATE:1512879647,ADD_ROUTES,
Sat Dec 09 22:20:47 2017 C:\WINDOWS\system32\route.exe ADD 67.55.92.183 MASK 255.255.255.0 192.168.0.1
Sat Dec 09 22:20:47 2017 Warning: route gateway is ambiguous: 192.168.0.1 (3 matches)
Sat Dec 09 22:20:47 2017 Route addition via service failed
Sat Dec 09 22:20:47 2017 C:\WINDOWS\system32\route.exe ADD 50.63.202.0 MASK 255.255.255.0 192.168.0.1
Sat Dec 09 22:20:47 2017 Warning: route gateway is ambiguous: 192.168.0.1 (3 matches)
Sat Dec 09 22:20:47 2017 Route addition via service failed
Sat Dec 09 22:20:47 2017 Initialization Sequence Completed
Sat Dec 09 22:20:47 2017 MANAGEMENT: >STATE:1512879647,CONNECTED,SUCCESS,10.7.7.147,173.254.255.139,443,192.168.0.153,65019

