As those of you who read the NZRR database notifications (or am I the only one?) will have noticed, we've updated filters with the intent to advertise the 6to4 prefix (192.88.99.0/24) on the APE shortly. This will put the closest 6to4 server for NZers on peering ISPs in Auckland, as opposed to Chicago (the current closest in all the tests I did, anyway). I'm sure many people will be interested in the level of traffic we receive, and the nature of that traffic, so I will be doing some analysis and will post details after it's been live a while. At this stage it looks like we will be announcing the prefix some time between now and Wednesday. Cheers, -- Jasper Bryant-Greene Network Engineer, Unleash p: +64 21 129 9458 e: jasper(a)unleash.co.nz w: http://www.unleash.co.nz/
On 1/09/2008, at 12:39 PM, Jasper Bryant-Greene wrote:
As those of you who read the NZRR database notifications (or am I the only one?) will have noticed, we've updated filters with the intent to advertise the 6to4 prefix (192.88.99.0/24) on the APE shortly.
This will put the closest 6to4 server for NZers on peering ISPs in Auckland, as opposed to Chicago (the current closest in all the tests I did, anyway).
I'm sure many people will be interested in the level of traffic we receive, and the nature of that traffic, so I will be doing some analysis and will post details after it's been live a while.
At this stage it looks like we will be announcing the prefix some time between now and Wednesday.
Note that this means that Jasper will be providing international and domestic v6 outbound transit for anyone who uses 6to4 and accepts 192.88.99.0/24. If you feel that you don't want that, you should either not accept the prefix from him (which will cause terrible performance for your 6to4 users, as they will go offshore), and/or set up your own 6to4 relay. Cheers, -- Nathan Ward
We are announcing the 6to4 prefix (192.88.99.0/24) on the APE as of early this afternoon. We're seeing about 15-25 Kbit/s of traffic, of which about 1/3 is exiting via one of our peering links rather than tunneling to the USA. I'll collect stats over the next while and post some pretty graphs etc at some stage. Cheers Jasper On Mon, 2008-09-01 at 12:39 +1200, Jasper Bryant-Greene wrote:
As those of you who read the NZRR database notifications (or am I the only one?) will have noticed, we've updated filters with the intent to advertise the 6to4 prefix (192.88.99.0/24) on the APE shortly.
This will put the closest 6to4 server for NZers on peering ISPs in Auckland, as opposed to Chicago (the current closest in all the tests I did, anyway).
I'm sure many people will be interested in the level of traffic we receive, and the nature of that traffic, so I will be doing some analysis and will post details after it's been live a while.
At this stage it looks like we will be announcing the prefix some time between now and Wednesday.
Cheers, -- Jasper Bryant-Greene Network Engineer, Unleash
p: +64 21 129 9458 e: jasper(a)unleash.co.nz w: http://www.unleash.co.nz/ INOC-DBA: 38477
Indeed. The graphs will be interesting, so looking forward to that.
Looking at
http://tr.meta.net.nz/datexplore.php/2008-09-03_10:19_192.88.99.1?format=png&openasthe
majority of ISPs are currently coming to your 6to4 anycast gateway.
That's a lot of ISPs entrusting their IPv6 traffic to someone off-net. That
surprises me, as it isn't particularly difficult to set up.
Cheers,
neil
2008/9/2 Jasper Bryant-Greene
We are announcing the 6to4 prefix (192.88.99.0/24) on the APE as of early this afternoon.
We're seeing about 15-25 Kbit/s of traffic, of which about 1/3 is exiting via one of our peering links rather than tunneling to the USA.
I'll collect stats over the next while and post some pretty graphs etc at some stage.
Cheers Jasper
On Mon, 2008-09-01 at 12:39 +1200, Jasper Bryant-Greene wrote:
As those of you who read the NZRR database notifications (or am I the only one?) will have noticed, we've updated filters with the intent to advertise the 6to4 prefix (192.88.99.0/24) on the APE shortly.
This will put the closest 6to4 server for NZers on peering ISPs in Auckland, as opposed to Chicago (the current closest in all the tests I did, anyway).
I'm sure many people will be interested in the level of traffic we receive, and the nature of that traffic, so I will be doing some analysis and will post details after it's been live a while.
At this stage it looks like we will be announcing the prefix some time between now and Wednesday.
Cheers, -- Jasper Bryant-Greene Network Engineer, Unleash
p: +64 21 129 9458 e: jasper(a)unleash.co.nz w: http://www.unleash.co.nz/
INOC-DBA: 38477
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
If us doing this prompted all the other ISPs to build 6to4 gateways for their customers, then I'd certainly be happy with that outcome! -jasper On Wed, 2008-09-03 at 10:30 +1200, Neil Fenemor wrote:
Indeed. The graphs will be interesting, so looking forward to that.
Looking at http://tr.meta.net.nz/datexplore.php/2008-09-03_10:19_192.88.99.1?format=png&openas the majority of ISPs are currently coming to your 6to4 anycast gateway.
That's a lot of ISPs entrusting their IPv6 traffic to someone off-net. That surprises me, as it isn't particularly difficult to set up.
Cheers,
neil
2008/9/2 Jasper Bryant-Greene
We are announcing the 6to4 prefix (192.88.99.0/24) on the APE as of early this afternoon. We're seeing about 15-25 Kbit/s of traffic, of which about 1/3 is exiting via one of our peering links rather than tunneling to the USA.
I'll collect stats over the next while and post some pretty graphs etc at some stage.
Cheers Jasper
On Mon, 2008-09-01 at 12:39 +1200, Jasper Bryant-Greene wrote: > As those of you who read the NZRR database notifications (or am I the > only one?) will have noticed, we've updated filters with the intent to > advertise the 6to4 prefix (192.88.99.0/24) on the APE shortly. > > This will put the closest 6to4 server for NZers on peering ISPs in > Auckland, as opposed to Chicago (the current closest in all the tests I > did, anyway). > > I'm sure many people will be interested in the level of traffic we > receive, and the nature of that traffic, so I will be doing some > analysis and will post details after it's been live a while. > > At this stage it looks like we will be announcing the prefix some time > between now and Wednesday. > > Cheers, -- Jasper Bryant-Greene Network Engineer, Unleash
p: +64 21 129 9458 e: jasper(a)unleash.co.nz w: http://www.unleash.co.nz/
INOC-DBA: 38477
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
-- Jasper Bryant-Greene Network Engineer, Unleash p: +64 21 129 9458 e: jasper(a)unleash.co.nz w: http://www.unleash.co.nz/ INOC-DBA: 38477
On Wed, 2008-09-03 at 10:30 +1200, Neil Fenemor wrote:
Indeed. The graphs will be interesting, so looking forward to that.
Looking at http://tr.meta.net.nz/datexplore.php/2008-09-03_10:19_192.88.99.1?format=png&openas the majority of ISPs are currently coming to your 6to4 anycast gateway.
That's a lot of ISPs entrusting their IPv6 traffic to someone off-net. That surprises me, as it isn't particularly difficult to set up.
When you get onto the '6 you should be able to see http://www.ipv6porn.co.nz (it IS Work safe). (why else would you get on v6) Thanks Craig
I think someone should post a how-to for connecting medium size businesses to the ipv6 anycast network.. :) Perhaps some quick documentation on how to do the 6-to-4 nat for an entire /24 ? -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Wednesday, 3 September 2008 1:35 p.m. To: Neil Fenemor Cc: nznog Subject: Re: [nznog] 6to4 on the APE On Wed, 2008-09-03 at 10:30 +1200, Neil Fenemor wrote:
Indeed. The graphs will be interesting, so looking forward to that.
Looking at http://tr.meta.net.nz/datexplore.php/2008-09-03_10:19_192.88.99.1?format=png &openas the majority of ISPs are currently coming to your 6to4 anycast gateway.
That's a lot of ISPs entrusting their IPv6 traffic to someone off-net. That surprises me, as it isn't particularly difficult to set up.
When you get onto the '6 you should be able to see http://www.ipv6porn.co.nz (it IS Work safe). (why else would you get on v6) Thanks Craig _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On 3/09/2008, at 2:56 PM, Craig Spiers wrote:
I think someone should post a how-to for connecting medium size businesses to the ipv6 anycast network.. :)
Perhaps some quick documentation on how to do the 6-to-4 nat for an entire /24 ?
Sure, I'll re-work some of my slides and post. Note that 'entire /24' isn't really relevant with 6to4 - a single IPv4 address = IPv6 /48 = 65,536 IPv6 /64 networks. So, background, 6to4 runs on a border router, and lets a native IPv6 network (numbered out of a 6to4 prefix) connect to the IPv6 Internet. Note that it requires IPv6 support from your internal devices - if you have any routers or whatever in your 'medium size' business network then they will require IPv6 support. Alternative to native support inside a network is to run ISATAP, which is a protocol targeted at enterprises which runs automatic IPv6 over IPv4 tunnels to your border router - that border router can run 6to4, or have native connectivity. I'll write up some scenarios, I've got some time to kill on a flight tomorrow. -- Nathan Ward
Excellent - cheers -----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Wednesday, 3 September 2008 3:04 p.m. To: nznog Subject: Re: [nznog] 6to4 on the APE On 3/09/2008, at 2:56 PM, Craig Spiers wrote:
I think someone should post a how-to for connecting medium size businesses to the ipv6 anycast network.. :)
Perhaps some quick documentation on how to do the 6-to-4 nat for an entire /24 ?
Sure, I'll re-work some of my slides and post. Note that 'entire /24' isn't really relevant with 6to4 - a single IPv4 address = IPv6 /48 = 65,536 IPv6 /64 networks. So, background, 6to4 runs on a border router, and lets a native IPv6 network (numbered out of a 6to4 prefix) connect to the IPv6 Internet. Note that it requires IPv6 support from your internal devices - if you have any routers or whatever in your 'medium size' business network then they will require IPv6 support. Alternative to native support inside a network is to run ISATAP, which is a protocol targeted at enterprises which runs automatic IPv6 over IPv4 tunnels to your border router - that border router can run 6to4, or have native connectivity. I'll write up some scenarios, I've got some time to kill on a flight tomorrow. -- Nathan Ward _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On Wed, 2008-09-03 at 14:56 +1200, Craig Spiers wrote:
I think someone should post a how-to for connecting medium size businesses to the ipv6 anycast network.. :)
Perhaps some quick documentation on how to do the 6-to-4 nat for an entire /24 ?
See: www.v6.co.nz. people can update it .. There is an example of cisco config @ http://www.v6.co.nz/doku.php/cisco which is a short version of : http://www.ifm.net.nz/cookbooks/ipv6configwizard.html Thanks Craig
participants (5)
-
Craig Spiers
-
Craig Whitmore
-
Jasper Bryant-Greene
-
Nathan Ward
-
Neil Fenemor