|
Ticket ID: SIXXS #3134701 Ticket Status: Works for Me PoP: usbos01 - OCCAID Inc. (Boston, Massachusetts)
New Route Problem
![[us]](/s/countries/us.gif) Shadow Hawkins on Wednesday, 01 December 2010 13:49:46
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
Hello,
I have been assigned a new route and it appears that it is not working. I can't ping hosts in the subnet and no traffic is routed to my tunnel. Details follow:
Username : KM2099-RIPE
Route : R20654
PoP Name : usbos01 (OCCAI [AS30071])
Subnet IPv6 : 2001:4830:114a::/48
Routed to : 2001:4830:1100:fa::2/64
Your IPv4 : 24.191.7.211
ifconfig output from 24.191.7.211:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33200
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:00:24:c2:47:b0
priority: 0
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::200:24ff:fec2:47b0%sis0 prefixlen 64 scopeid 0x1
inet 24.191.7.211 netmask 0xfffffc00 broadcast 255.255.255.255
sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:00:24:c2:47:b1
priority: 0
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 172.16.1.1 netmask 0xffffff00 broadcast 172.16.1.255
inet6 fe80::200:24ff:fec2:47b1%sis1 prefixlen 64 scopeid 0x2
inet6 2001:4830:11a4:1::1 prefixlen 64
sis2: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:00:24:c2:47:b2
priority: 0
media: Ethernet autoselect (none)
status: no carrier
enc0: flags=0<>
priority: 0
groups: enc
status: active
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
priority: 0
groups: gif egress
physical address inet 24.191.7.211 --> 216.93.250.26
inet6 fe80::200:24ff:fec2:47b0%gif0 -> prefixlen 64 scopeid 0x6
inet6 2001:4830:1100:fa::2 -> 2001:4830:1100:fa::1 prefixlen 128
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33200
priority: 0
groups: pflog
From an external ipv6 address (2001:4830:1100:f4::2) I can ping6 and traceroute6 to the tunnel ip 2001:4830:1100:fa::2
$ ping6 2001:4830:1100:fa::2
PING6(56=40+8+8 bytes) 2001:4830:1100:f4::2 --> 2001:4830:1100:fa::2
16 bytes from 2001:4830:1100:fa::2, icmp_seq=0 hlim=63 time=32.692 ms
16 bytes from 2001:4830:1100:fa::2, icmp_seq=1 hlim=63 time=35.336 ms
^C
--- 2001:4830:1100:fa::2 ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 32.692/34.014/35.336/1.322 ms
$ traceroute6 2001:4830:1100:fa::2
traceroute6 to 2001:4830:1100:fa::2 (2001:4830:1100:fa::2) from 2001:4830:1100:f4::2, 64 hops max, 12 byte packets
1 gw-245.bos-01.us.sixxs.net 16.997 ms 17.48 ms 15.817 ms
2 cl-251.bos-01.us.sixxs.net 33.012 ms 31.081 ms 31.291 ms
However both ping6 and traceroute6 to a host in the subnet fail:
$ traceroute6 2001:4830:11a4:1::1
traceroute6 to 2001:4830:11a4:1::1 (2001:4830:11a4:1::1) from 2001:4830:1100:f4::2, 64 hops max, 12 byte packets
1 gw-245.bos-01.us.sixxs.net 18.84 ms !N 17.16 ms !N 21.286 ms !N
$ ping6 2001:4830:11a4:1::1
PING6(56=40+8+8 bytes) 2001:4830:1100:f4::2 --> 2001:4830:11a4:1::1
^C
--- 2001:4830:11a4:1::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
While pinging from external host 2001:4830:1100:f4::2 to an address in the subnet 2001:4830:11a4:1::1, tcpdump on the tunnel shows no traffic:
# tcpdump -i sis0 host 216.93.250.26
tcpdump: listening on sis0, link-type EN10MB
^C
136 packets received by filter
0 packets dropped by kernel
If I'm not mistaken this means the route to the subnet is not activated or misconfigured.
Thank You,
-Kurt Miller (KM2099-RIPE)
New Route Problem
Shadow Hawkins on Wednesday, 01 December 2010 13:51:42
Hi,
Sorry I did read the header/Reporting Problems section and intended to delete it but forgot.
-Kurt
New Route Problem
Works for me from the PoP:
traceroute to 2001:4830:114a:: (2001:4830:114a::), 30 hops max, 40 byte packets
1 cl-251.bos-01.us.sixxs.net (2001:4830:1100:fa::2) 20.263 ms 20.210 ms 20.177 ms
and from Switzerland:
traceroute to 2001:4830:114a:: (2001:4830:114a::), 30 hops max, 80 byte packets
1 2001:788:2:117:ffff:ffff:ffff:ffff (2001:788:2:117:ffff:ffff:ffff:ffff) 1.025 ms 0.929 ms 0.910 ms
2 2001:788::27 (2001:788::27) 0.895 ms 0.877 ms 0.861 ms
3 2001:41e0:6203:3000::1 (2001:41e0:6203:3000::1) 1.339 ms 1.326 ms 1.309 ms
4 2a02:2528:2:8::1 (2a02:2528:2:8::1) 2.537 ms 2.524 ms 2.598 ms
5 2a02:2528:2:1::2 (2a02:2528:2:1::2) 2.445 ms 2.562 ms 2.231 ms
6 2001:1620:1000::bd (2001:1620:1000::bd) 2.396 ms 2.742 ms 2.609 ms
7 2001:1620:2::99 (2001:1620:2::99) 19.682 ms 19.672 ms 19.656 ms
8 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 19.638 ms 19.743 ms 19.681 ms
9 bbr01-p1-0.nwrk01.occaid.net (2001:4830:fe:1010::2) 102.591 ms 102.583 ms 102.634 ms
10 bbr01-t1-0.bstn01.occaid.net (2001:4830:ff:15c4::2) 109.385 ms 109.229 ms 109.334 ms
11 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 109.720 ms 109.414 ms 109.502 ms
12 cl-251.bos-01.us.sixxs.net (2001:4830:1100:fa::2) 128.093 ms 128.064 ms 128.034 ms
New Route Problem
Shadow Hawkins on Wednesday, 01 December 2010 17:30:46
Hi Jeroen,
Thank you for your test. The address you used was my tunnel endpoint address (2001:4830:1100:fa::2). That works for me too. Addresses in the R20645 subnet (2001:4830:114a::/48) such as 2001:4830:11a4:1::1 are not being routed to the tunnel endpoint.
$ ping6 2001:4830:11a4:1::1
PING6(56=40+8+8 bytes) 2001:4830:1100:f4::2 --> 2001:4830:11a4:1::1
^C
--- 2001:4830:11a4:1::1 ping6 statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
$ traceroute6 2001:4830:11a4:1::1
traceroute6 to 2001:4830:11a4:1::1 (2001:4830:11a4:1::1) from 2001:4830:1100:f4::2, 64 hops max, 12 byte packets
1 gw-245.bos-01.us.sixxs.net 16.117 ms !N 17.751 ms !N 18.998 ms !N
$
tcpdump shows no packets are being passed to me for ping6 2001:4830:11a4:1::1.
Thanks,
-Kurt
New Route Problem
Check again, I used 2001:4830:114a::, this is the subnet anycast address, thus the first host that is in that /64 will respond to it, which in your case is your tunnel endpoint.
Please also note that the 2001:4830:114a::/48 which is routed to you is not the 2001:4830:11a4::/48 you are mentioning now, note the mix up of the last part. 2001:4830:11a4::/48 is not assigned to you thus won't be routed to you either.
New Route Problem
Shadow Hawkins on Wednesday, 01 December 2010 23:15:14
Hi Jeroen,
You nailed it. I must have a bit of dyslexia and interchanged those digits. Sorry for the noise and thanks for the help.
-Kurt
New Route Problem
No worries, happens, I didn't notice it at first either ;)
State change: worksforme
The state of this ticket has been changed to worksforme
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 01 December 2010 13:58:39
Posting is only allowed when you are