Intermittently can't ping some hosts on client subnet
Posted: Tue May 06, 2014 10:22 pm
Howdy folks.
Server config (amblet.conf) :
Client config (ccd/mtw) :
Goal:
I want one single openVPN client (win7) to connect and expose it's local subnet to the server. The local subnet is an office network with workstations, network printers, wireless access points, et cetera. From the openVPN server in the cloud, I want to be able to ping every host residing on the openVPN client's local subnet. This is to allow a Nagios server running on the ec2 instance to monitor IT assets residing in the office network.
I've pretty much accomplished this goal, with one big problem being that not every host inside the office network is reliably pingable. Something is causing an intermittent problem with this. One day, I can ping everything. The next day, only one or two hosts out of 30 some are pingable. Example of a bad day:
Ping network printer 192.168.10.115:
Ping windows server 192.168.10.85:
On the main office router, I have a static route set up to route vpn traffic to the openVPN client (192.168.10.116). Here is the routing table for the router:
Does anything look really wrong?
Server config (amblet.conf) :
Code: Select all
port 1194
proto udp
dev tun
ca ca.crt
cert amblet.crt
key amblet.key # This file should be kept secret
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.10.0 255.255.255.0" # "dear client, please route this network over the vpn (if not ur local net)"
keepalive 10 30
comp-lzo
max-clients 5
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
verb 3
client-config-dir ccd
plugin /usr/lib/openvpn/openvpn-auth-pam.so common-auth
client-cert-not-required
username-as-common-name
route 192.168.10.0 255.255.255.0
Client config (ccd/mtw) :
Code: Select all
iroute 192.168.10.0 255.255.255.0
I want one single openVPN client (win7) to connect and expose it's local subnet to the server. The local subnet is an office network with workstations, network printers, wireless access points, et cetera. From the openVPN server in the cloud, I want to be able to ping every host residing on the openVPN client's local subnet. This is to allow a Nagios server running on the ec2 instance to monitor IT assets residing in the office network.
I've pretty much accomplished this goal, with one big problem being that not every host inside the office network is reliably pingable. Something is causing an intermittent problem with this. One day, I can ping everything. The next day, only one or two hosts out of 30 some are pingable. Example of a bad day:
Ping network printer 192.168.10.115:
Code: Select all
ping -c3 192.168.10.115
PING 192.168.10.115 (192.168.10.115) 56(84) bytes of data.
64 bytes from 192.168.10.115: icmp_req=1 ttl=254 time=45.5 ms
64 bytes from 192.168.10.115: icmp_req=2 ttl=254 time=29.7 ms
64 bytes from 192.168.10.115: icmp_req=3 ttl=254 time=33.4 msCode: Select all
ping -c3 192.168.10.85
PING 192.168.10.85 (192.168.10.85) 56(84) bytes of data.
--- 192.168.10.85 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016msCode: Select all
Destination IP Subnet Mask Default Gateway Hop Count Interface
10.8.0.0 255.255.255.0 192.168.10.116 1 eth0
x.x.x.0 255.255.255.0 * 0 eth2
192.168.10.0 255.255.255.0 * 0 eth0
default 0.0.0.0 69.28.35.1 40 eth2