can anyone trace/ping 2001:67c:174:101::5?
The HE route-server can't seem to, just wondering if its temporary or if HE is partitioned from AS 48345 usually.
Its reader.ipv6.xsnews.nl. HE is announcing it as a /48 to me however the traceroute dies. I filtered out that prefix from HE and I can reach it over alternate v6 links.
Unreachable for me as well.
Unreachable for me as well. Seems like I get inconsistent ICMP responses when trying to ping.
C:\Users\antillie>ping 2001:67c:174:101::5
Pinging 2001:67c:174:101::5 with 32 bytes of data:
Request timed out.
Destination net unreachable.
Destination net unreachable.
Request timed out.
Ping statistics for 2001:67c:174:101::5:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\antillie>tracert 2001:67c:174:101::5
Tracing route to 2001:67c:174:101::5 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router.local.lan [2001:470:b98a:1:20e:d7ff:fe0b:21e0]
2 67 ms 67 ms 67 ms antillie-1.tunnel.tserv8.dal1.ipv6.he.net [2001:470:1f0e:6ca::1]
3 69 ms 71 ms 74 ms gige-g2-14.core1.dal1.he.net [2001:470:0:78::1]
4 86 ms 86 ms 91 ms 10gigabitethernet5-4.core1.atl1.he.net [2001:470:0:1b6::2]
5 98 ms 97 ms 97 ms 10gigabitethernet6-4.core1.ash1.he.net [2001:470:0:1b5::1]
6 105 ms 114 ms 104 ms 10gigabitethernet1-2.core1.nyc4.he.net [2001:470:0:36::2]
7 178 ms 174 ms 173 ms 10gigabitethernet1-2.core1.lon1.he.net [2001:470:0:3e::2]
8 Destination net unreachable.
Trace complete.
Hrm. Traced with Comcast 6RD, and it works. U should probably send email to ipv6@he.net.
{jimb@T510jimb/tty1}~> tracert 2001:67c:174:101::5
Tracing route to 2001:67c:174:101::5 over a maximum of 30 hops
1 3 ms 3 ms 1 ms 2001:db8:1234:5678:1::1
2 68 ms 97 ms 95 ms 2001:55c:45fc:5042::1
3 86 ms 66 ms 85 ms 2001:558:d0:1e::1
4 69 ms 69 ms 66 ms 2001:558:d0:b::1
5 68 ms 64 ms 66 ms 2001:558:d0:1::1
6 102 ms 82 ms 71 ms 2001:558:0:f6c5::1
7 100 ms 82 ms 95 ms pos-0-3-0-0-cr01.santateresa.tx.ibone.comcast.net [2001:558:0:f5ab::2]
8 100 ms 98 ms 115 ms pos-0-4-0-0-cr01.losangeles.ca.ibone.comcast.net [2001:558:0:f584::1]
9 110 ms 98 ms 105 ms 2001:450:2002:7d::1
10 241 ms 283 ms 241 ms 2001:450:2002:ee::2
11 236 ms 265 ms 235 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580:1::3302:2]
12 239 ms 236 ms 236 ms 20ge-r1.as48345.net [2001:67c:174::1:1]
13 234 ms 255 ms 232 ms 2001:67c:174:101::5
Trace complete.
telnet 2001:67c:174:101::5 119
201 reader.ipv6.xsnews.nl NNRP Service Ready (no posting).
quit
205 Transferred 60 bytes in 0 articles, 0 groups. Disconnecting.
Connection to host lost.
Quote from: jimb on February 22, 2011, 11:01:39 PM
Hrm. Traced with Comcast 6RD, and it works. U should probably send email to ipv6@he.net.
I guess I will. Hopefully not seen as a complaint since I am after all getting this connectivity for free :)
Yeah I'm noticing the same thing with my he.net tunnel:
R1#ping 2001:67c:174:101::5 repeat 3
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:67C:174:101::5, timeout is 2 seconds:
U..
Success rate is 0 percent (0/3)
R1#
My other tunnel (gogonet) is able to reach it.
[mierdin@COSBOX~]# ping6 2001:67c:174:101::5
PING 2001:67c:174:101::5(2001:67c:174:101::5) 56 data bytes
64 bytes from 2001:67c:174:101::5: icmp_seq=0 ttl=53 time=442 ms
64 bytes from 2001:67c:174:101::5: icmp_seq=1 ttl=53 time=476 ms
64 bytes from 2001:67c:174:101::5: icmp_seq=2 ttl=53 time=477 ms
--- 2001:67c:174:101::5 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 442.898/465.672/477.641/16.120 ms, pipe 2
I'm wondering what could be causing this - how could a HE.NET tunnel not be reachable by another HE.NET tunnel, but is reachable via other services?
Quote from: Mierdin on February 23, 2011, 07:34:27 AM
Yeah I'm noticing the same thing with my he.net tunnel:
...
I'm wondering what could be causing this - how could a HE.NET tunnel not be reachable by another HE.NET tunnel, but is reachable via other services?
er.......
inet6num: 2001:67c:174::/48
netname: NL-XSNEWS-AMS
descr: XS News BV
country: NL
org: ORG-XN2-RIPE
admin-c: ATAR-RIPE
tech-c: ATTR-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-by: ATRATO-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-routes: ATRATO-MNT
mnt-domains: ATRATO-MNT
source: RIPE # Filtered
aren't you pining away every day doing whois's etc to increase your sage score? :D this netblock is not HEs, and is not a tunnel.
Probably a broken peering somewhere, the v6-backbone is sufferring from reachability issues like any growing network.
anyway it looks fixed now.
Heh - jimb had advised you email He.net and I assumed it was a henet tunnel.
In this case, assuming makes an ass out of just me. ;D