Pinging Certain Klients / Servers - (SOLVED)
-
Hi Everyone
I know this have been discused before, but i think my problem is very strange it is as follows.
I can connect with openvpn no problem, i can ping servers firewalls etc, but some klients i can't ping, let my narrow this.
I can ping the servers at 10.0.0.1, 10.0.0.2 WINDOWS Servers, 10.0.0.254 pfsense firewall and some NAS storage on 10.0.0.151, 10.0.0.154
But when i try to ping 10.0.0.100 a windows client computer no go and it is allowed to ping in firewall, and i can ping it from the servers and other clients internaly on the network.
I try also to ping some hardware on 10.0.0.161, 162, 163, 164 no go and i can ping theese also internaly on the network.Firewall setup is.
–----Start------
Address Pool = 10.10.0.0/16
Local Network = 10.0.0.0/16
------End-------Open VPN log on client.
------Start------
Mon Feb 22 08:31:19 2010 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009
Mon Feb 22 08:31:19 2010 NOTE: OpenVPN 2.1 requires '–script-security 2' or higher to call user-defined scripts or executables
Mon Feb 22 08:31:19 2010 LZO compression initialized
Mon Feb 22 08:31:19 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Mon Feb 22 08:31:19 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Mon Feb 22 08:31:19 2010 Local Options hash (VER=V4): '41690919'
Mon Feb 22 08:31:19 2010 Expected Remote Options hash (VER=V4): '530fdded'
Mon Feb 22 08:31:19 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Mon Feb 22 08:31:19 2010 UDPv4 link local: [undef]
Mon Feb 22 08:31:19 2010 UDPv4 link remote: X.X.X.66:1194
Mon Feb 22 08:31:19 2010 TLS: Initial packet from X.X.X.66:1194, sid=f3b0fc36 2b0bda07
Mon Feb 22 08:31:20 2010 VERIFY OK:
Mon Feb 22 08:31:20 2010 VERIFY OK:
Mon Feb 22 08:31:20 2010 VERIFY OK:
Mon Feb 22 08:31:23 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Feb 22 08:31:23 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Feb 22 08:31:23 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Feb 22 08:31:23 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Feb 22 08:31:23 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Mon Feb 22 08:31:23 2010 [server] Peer Connection Initiated with X.X.X.66:1194
Mon Feb 22 08:31:25 2010 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Mon Feb 22 08:31:25 2010 PUSH: Received control message: 'PUSH_REPLY,route 10.0.0.0 255.255.0.0,dhcp-option DISABLE-NBT,route 10.10.0.1,ping 10,ping-restart 60,ifconfig 10.10.0.6 10.10.0.5'
Mon Feb 22 08:31:25 2010 OPTIONS IMPORT: timers and/or timeouts modified
Mon Feb 22 08:31:25 2010 OPTIONS IMPORT: –ifconfig/up options modified
Mon Feb 22 08:31:25 2010 OPTIONS IMPORT: route options modified
Mon Feb 22 08:31:25 2010 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Feb 22 08:31:25 2010 ROUTE default_gateway=79.138.230.176
Mon Feb 22 08:31:25 2010 TAP-WIN32 device [LAN-forbindelse 2] opened: \.\Global{58A475E2-C0FB-4675-85F7-3F68B32ECA8C}.tap
Mon Feb 22 08:31:25 2010 TAP-Win32 Driver Version 9.6
Mon Feb 22 08:31:25 2010 TAP-Win32 MTU=1500
Mon Feb 22 08:31:25 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.10.0.6/255.255.255.252 on interface {58A475E2-C0FB-4675-85F7-3F68B32ECA8C} [DHCP-serv: 10.10.0.5, lease-time: 31536000]
Mon Feb 22 08:31:25 2010 Successful ARP Flush on interface [4] {58A475E2-C0FB-4675-85F7-3F68B32ECA8C}
Mon Feb 22 08:31:31 2010 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Mon Feb 22 08:31:31 2010 C:\WINDOWS\system32\route.exe ADD 10.0.0.0 MASK 255.255.0.0 10.10.0.5
Mon Feb 22 08:31:31 2010 Route addition via IPAPI succeeded [adaptive]
Mon Feb 22 08:31:31 2010 C:\WINDOWS\system32\route.exe ADD 10.10.0.1 MASK 255.255.255.255 10.10.0.5
Mon Feb 22 08:31:31 2010 Route addition via IPAPI succeeded [adaptive]
Mon Feb 22 08:31:31 2010 Initialization Sequence Completed
–----END-------- -
If you guys have this problem also and running Captive Portal remember thoose clients you need to connect to needed to be added to Allowed IP Adresses.