ulmwind wrote:jsl17, the result is very strange, ping time is too great for direct connection to router.
Now please, reproduce your previous result, ping FROM Location B 172.29.240.1, 172.29.240.154 Also tracert from the same location the same IPs.
Location B 172.28.240.10
traceroute to 172.29.240.154 (172.29.240.154) , 5 relative hops max, 52 byte packets
1 172.27.232.1 (172.27.232.1) 90.026 ms 112.281 ms 117.892 ms "OVPN Access Server on VPS"
2 172.28.240.20 (172.28.240.20) 93.763 ms 99.444 ms 105.478 ms "Router VPN IP"
3 172.28.240.20 (172.28.240.20) 87.108 ms 99.008 ms 109.025 ms
traceroute to 172.29.240.1 (172.29.240.1) , 5 relative hops max, 52 byte packets
1 172.27.232.1 (172.27.232.1) 1309.572 ms 1339.628 ms 1449.248 ms "OVPN Access Server on VPS"
2 172.29.240.1 (172.29.240.1) 794.564 ms 799.483 ms 803.321 ms "Router LAN-port IP"
Location C
Router
172.28.240.20 VPN IP
172.29.240.1 LAN IP
PING 172.29.240.154 (172.29.240.154): 56 data bytes
64 bytes from 172.29.240.154: seq=0 ttl=128 time=0.900 ms
64 bytes from 172.29.240.154: seq=1 ttl=128 time=0.680 ms
64 bytes from 172.29.240.154: seq=2 ttl=128 time=0.660 ms
64 bytes from 172.29.240.154: seq=3 ttl=128 time=0.600 ms
64 bytes from 172.29.240.154: seq=4 ttl=128 time=0.620 ms
--- 172.29.240.154 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.600/0.692/0.900 ms
traceroute to 172.29.240.154 (172.29.240.154), 30 hops max, 38 byte packets
1 172.29.240.154 0.680 ms
Maybe high ping, but cable is only 30cm
Firewall settings
https link drive.google.com/file/d/0B20DIZI72_A-eDc0VXFoTGdlUU0/view?usp=sharing
(Last edited by jsl17 on 18 Dec 2016, 16:14)