Hi,
I have a problem to get Google services (gmail, youtube, i.e.) over ipv6 tunnel:
ping ipv6 ipv6.google.com size 1000 source Tun1
Type escape sequence to abort.
Sending 5, 1000-byte ICMP Echos to 2A00:1450:4010:C08::65, timeout is 2 seconds:
Packet sent with a source address of <omitted>
CCCCC
Success rate is 0 percent (0/5)
...
ping ipv6 ipv6.google.com source Tun1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2A00:1450:4010:C04::65, timeout is 2 seconds:
Packet sent with a source address of <omitted>
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms
But other hosts are available:
ping ipv6 www.ipv6tf.org size 1000 source Tun1
Type escape sequence to abort.
Sending 5, 1000-byte ICMP Echos to 2A02:2E00:F000:1500:20C:29FF:FEF3:F557, timeout is 2 seconds:
Packet sent with a source address of <omitted>
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 160/163/172 ms
ping ipv6 ipv6.nnm-club.me size 1000 source Tun1
Type escape sequence to abort.
Sending 5, 1000-byte ICMP Echos to 2001:470:26:482::2, timeout is 2 seconds:
Packet sent with a source address of <omitted>
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 68/71/76 ms
Configuration of ipv6 tunnel:
sh run int tun1
Building configuration...
Current configuration : 352 bytes
!
interface Tunnel1
description -= Hurricane Electric IPv6 Tunnel Broker =-
no ip address
ipv6 address <omitted>
ipv6 enable
ipv6 traffic-filter ToTunnelBroker in
ipv6 mtu 1280
ipv6 inspect tunnel-broker out
ipv6 virtual-reassembly
keepalive 10 3
tunnel source Loopback1
tunnel destination <omitted>
tunnel mode ipv6ip
end
How can I fix ?
I'm confused...what exactly are you trying to accomplish?
Sites gmail.com, yoube.com, google.com open too slow, because packets size bigger than 64 bytes are dropped:
ping6 ipv6.google.com -s 64
PING ipv6.google.com(2a00:1450:4010:c07::65) 64 data bytes
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=1 ttl=55 time=86.9 ms
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=2 ttl=55 time=88.1 ms
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=3 ttl=55 time=86.1 ms
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=4 ttl=55 time=86.1 ms
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=5 ttl=55 time=88.1 ms
ping6 ipv6.google.com -s 65
PING ipv6.google.com(2a00:1450:4010:c07::65) 65 data bytes
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=1 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=2 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=3 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=4 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=5 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=6 ttl=55 (truncated)
72 bytes from 2a00:1450:4010:c07::65: icmp_seq=7 ttl=55 (truncated)
this is only an issue with he.net's tunnel. You can sign up for a gogonet tunnel and it works fine.
You're likely hitting a different cluster of Google's which isn't exhibiting this on a gogo tunnel. SixXS was also seeing this in spots. As it is, it should be resolved according to Google.
Quote from: kcochran on November 09, 2014, 06:31:41 PM
You're likely hitting a different cluster of Google's which isn't exhibiting this on a gogo tunnel. SixXS was also seeing this in spots. As it is, it should be resolved according to Google.
Thanks you. I changed ipv6 forwarders in my named.conf. After that the problem was fixed:
ping6 ipv6.google.com -s 1400
PING ipv6.google.com(fra07s30-in-x03.1e100.net) 1400 data bytes
1408 bytes from fra07s30-in-x03.1e100.net: icmp_seq=1 ttl=57 time=61.8 ms
1408 bytes from fra07s30-in-x03.1e100.net: icmp_seq=2 ttl=57 time=61.0 ms
1408 bytes from fra07s30-in-x03.1e100.net: icmp_seq=3 ttl=57 time=61.7 ms