|
Ticket ID: SIXXS #1229972 Ticket Status: User PoP: nlams05 - SURFnet (Amsterdam)
tunnel T23403, can't ping endpoint.
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 14 October 2009 18:44:15
Having some probleems to make the tunnel work.
Everthing looks fine but I cant ping the endnpoint.
Tunnel Id : T23403
PoP Name : nlams05 (nl.surfnet [AS1103])
TIC Server : tic.sixxs.net (which is the default in AICCU)
Your Location : hilversum, nl
SixXS IPv6 : 2001:610:600:596::1/64
Your IPv6 : 2001:610:600:596::2/64
SixXS IPv4 : 192.87.102.107
Tunnel Type : Dynamic (ayiya)
This are the ping results.
kotenxs:~ admin$ ping6 2001:610:600:596::1
PING6(56=40+8+8 bytes) 2001:610:600:596::2 --> 2001:610:600:596::1
Request timeout for icmp_seq=0
Request timeout for icmp_seq=1
Request timeout for icmp_seq=2
Request timeout for icmp_seq=3
Request timeout for icmp_seq=4
Request timeout for icmp_seq=5
Request timeout for icmp_seq=6
Request timeout for icmp_seq=7
Request timeout for icmp_seq=8
^C
--- 2001:610:600:596::1 ping6 statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
kotenxs:~ admin$ ping6 2001:610:600:596::2
PING6(56=40+8+8 bytes) 2001:610:600:596::2 --> 2001:610:600:596::2
16 bytes from 2001:610:600:596::2, icmp_seq=0 hlim=64 time=0.142 ms
16 bytes from 2001:610:600:596::2, icmp_seq=1 hlim=64 time=0.129 ms
16 bytes from 2001:610:600:596::2, icmp_seq=2 hlim=64 time=0.150 ms
16 bytes from 2001:610:600:596::2, icmp_seq=3 hlim=64 time=0.127 ms
16 bytes from 2001:610:600:596::2, icmp_seq=4 hlim=64 time=0.152 ms
16 bytes from 2001:610:600:596::2, icmp_seq=5 hlim=64 time=0.131 ms
16 bytes from 2001:610:600:596::2, icmp_seq=6 hlim=64 time=0.133 ms
^C
--- 2001:610:600:596::2 ping6 statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.127/0.138/0.152/0.009 ms
And a piece of the tcpdump
15:57:16.217831 IP kotenxs.vankoten.nl.asia > all-systems.mcast.net.asia: UDP, length 39
15:57:16.320062 IP kotenxs.vankoten.nl.61867 > l.root-servers.net.domain: 4276 [1au] PTR? 1.0.0.224.in-addr.arpa. (51)
15:57:16.373137 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3208957:3215925, ack 289, win 33304, options [nop,nop,TS val 421014626 ecr 1019696810], length 6968
15:57:16.373473 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3215925:3216105, ack 289, win 33304, options [nop,nop,TS val 421014626 ecr 1019696810], length 180
15:57:16.373673 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3216105:3217592, ack 289, win 33304, options [nop,nop,TS val 421014626 ecr 1019696810], length 1487
15:57:16.373707 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3217592:3217844, ack 289, win 33304, options [nop,nop,TS val 421014626 ecr 1019696810], length 252
15:57:16.373951 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3217844:3219522, ack 289, win 33304, options [nop,nop,TS val 421014626 ecr 1019696810], length 1678
15:57:16.438902 IP l.root-servers.net.domain > kotenxs.vankoten.nl.61867: 4276- 0/4/1 (167)
15:57:16.439323 IP 192.168.69.54.50864 > kotenxs.vankoten.nl.vnc-server: Flags [.], ack 3211853, win 65535, options [nop,nop,TS val 1019696814 ecr 421014626], length 0
15:57:16.439367 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [.], seq 3219522:3226333, ack 289, win 33304, options [nop,nop,TS val 421014627 ecr 1019696814], length 6811
15:57:16.439673 IP kotenxs.vankoten.nl.53571 > c.gtld-servers.net.domain: 27777% [1au] A? ns.isi.edu. (39)
15:57:16.439792 IP kotenxs.vankoten.nl.60229 > g.gtld-servers.net.domain: 37747% [1au] AAAA? ns.isi.edu. (39)
15:57:16.440024 IP kotenxs.vankoten.nl.56594 > a.gtld-servers.net.domain: 49096% [1au] A? nic.near.net. (41)
15:57:16.440175 IP kotenxs.vankoten.nl.61413 > k.gtld-servers.net.domain: 60900% [1au] AAAA? nic.near.net. (41)
15:57:16.440330 IP kotenxs.vankoten.nl.64874 > c.gtld-servers.net.domain: 2158% [1au] A? flag.ep.net. (40)
15:57:16.440483 IP kotenxs.vankoten.nl.65440 > c.gtld-servers.net.domain: 51382% [1au] AAAA? flag.ep.net. (40)
15:57:16.440674 IP kotenxs.vankoten.nl.63349 > se-dns.gbg.netnod.se.domain: 32400% [1au] A? strul.stupi.se. (43)
15:57:16.440795 IP kotenxs.vankoten.nl.58144 > se1.dnsnode.net.domain: 35280% [1au] AAAA? strul.stupi.se. (43)
15:57:16.446540 IP 192.168.69.54.50864 > kotenxs.vankoten.nl.vnc-server: Flags [.], ack 3214749, win 65535, options [nop,nop,TS val 1019696814 ecr 421014626], length 0
15:57:16.446608 IP kotenxs.vankoten.nl.vnc-server > 192.168.69.54.50864: Flags [P.], seq 3226333:3228262, ack 289, win 33304, options [nop,nop,TS val 421014627 ecr 1019696814], length 1929
15:57:16.463608 IP k.gtld-servers.net.domain > kotenxs.vankoten.nl.61413: 60900- 0/2/1 (90)
^C15:57:16.464122 IP kotenxs.vankoten.nl.54932 > l.de.net.domain: 41942% [1au] A? ns5.opm-server.de. (46)
2553 packets captured
5124 packets received by filter
2443 packets dropped by kernel
sh-3.2#
Check white to friend of my (the have also a tunnel) we really cant see whats wrong.
tunnel T23403, can't ping endpoint.
Shadow Hawkins on Wednesday, 14 October 2009 18:52:58
Set my tunnel from ayiya to 6to4 static.
Tunnel Name My First Tunnel
PoP Name nlams05
PoP Location Amsterdam, Netherlands, The Netherlands, The
PoP IPv4 192.87.102.107
TIC Server tic.sixxs.net (default in AICCU)
Your Location hilversum, Netherlands, The Netherlands, The
Your IPv4 24.132.122.103
IPv6 Prefix 2001:610:600:596::1/64
PoP IPv6 2001:610:600:596::1
Your IPv6 2001:610:600:596::2
Created 2009-10-05 15:51:57 CEST
State Enabled
still can't ping the eind point.
State change: user
The state of this ticket has been changed to user
tunnel T23403, can't ping endpoint.
I see DNS traffic (at least I assume from the hostnames) and some traffic going to an RFC1918 address. But really, what does that have to do with IPv6 tunneled packets in any way?
Please read that big orange box that you should clearly see when posting and follow the instructions as pointed from there.
tunnel T23403, can't ping endpoint.
Shadow Hawkins on Friday, 16 October 2009 13:48:47
Thanks Jeroen
Thanks, below as you can see it works now, and I did nothing, just ping.
sh-3.2# ping6 2001:610:600:596::1
PING6(56=40+8+8 bytes) 2001:610:600:596::2 --> 2001:610:600:596::1
16 bytes from 2001:610:600:596::1, icmp_seq=0 hlim=64 time=17.999 ms
16 bytes from 2001:610:600:596::1, icmp_seq=1 hlim=64 time=11.838 ms
16 bytes from 2001:610:600:596::1, icmp_seq=2 hlim=64 time=9.767 ms
16 bytes from 2001:610:600:596::1, icmp_seq=3 hlim=64 time=10.144 ms
16 bytes from 2001:610:600:596::1, icmp_seq=4 hlim=64 time=10.442 ms
16 bytes from 2001:610:600:596::1, icmp_seq=5 hlim=64 time=10.126 ms
16 bytes from 2001:610:600:596::1, icmp_seq=6 hlim=64 time=11.962 ms
16 bytes from 2001:610:600:596::1, icmp_seq=7 hlim=64 time=9.905 ms
16 bytes from 2001:610:600:596::1, icmp_seq=8 hlim=64 time=6.127 ms
16 bytes from 2001:610:600:596::1, icmp_seq=9 hlim=64 time=9.748 ms
16 bytes from 2001:610:600:596::1, icmp_seq=10 hlim=64 time=12.428 ms
16 bytes from 2001:610:600:596::1, icmp_seq=11 hlim=64 time=9.496 ms
16 bytes from 2001:610:600:596::1, icmp_seq=12 hlim=64 time=9.630 ms
16 bytes from 2001:610:600:596::1, icmp_seq=13 hlim=64 time=9.754 ms
16 bytes from 2001:610:600:596::1, icmp_seq=14 hlim=64 time=9.844 ms
16 bytes from 2001:610:600:596::1, icmp_seq=15 hlim=64 time=9.939 ms
16 bytes from 2001:610:600:596::1, icmp_seq=16 hlim=64 time=10.375 ms
16 bytes from 2001:610:600:596::1, icmp_seq=17 hlim=64 time=10.185 ms
16 bytes from 2001:610:600:596::1, icmp_seq=18 hlim=64 time=17.616 ms
^C
--- 2001:610:600:596::1 ping6 statistics ---
19 packets transmitted, 19 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 6.127/10.912/17.999/2.669 ms
|
![[ch]](/s/countries/ch.gif)
on Thursday, 15 October 2009 18:35:10
Posting is only allowed when you are