Yeah, UoA prefer KAREN routes over Internet routes. For some reason, people are advertising public IPv6 routes in to internet2 (or some connected research network). They really shouldn't, it would make the public IPv6 network work a whole lot better for early adopters like research networks. On 18/09/2009, at 12:43 PM, Brian E Carpenter wrote:
It appears to go out of here native through KAREN, which makes the Seattle hop plausible.
Brian
On 2009-09-18 12:21, McDonald Richards wrote:
Out of curiosity is that through a tunnel broker of some sort? The lack of reverse dns on the path is making it difficult to tell ;)
Macca
-----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Brian E Carpenter Sent: Friday, 18 September 2009 10:16 AM To: Blair Harrison Cc: nznog(a)list.waikato.ac.nz; Alan Maher Subject: [nznog] fx.net.nz [Re: NZNOG Digest, Vol 81, Issue 12]
Yes, the IPv6 path across town is a bit comnvoluted and seems to involve Seattle.
tracert www.fx.net.nz
Tracing route to www.fx.net.nz [2402:6000:200:100::4] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2001:df0:0:2006::254 2 <1 ms <1 ms <1 ms 2001:df0:0:201f::1022:400 3 1 ms <1 ms <1 ms 2001:df0:0:1::14:400 4 1 ms <1 ms <1 ms 2001:df0:0:1::7:be 5 1 ms <1 ms <1 ms 2001:df0:0:1::3:b2 6 1 ms <1 ms <1 ms 2001:df0:0:1::3:b1 7 12 ms 11 ms 13 ms 2404:138:0:1::2 8 11 ms 11 ms 11 ms 2404:138:0:4:214:f601:2d88:dc7e 9 159 ms 153 ms 153 ms 2404:138:2000::a 10 153 ms 153 ms 153 ms kreonet-1-lo-jmb-706.sttlwa.pacificwave.net [2001:504:b:10::6] 11 268 ms 267 ms 267 ms 2001:320:1b00:1::1 12 348 ms 348 ms 348 ms hurricaneelectric-RGE.hkix.net [2001:7fa:0:1::ca28:a19e] 13 348 ms 348 ms 348 ms gige-g0-1.tserv19.hkg1.ipv6.he.net [2001:470:0:b8::2] 14 546 ms 474 ms 474 ms fxnetworks-3-pt.tunnel.tserv19.hkg1.ipv6.he.net [2001:470:17:86::2] 15 * 474 ms 735 ms as9503.akl01.akl.VOCUS.net.au [2402:7800:110:501::3] 16 746 ms 482 ms 482 ms palmy-fw1.ip6.fx.net.nz [2402:6000:f000::100] 17 487 ms 568 ms 482 ms palmy-web1.fx.net.nz [2402:6000:200:100::4]
Trace complete.
Brian
On 2009-09-17 22:05, Blair Harrison wrote:
Hi Alan,
Do you have ipv6 enabled on your computer?
www.fx.net.nz is ipv6 enabled, and I suspect if the website is loading slowly it may have to do with faulty v6 transit. (ie, if you are accessing it over a tunnel going via the US or EU)
You could try www2.fx.net.nz which will go to the same place, but does not have a v6 DNS record.
We haven't had any DoS attacks this evening that I'm aware of.
Regards, Blair Harrison FX Networks
On Thu, Sep 17, 2009 at 7:45 PM, Alan Maher
wrote: My apologies for this (my first) post. As a former Sys Admin, I retain an interest in this area for purely personal & academic reasons. After observing the post, I attempted to access http://www.fx.net.nz/ and it timed out. And is doing so again this evening. Your thoughts? All else is functioning fine. ( I run PClos linux on my desktop & use Open DNS) Alan Maher
------------------------------------------------------------------------
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
!DSPAM:22,4ab2d7b426431827514789!