VPN Connected bu not able to access anything

This forum is for general conversation and user-user networking.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Post Reply
satyendrasinghchouhan
OpenVpn Newbie
Posts: 1
Joined: Fri Jul 06, 2018 5:20 pm

VPN Connected bu not able to access anything

Post by satyendrasinghchouhan » Fri Jul 06, 2018 5:23 pm

Dear ,

I have connected open vpn and it is showing status connected but I am not able to access anything. what is problem pls resolve problem as soon problem.

Regards & Thanks
Satyendra Singh


Here Log:-

Fri Jul 06 22:41:04 2018 CrSSL(OpenVPN) 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on May 22 2013
Fri Jul 06 22:42:17 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Jul 06 22:42:17 2018 NOTE: CrSSL(OpenVPN) 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Fri Jul 06 22:42:17 2018 LZO compression initialized
Fri Jul 06 22:42:17 2018 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Fri Jul 06 22:42:17 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Fri Jul 06 22:42:17 2018 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Fri Jul 06 22:42:17 2018 Local Options hash (VER=V4): '69109d17'
Fri Jul 06 22:42:17 2018 Expected Remote Options hash (VER=V4): 'c0103fa8'
Fri Jul 06 22:42:17 2018 Attempting to establish TCP connection with 111.93.123.234:8443
Fri Jul 06 22:42:18 2018 TCP connection established with 111.93.123.234:8443
Fri Jul 06 22:42:18 2018 TCPv4_CLIENT link local: [undef]
Fri Jul 06 22:42:18 2018 TCPv4_CLIENT link remote: 111.93.123.234:8443
Fri Jul 06 22:42:18 2018 TLS: Initial packet from 111.93.123.234:8443, sid=5c3fd04f f0a1a252
Fri Jul 06 22:42:22 2018 VERIFY OK: depth=1, /C=IN/ST=Gujarat/L=Ahmedabad/O=Cyberoam/OU=Cyberoam Appliance/CN=Cyberoam Appliance CA_C20312527646/emailAddress=info@cyberoam.com
Fri Jul 06 22:42:22 2018 VERIFY OK: depth=0, /C=IN/ST=Gujarat/L=Ahmedabad/O=Cyberoam/OU=Cyberoam Appliance/CN=CyberoamApplianceCertificate_C20312527646/emailAddress=info@cyberoam.com
Fri Jul 06 22:42:31 2018 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jul 06 22:42:31 2018 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jul 06 22:42:31 2018 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jul 06 22:42:31 2018 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jul 06 22:42:31 2018 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Fri Jul 06 22:42:31 2018 [CyberoamApplianceCertificate_C20312527646] Peer Connection Initiated with 111.93.123.234:8443
Fri Jul 06 22:42:33 2018 SENT CONTROL [CyberoamApplianceCertificate_C20312527646]: 'PUSH_REQUEST' (status=1)
Fri Jul 06 22:42:35 2018 PUSH: Received control message: 'PUSH_REPLY,topology subnet,route-gateway 172.16.2.10,dhcp-option DNS 4.2.2.2,dhcp-option DNS 8.8.8.8,inactive 900 65500,ping 60,ping-restart 18000,route 192.168.1.23 255.255.255.255,route 192.168.1.20 255.255.255.255,route 192.168.1.5 255.255.255.255,route 192.168.1.44 255.255.255.255,route 192.168.1.6 255.255.255.255,route 192.168.1.135 255.255.255.255,route 192.168.1.9 255.255.255.255,route 192.168.1.7 255.255.255.255,route 192.168.1.8 255.255.255.255,route 192.168.1.84 255.255.255.255,route 192.168.1.10 255.255.255.255,route 192.168.1.19 255.255.255.255,route 192.168.1.33 255.255.255.255,route 192.168.3.204 255.255.255.255,route 192.168.1.17 255.255.255.255,ifconfig 172.16.2.11 255.255.255.0'
Fri Jul 06 22:42:35 2018 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jul 06 22:42:35 2018 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jul 06 22:42:35 2018 OPTIONS IMPORT: route options modified
Fri Jul 06 22:42:35 2018 OPTIONS IMPORT: route-related options modified
Fri Jul 06 22:42:35 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Jul 06 22:42:35 2018 ROUTE default_gateway=192.168.43.1
Fri Jul 06 22:42:35 2018 TAP-WIN32 device [Ethernet 5] opened: \\.\Global\{F649BEB9-4B2D-4960-8D73-5FDAFA826CE2}.tap
Fri Jul 06 22:42:35 2018 TAP-Win32 Driver Version 9.9
Fri Jul 06 22:42:35 2018 TAP-Win32 MTU=1500
Fri Jul 06 22:42:35 2018 Set TAP-Win32 TUN subnet mode network/local/netmask = 172.16.2.0/172.16.2.11/255.255.255.0 [SUCCEEDED]
Fri Jul 06 22:42:35 2018 Notified TAP-Win32 driver to set a DHCP IP/netmask of 172.16.2.11/255.255.255.0 on interface {F649BEB9-4B2D-4960-8D73-5FDAFA826CE2} [DHCP-serv: 172.16.2.254, lease-time: 31536000]
Fri Jul 06 22:42:35 2018 Successful ARP Flush on interface [28] {F649BEB9-4B2D-4960-8D73-5FDAFA826CE2}
Fri Jul 06 22:42:40 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:40 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:45 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:45 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:46 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:46 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:47 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:47 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:48 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:48 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:49 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:49 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:50 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:50 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:51 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:51 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:52 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:52 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:53 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:53 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:55 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:55 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:56 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:56 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:57 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:57 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:58 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:58 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:42:59 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:42:59 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:00 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:00 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:01 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:01 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:02 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:02 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:03 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:03 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:05 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:05 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:06 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:06 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:07 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:07 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:08 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:08 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:09 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:09 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Jul 06 22:43:11 2018 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Fri Jul 06 22:43:11 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.23 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:11 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:11 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:11 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:11 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:11 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:11 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.23 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:11 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.20 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:11 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:11 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:11 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:11 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:11 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.20 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:12 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.5 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:12 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:12 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:12 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.5 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:12 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.44 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:12 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:12 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:12 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.44 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:12 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.6 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:12 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:12 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:12 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.6 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:12 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.135 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:12 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:12 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:12 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:12 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.135 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:13 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.9 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:13 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:13 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:13 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.9 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:13 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.7 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:13 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:13 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:13 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.7 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:13 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.8 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:13 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:13 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:13 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.8 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:13 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.84 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:13 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:13 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:13 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:13 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:14 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.84 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:14 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.10 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:14 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:14 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:14 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:14 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:14 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:15 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.10 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:15 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.19 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:15 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:15 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:15 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:15 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:15 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:15 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.19 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:15 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.33 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:15 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:15 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:15 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:15 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:15 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:16 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.33 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:16 2018 C:\WINDOWS\system32\route.exe ADD 192.168.3.204 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:16 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:16 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:16 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:16 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:16 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:16 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.3.204 MASK 255.255.255.255 172.16.2.10 succeeded
Fri Jul 06 22:43:16 2018 C:\WINDOWS\system32\route.exe ADD 192.168.1.17 MASK 255.255.255.255 172.16.2.10
Fri Jul 06 22:43:16 2018 Warning: route gateway is not reachable on any active network adapters: 172.16.2.10
Fri Jul 06 22:43:16 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 06 22:43:16 2018 Route addition fallback to route.exe
Fri Jul 06 22:43:16 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:16 2018 WriteFile() to pipe was successful.
Fri Jul 06 22:43:17 2018 openvpn_execve: command C:\WINDOWS\system32\route.exe ADD 192.168.1.17 MASK 255.255.255.255 172.16.2.10 succeeded
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.43.1 p=0 i=22 t=4 pr=3 a=749 h=0 m=55/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=305026 h=0 m=331/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=305026 h=0 m=331/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=305026 h=0 m=331/0/0/0/0
192.168.1.5 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=5 h=0 m=56/0/0/0/0
192.168.1.6 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=4 h=0 m=56/0/0/0/0
192.168.1.7 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=3 h=0 m=56/0/0/0/0
192.168.1.8 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=3 h=0 m=56/0/0/0/0
192.168.1.9 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=3 h=0 m=56/0/0/0/0
192.168.1.10 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=2 h=0 m=56/0/0/0/0
192.168.1.17 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=0 h=0 m=56/0/0/0/0
192.168.1.19 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=2 h=0 m=56/0/0/0/0
192.168.1.20 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=5 h=0 m=56/0/0/0/0
192.168.1.23 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=6 h=0 m=56/0/0/0/0
192.168.1.33 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=1 h=0 m=56/0/0/0/0
192.168.1.44 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=5 h=0 m=56/0/0/0/0
192.168.1.84 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=2 h=0 m=56/0/0/0/0
192.168.1.135 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=4 h=0 m=56/0/0/0/0
192.168.3.204 255.255.255.255 172.16.2.10 p=0 i=22 t=4 pr=3 a=1 h=0 m=56/0/0/0/0
192.168.43.0 255.255.255.0 192.168.43.61 p=0 i=22 t=3 pr=2 a=749 h=0 m=311/0/0/0/0
192.168.43.61 255.255.255.255 192.168.43.61 p=0 i=22 t=3 pr=2 a=749 h=0 m=311/0/0/0/0
192.168.43.255 255.255.255.255 192.168.43.61 p=0 i=22 t=3 pr=2 a=749 h=0 m=311/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=305026 h=0 m=331/0/0/0/0
224.0.0.0 240.0.0.0 192.168.43.61 p=0 i=22 t=3 pr=2 a=754 h=0 m=311/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=305026 h=0 m=331/0/0/0/0
255.255.255.255 255.255.255.255 192.168.43.61 p=0 i=22 t=3 pr=2 a=754 h=0 m=311/0/0/0/0
SYSTEM ADAPTER LIST
Realtek PCIe FE Family Controller
Index = 10
GUID = {413982BB-C18D-4B51-BCD4-943F72FA5456}
IP = 0.0.0.0/0.0.0.0
MAC = 28:92:4a:27:e3:c8
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Tue Feb 23 16:32:04 1971
DNS SERV =
Bluetooth Device (Personal Area Network)
Index = 6
GUID = {1DE89FA1-B821-416E-894E-AA8FE4E14960}
IP = 0.0.0.0/0.0.0.0
MAC = 20:68:9d:4b:ad:4a
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Tue Feb 23 16:42:44 1971
DNS SERV =
Fortinet Virtual Ethernet Adapter (NDIS 6.30)
Index = 17
GUID = {6C8D81C1-5445-4B40-827F-F71644D3CC86}
IP = 0.0.0.0/0.0.0.0
MAC = 00:09:0f:fe:00:01
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Tue Feb 23 16:53:24 1971
DNS SERV =
TAP-Windows Adapter V9
Index = 28
GUID = {F649BEB9-4B2D-4960-8D73-5FDAFA826CE2}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:f6:49:be:b9
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Tue Feb 23 17:04:04 1971
DNS SERV =
Qualcomm Atheros AR9485 802.11b|g|n WiFi Adapter
Index = 22
GUID = {BE8D0739-E304-4110-B224-8DF75FE8BEAA}
IP = 192.168.43.61/255.255.255.0
MAC = 20:68:9d:4b:50:52
GATEWAY = 192.168.43.1/255.255.255.255
DHCP SERV = 192.168.43.1/255.255.255.255
DHCP LEASE OBTAINED = Fri Jul 06 22:30:48 2018
DHCP LEASE EXPIRES = Tue Feb 23 17:14:44 1971
DNS SERV = 192.168.43.1/255.255.255.255
Microsoft Wi-Fi Direct Virtual Adapter #4
Index = 19
GUID = {7E43AE6E-7D8D-4E1E-9139-9727E3DC771C}
IP = 0.0.0.0/0.0.0.0
MAC = 12:68:9d:4b:50:52
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Thu Jan 01 05:30:00 1970
DNS SERV =
Microsoft Wi-Fi Direct Virtual Adapter #5
Index = 26
GUID = {F1A5B919-7D92-47D9-AF75-1D83CBED11A7}
IP = 0.0.0.0/0.0.0.0
MAC = 22:68:9d:4b:50:52
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jul 06 22:43:17 2018
DHCP LEASE EXPIRES = Thu Jan 01 05:30:00 1970
DNS SERV =
Fri Jul 06 22:43:17 2018 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: VPN Connected bu not able to access anything

Post by TinCanTech » Fri Jul 06, 2018 7:09 pm

satyendrasinghchouhan wrote:
Fri Jul 06, 2018 5:23 pm
CrSSL(OpenVPN) 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on May 22 2013
upgrade .. :roll:

Post Reply