Re: [m0n0wall] how do we check, that ipv6 is actually working (OT again)

From:	Steve Bertrand <steve at ibctech dot ca>
To:	Michel Servaes <michel at mcmc dot be>
Cc:	"m0n0wall at lists dot m0n0 dot ch >> M0n0wall Mailing List" <m0n0wall at lists dot m0n0 dot ch>
Subject:	Re: [m0n0wall] how do we check, that ipv6 is actually working (OT again)
Date:	Tue, 14 Apr 2009 15:00:17 -0400

Michel Servaes wrote:
> Steve,
> 
> I have added ipv6.mcmc.be as an AAAA record.

That works:

%dig aaaa ipv6.mcmc.be

;; QUESTION SECTION:
;ipv6.mcmc.be.                  IN      AAAA

;; ANSWER SECTION:
ipv6.mcmc.be.           14400   IN      AAAA
2001:470:1f15:158c:d7d:bd6:5ff3:6988

> This only goes to my Vista machine, and should only show you the IIS7
> index page...

Can't get to it via web, trace tells me this:

%traceroute6 ipv6.mcmc.be

traceroute6 to ipv6.mcmc.be (2001:470:1f15:158c:d7d:bd6:5ff3:6988) from
2607:f118::b6, 64 hops max, 12 byte packets

 1  v6-pe3.eagle.ca  0.279 ms  0.270 ms  0.218 ms
 2  2607:f118:1:3:20f:b5ff:fe43:134d  0.430 ms  0.530 ms  0.352 ms
 3  2610:38:1::11  6.094 ms  9.267 ms  4.955 ms
 4  2001:478:245:1::112  30.972 ms  31.199 ms  30.422 ms
 5  10gigabitethernet1-2.core1.nyc5.he.net  29.966 ms  30.437 ms  30.957 ms
 6  10gigabitethernet1-4.core1.nyc1.he.net  30.959 ms  30.497 ms  30.965 ms
 7  10gigabitethernet1-1.core1.nyc4.he.net  30.445 ms  30.462 ms  29.959 ms
 8  10gigabitethernet1-2.core1.lon1.he.net  99.421 ms  100.068 ms  99.418 ms
 9  10gigabitethernet1-1.core1.ams1.he.net  106.933 ms  107.851 ms
108.433 ms
10  1g-bge0.tserv11.ams1.ipv6.he.net  109.876 ms  110.419 ms  110.920 ms
11  * * *
12  *^C

...nor can I ping the IP.

What is the IPv6 address of your tunnel endpoint?

Steve