LINUX.ORG.RU
ФорумAdmin

Пинг клиента OpenVPN

 


0

1

Дано:

  • Маршрутизатор 192.168.206.75
  • На Маршрутизаторе OpenVPN-клиент 172.16.206.129

Сетевой компьютер 192.168.206.125

traceroute 172.16.206.129
traceroute to 172.16.206.129 (172.16.206.129), 30 hops max, 60 byte packets
 1  192.168.206.75 (192.168.206.75)  2.192 ms  2.180 ms  2.237 ms
 2  172.16.206.129 (172.16.206.129)  19.921 ms * *

ping 172.16.206.129
PING 172.16.206.129 (172.16.206.129) 56(84) bytes of data.
64 bytes from 172.16.206.129: icmp_req=1 ttl=127 time=14.0 ms
64 bytes from 172.16.206.129: icmp_req=2 ttl=127 time=13.8 ms
64 bytes from 172.16.206.129: icmp_req=3 ttl=127 time=14.9 ms
64 bytes from 172.16.206.129: icmp_req=4 ttl=127 time=90.2 ms

 tcpdump -i tun0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun0, link-type RAW (Raw IP), capture size 65535 bytes
10:51:00.612307 IP 192.168.206.125 > 172.16.206.129: ICMP echo request, id 9110, seq 1, length 64
10:51:00.625283 IP 172.16.206.129 > 192.168.206.125: ICMP echo reply, id 9110, seq 1, length 64
10:51:01.622477 IP 192.168.206.125 > 172.16.206.129: ICMP echo request, id 9110, seq 2, length 64
10:51:01.634055 IP 172.16.206.129 > 192.168.206.125: ICMP echo reply, id 9110, seq 2, length 64
10:51:02.615225 IP 192.168.206.125 > 172.16.206.129: ICMP echo request, id 9110, seq 3, length 64
10:51:02.627568 IP 172.16.206.129 > 192.168.206.125: ICMP echo reply, id 9110, seq 3, length 64
10:51:03.615240 IP 192.168.206.125 > 172.16.206.129: ICMP echo request, id 9110, seq 4, length 64
10:51:03.630169 IP 172.16.206.129 > 192.168.206.125: ICMP echo reply, id 9110, seq 4, length 64

С него клиент доступен!

Маршрутизатор 192.168.206.75

traceroute 172.16.206.129
traceroute to 172.16.206.129 (172.16.206.129), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  *^C
ping 172.16.206.129
PING 172.16.206.129 (172.16.206.129) 56(84) bytes of data.
^C
--- 172.16.206.129 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms
tcpdump -i tun0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun0, link-type RAW (Raw IP), capture size 65535 bytes
10:52:41.507544 IP 172.16.206.1 > 172.16.206.129: ICMP echo request, id 12246, seq 1, length 64
10:52:41.519990 IP 172.16.206.129 > 172.16.206.1: ICMP echo reply, id 12246, seq 1, length 64
10:52:42.507819 IP 172.16.206.1 > 172.16.206.129: ICMP echo request, id 12246, seq 2, length 64
10:52:42.520061 IP 172.16.206.129 > 172.16.206.1: ICMP echo reply, id 12246, seq 2, length 64
10:52:43.507774 IP 172.16.206.1 > 172.16.206.129: ICMP echo request, id 12246, seq 3, length 64
10:52:43.519903 IP 172.16.206.129 > 172.16.206.1: ICMP echo reply, id 12246, seq 3, length 64
ifconfig tun0
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:172.16.206.1  P-t-P:172.16.206.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1110 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1827 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:146522 (143.0 KiB)  TX bytes:1066112 (1.0 MiB)

Вижу ICMP echo reply на 172.16.206.1, но ping молчит.

ping 172.16.206.1
PING 172.16.206.1 (172.16.206.1) 56(84) bytes of data.
64 bytes from 172.16.206.1: icmp_req=1 ttl=64 time=0.055 ms
64 bytes from 172.16.206.1: icmp_req=2 ttl=64 time=0.044 ms
64 bytes from 172.16.206.1: icmp_req=3 ttl=64 time=0.055 ms
^C

★★★★★

Последнее исправление: petav (всего исправлений: 2)

Ответ на: комментарий от petav

Можно и по таким условиям порезать. Но раз решилось обратным маршрутом, то отлично.

turtle_bazon ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.