I am currently sage certified but I dont have a vm or pc for ping or tracert, all I have is my cisco router doing the tunnel back, so my question is why cant we use that for ping and traceroute? I know it works but need another machine but dont have the time to build one and use it. Here is an example of a tracert
IPV6_Tun.Eacompsolutions.net#$ipv6 2A02:920:212E:1::213
Type escape sequence to abort.
Tracing the route to ipv6friday.org (2A02:920:212E:1::213)
1 a9a1c1-1.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1F06:D85::1) 12 msec 12 msec 12 msec
2 ve422.core1.nyc4.he.net (2001:470:0:5D::1) 12 msec 12 msec 8 msec
3 100ge7-2.core1.lon2.he.net (2001:470:0:2CF::1) 96 msec 76 msec 76 msec
4 100ge6-2.core1.ams1.he.net (2001:470:0:2D0::2) 88 msec 88 msec 88 msec
5 10ge1-5.core1.sto1.he.net (2001:470:0:22F::2) 108 msec 116 msec 108 msec
6 2001:7F8:D:FE::247 108 msec 104 msec 104 msec
7 htgr01-107.gotanet.se (2A02:920:1FFF:6B::113) 112 msec 104 msec 104 msec
8 ipv6friday.org (2A02:920:212E:1::213) 112 msec 108 msec 104 msec
not accepted any ideas on what else to do?
The parser is somewhat simplistic at times. You might try changing:
Quote from: a9a1c1 on March 08, 2017, 01:04:06 PM
6 2001:7F8:D:FE::247 108 msec 104 msec 104 msec
to
6 2001:7F8:D:FE::247 (2001:7F8:D:FE::247) 108 msec 104 msec 104 msec
I can definitely tell you that if an entry uses the alternate IPv4 derived address formatting, it is rejected. I.e. if that address were written 2001:7F8:D:FE::0.0.2.71 it would definitely be rejected, even though it is perfectly valid and equivalent.
In any case, I'll try targetting that address tomorrow. (I've already done my points for today. :-) )
--David G
Quote from: divad27182 on March 08, 2017, 01:54:31 PM
In any case, I'll try targetting that address tomorrow. (I've already done my points for today. :-) )
Well, I tried it, and I removed the duplicate address I was suggesting, and it worked. The other major differences were:
- my addresses were in lower case
- I had one more hop before reaching ve422.core1.nyc4.he.net
- My traceroute doesn't assume the target's address gets the target's name, so the last line was:
Quote9 juniper.webway.se (2a02:920:212e:1::213) 131.990 ms 132.554 ms 126.184 ms
Frankly, I would not have thought any of these would cause problems, but it gives me more things to test. ;)
--David
Edit: correct list formatting
Edit: Upper case didn't make it fail. Nor did lack of hostnames.
Edit: It appears that the line before the first trace line is important. It appears that it having a hostname they can resolve is not.