Tag Info

New answers tagged

1

It turns out that the tunnel should have an IPv6 address on the source host, not the target host (the peer), for this simple ping test to work. function tunnel { local name="$1" self_ipv4="$2" self_ipv6="$3" ipv4="$4" ipv6="$5" ip tunnel add "$name" mode sit ttl 64 remote "$ipv4" local "$self_ipv4" ip -6 addr add "$self_ipv6"1 dev "$name" ip -6 ...


0

Overloaded network, or overloaded server. ('tho it's possible to cause this with traffic shaping -- on purpose, or (usually) by accident.)


2

A poor network connection. That's it. Also these results aren't inconsistent, they make perfect sense. Lets take a look at this section for example: 64 bytes from 192.168.1.9: icmp_seq=32 ttl=64 time=6811.810 ms 64 bytes from 192.168.1.9: icmp_seq=33 ttl=64 time=5817.897 ms 64 bytes from 192.168.1.9: icmp_seq=34 ttl=64 time=4820.810 ms 64 bytes from ...



Top 50 recent answers are included