|
Ticket ID: SIXXS #8635922 Ticket Status: Remote Problem PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
No connectivity to Cogent IPv6 network
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 17 January 2013 13:10:03
The connectivity between USQAS01 (2001:4830:1600:432::2) and (2001:550:2:b7::1) is broken. I have no problem to reach both addresses from other networks, but they are not reachable from each other:
[1]# ifconfig sixxs
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:4830:1600:432::2/64 Scope:Global
[1]# ping6 2001:550:2:b7::1
PING 2001:550:2:b7::1(2001:550:2:b7::1) 56 data bytes
--- 2001:550:2:b7::1 ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25078ms
[1]# traceroute6 2001:550:2:b7::1
traceroute to 2001:550:2:b7::1 (2001:550:2:b7::1), 30 hops max, 80 byte packets
1 gw-1075.qas-01.us.sixxs.net (2001:4830:1600:432::1) 11.511 ms 11.734 ms 11.689 ms
2 2001:4830:e6:7:250:56ff:fe80:1519 (2001:4830:e6:7:250:56ff:fe80:1519) 11.639 ms 11.587 ms 11.531 ms
3 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 11.470 ms 11.884 ms 11.847 ms
4 iad0-b0-ge0.hotnic.net (2001:4810::1:4:1) 12.739 ms 12.662 ms 12.578 ms
5 carpathia-gw.hotnic.net (2001:4810::1:4:2) 13.933 ms 16.363 ms 16.315 ms
6 2001:4838:0:1::1e:1 (2001:4838:0:1::1e:1) 15.892 ms 11.129 ms 10.892 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
[2]# ifconfig sixxs
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:4830:1600:438::2/64 Scope:Global
[2]# ping6 2001:550:2:b7::1
PING 2001:550:2:b7::1(2001:550:2:b7::1) 56 data bytes
--- 2001:550:2:b7::1 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 16392ms
[2] traceroute6 -n 2001:550:2:b7::1
traceroute to 2001:550:2:b7::1 (2001:550:2:b7::1), 30 hops max, 80 byte packets
1 2001:4830:1600:438::1 3.222 ms 3.231 ms 3.220 ms
2 2001:4830:e6:7:250:56ff:fe80:1519 3.545 ms 3.536 ms 3.532 ms
3 2001:4830:e6:7::1 4.036 ms 4.101 ms 4.093 ms
4 2001:4810::1:4:1 5.896 ms 5.887 ms 5.892 ms
5 2001:4810::1:4:2 6.997 ms 6.985 ms 7.290 ms
6 2001:4838:0:1::1e:1 6.018 ms 4.650 ms 4.585 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
No connectivity to Cogent IPv6 network
The only thing I can state here is that it is a known fact that Cogent has strange peering/interconnect policies, which is what this might be causing, as such tagging it as a remote problem.
Note that the path outbound works (packets just stop being returned), thus maybe it is the inbound path that is giving problems. A traceroute from the remote network would be useful.
I've informed OCCAID of this, maybe they can resolve this, but likely that might not be the case.
No connectivity to Cogent IPv6 network
Shadow Hawkins on Thursday, 17 January 2013 15:22:51
[1] # ping6 www.sixxs.net
PING www.sixxs.net(tunnelserver.concepts-ict.net) 56 data bytes
64 bytes from tunnelserver.concepts-ict.net: icmp_seq=1 ttl=52 time=88.8 ms
64 bytes from tunnelserver.concepts-ict.net: icmp_seq=2 ttl=52 time=88.8 ms
64 bytes from tunnelserver.concepts-ict.net: icmp_seq=3 ttl=52 time=89.0 ms
--- www.sixxs.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2306ms
rtt min/avg/max/mdev = 88.877/88.936/89.053/0.354 ms
[1] # ping6 2001:4830:1600:432::2
PING 2001:4830:1600:432::2(2001:4830:1600:432::2) 56 data bytes
From 2001:550:2:b7::1 icmp_seq=1 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=2 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=3 Destination unreachable: No route
--- 2001:4830:1600:432::2 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2307ms
[1] # traceroute6 -n 2001:4830:1600:432::2
traceroute to 2001:4830:1600:432::2 (2001:4830:1600:432::2), 30 hops max, 80 byte packets
1 2001:550:2:b7::1 0.485 ms !N 0.492 ms !N 0.493 ms !N
[2] ping6 2001:4830:1600:438::2
PING 2001:4830:1600:438::2(2001:4830:1600:438::2) 56 data bytes
From 2001:550:2:b7::1 icmp_seq=1 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=2 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=3 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=4 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=5 Destination unreachable: No route
From 2001:550:2:b7::1 icmp_seq=6 Destination unreachable: No route
--- 2001:4830:1600:438::2 ping statistics ---
25 packets transmitted, 0 received, +25 errors, 100% packet loss, time 24598ms
[2] traceroute6 -n 2001:4830:1600:438::2
traceroute to 2001:4830:1600:438::2 (2001:4830:1600:438::2), 30 hops max, 80 byte packets
1 2001:550:2:b7::1 0.492 ms !N 0.489 ms !N 0.517 ms !N
Same time the ping to Sixxs and other your POPs are going fine:
# ping6 2607:f878:ff00:5::1
PING 2607:f878:ff00:5::1(2607:f878:ff00:5::1) 56 data bytes
64 bytes from 2607:f878:ff00:5::1: icmp_seq=1 ttl=54 time=49.5 ms
64 bytes from 2607:f878:ff00:5::1: icmp_seq=2 ttl=54 time=49.6 ms
64 bytes from 2607:f878:ff00:5::1: icmp_seq=3 ttl=54 time=49.5 ms
--- 2607:f878:ff00:5::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2513ms
rtt min/avg/max/mdev = 49.577/49.589/49.603/0.257 ms
No connectivity to Cogent IPv6 network
[1] # ping6 2001:4830:1600:432::2 PING 2001:4830:1600:432::2(2001:4830:1600:432::2) 56 data bytes From 2001:550:2:b7::1 icmp_seq=1 Destination unreachable: No route
What is the source address of this ping?
Obviously Cogent (2001:550:2:b7::1) does not know where to route those packets and that would thus completely explain the failing traceroute.
[1] # traceroute6 -n 2001:4830:1600:432::2 traceroute to 2001:4830:1600:432::2 (2001:4830:1600:432::2), 30 hops max, 80 byte packets 1 2001:550:2:b7::1 0.485 ms !N 0.492 ms !N 0.493 ms !N
Looks like that Cogent hop is your first hop, if you are a Cogent customer you really should complain to them to get their peering in order.
Same time the ping to Sixxs and other your POPs are going fine:
Just means that they are missing at least one route. Not odd as they are apparently in dispute with several networks, not peering with or buying from them.
As you seem to be a customer, you should complain to them for not being reachable.
No connectivity to Cogent IPv6 network
Shadow Hawkins on Thursday, 17 January 2013 16:23:19
The source is 2001:550:2:b7::4/112
I am opening the ticket with them too.
No connectivity to Cogent IPv6 network
Shadow Hawkins on Thursday, 17 January 2013 17:25:44
Silly, but this is an answer from Cogent:
When I trace to that IP from a public routeviews server I see that Hurricane Electric is in the path. Hurricane Electric is not a customer of Cogent's and do not have any transit into the Cogent network.
No connectivity to Cogent IPv6 network
Is it normal behavior ?
For Cogent, apparently yes, if you google a bit you will find a lot about their peering spats with other providers.
For instance it is documented on Wikipedia :: Comparison of IPv6 support by major transit providers
Or should I work with them harder to make this resolved somehow?
As you are (paying) customer of them, you definitely should as you are not reachable for quite a bit of the IPv6 Internet.
As sounds like HE customers on IPv6 will unable to reach us on Cogent, which is really dangerous....
Not dangerous, but indeed anything coming through Hurricane Electric, who transit for quite a few folks, where those ASNs are not getting transit through other paths to Cogent are effectively unreachable.
There is very little we can do about this though as Cogent is the problem here (well, actually there are always multiple parties involved in not wanting to pay/connect to others, but Cogent is doing their utmost best to be not so nice here; then again they claim to have offered payed access, which makes sense in the world and happens all the time... it is the Internet and business is business)
No connectivity to Cogent IPv6 network
Shadow Hawkins on Thursday, 17 January 2013 17:41:28
Thank you.
At any extend, I am going to work with them and will not let them close the tickets as long as I can..... this is only my investment to the "6" community.
But I still need to have 2 tunnels are operational for full testing, so I may peer with 2 another your PoPs, one for dynamic access and one for static, so the test goes in full..... but to be a little greedy - can I can refund/credit for removing 1 tunnel (current static one) and establish another 1-2 with different PoP?
No connectivity to Cogent IPv6 network
so I may peer with 2 another your PoPs
Please see our FAQ, we do not provide peering (except for GRH).
but to be a little greedy - can I can refund/credit for removing 1 tunnel (current static one) and establish another 1-2 with different PoP?
Please see the FAQ on credits, they need to be earned.
No connectivity to Cogent IPv6 network
Shadow Hawkins on Friday, 18 January 2013 03:44:31Please see the FAQ on credits, they need to be earned. I agree to earn, but this is not my problem to face issues with connectivity between HE and Cogent, so want to check if this is possible to get at least one tunnel removed and re-established with a different PoP, without losing currently earned credits.
Thanks
No connectivity to Cogent IPv6 network
Shadow Hawkins on Friday, 18 January 2013 03:57:03
As per my calculations, it will not be even enough for me to cover this move for both tunnels:
Removing a reverse DNS server - 1 ISK x 3 NS x 2 zones
Deletion of a tunnel - 25 ISK x 2 tunnels
Requesting a tunnel - 10 ISK x 2 tunnels
Approving a tunnel request - 5 ISK x 2 tunnels
Adding a reverse DNS server - 1 ISK x 3 NS x 2 zones
total: 89 ISK
|
![[ch]](/s/countries/ch.gif)
on Thursday, 17 January 2013 13:15:13
Posting is only allowed when you are