Tui update - please accept my routes and give me free transit. No really. Please?
Hello all, A few weeks back we were loaned 2 x /24s[1] and 2 x ASNs by APNIC R&D, big thanks to Geoff Huston. One ASN and /24 lives on the Tui route- server at APE, and the others on the Tui route-server at WIX. They are: - APE: AS24021 203.147.108.0/24 - WIX: AS45163 203.147.109.0/24 These /24s are used for the unit's 6to4 address, which is used for 2 things: - BGP peer address for remote Tui boxes. - Next hop for v6 routes from native exchange peers. These routes are only given to remote Tui boxes that are on networks that are visible from APE/WIX. The first Tui route-server has been installed by Andy on WIX today, we're looking to get the APE one in next week. If you are on WIX, can you please accept 203.147.109.0/24 from the WIX v4 route-servers. If you prefer private peering on the exchange we can do that too, drop me an email - nward(a)braintrust.co.nz. Same for the APE /24 next week. Now, that gets these two /24s visible to networks that are visible at APE/WIX, however that doesn't get us to networks that aren't. If you can see these two /24s, please transit them - ie. advertise them to your peers and transit providers. That let's networks that don't peer (for whatever reason) still use Tui boxes in their networks. If you transit these /24s, the only data you'll see going across your network to/from these networks is BGP traffic in 6to4. You won't see any actual data, just BGP control messages. The routing policy only gives next hops in these /24s if the remote Tui box is in a network visible to the exchange (in which case you won't transit packets for that network) - if it's not, it only gets information about other Tui boxes, and that data goes direct between Tui boxes. I've been trying to figure out how to explain this clearly in words.. hopefully that makes sense. I'll follow up with a picture if needed. In short - please accept and re-advertise those two /24s to your peers, customers, and internationally to help out this Tui project, they are very low traffic and only carry control data, I promise. We're talking kilobits per second here, so it's really nothing. Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you. Big thanks go to InternetNZ for hardware and support, APNIC for v4 and ASNs, and Citylink for exchange connectivity, hardware, etc. -- Nathan Ward Braintrust Ltd. nward(a)braintrust.co.nz +64-21-431675 [1] - No, the irony of burning 2 /24s to help encourage v6 adoption is not lost on me :-)
On 2/05/2008, at 4:47 PM, Nathan Ward wrote:
Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you.
It occurs to me that I'd need a default from you for this to be worthwhile, so, please let me know if you're keen so we can bring up a private session. Thanks all, -- Nathan Ward
Even though we are all awesome and as smart as you(!), please provide a picture for those of us who have had too many Friday night drinks! J
-----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Friday, 2 May 2008 4:48 PM To: nznog Subject: [nznog] Tui update - please accept my routes and give me freetransit. No really. Please?
Hello all,
A few weeks back we were loaned 2 x /24s[1] and 2 x ASNs by APNIC R&D, big thanks to Geoff Huston. One ASN and /24 lives on the Tui route- server at APE, and the others on the Tui route-server at WIX. They are: - APE: AS24021 203.147.108.0/24 - WIX: AS45163 203.147.109.0/24
These /24s are used for the unit's 6to4 address, which is used for 2 things: - BGP peer address for remote Tui boxes. - Next hop for v6 routes from native exchange peers. These routes are only given to remote Tui boxes that are on networks that are visible from APE/WIX.
The first Tui route-server has been installed by Andy on WIX today, we're looking to get the APE one in next week.
If you are on WIX, can you please accept 203.147.109.0/24 from the WIX v4 route-servers. If you prefer private peering on the exchange we can do that too, drop me an email - nward(a)braintrust.co.nz.
Same for the APE /24 next week.
Now, that gets these two /24s visible to networks that are visible at APE/WIX, however that doesn't get us to networks that aren't. If you can see these two /24s, please transit them - ie. advertise them to your peers and transit providers. That let's networks that don't peer (for whatever reason) still use Tui boxes in their networks. If you transit these /24s, the only data you'll see going across your network to/from these networks is BGP traffic in 6to4. You won't see any actual data, just BGP control messages. The routing policy only gives next hops in these /24s if the remote Tui box is in a network visible to the exchange (in which case you won't transit packets for that network) - if it's not, it only gets information about other Tui boxes, and that data goes direct between Tui boxes. I've been trying to figure out how to explain this clearly in words.. hopefully that makes sense. I'll follow up with a picture if needed.
In short - please accept and re-advertise those two /24s to your peers, customers, and internationally to help out this Tui project, they are very low traffic and only carry control data, I promise. We're talking kilobits per second here, so it's really nothing.
Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you.
Big thanks go to InternetNZ for hardware and support, APNIC for v4 and ASNs, and Citylink for exchange connectivity, hardware, etc.
-- Nathan Ward Braintrust Ltd. nward(a)braintrust.co.nz +64-21-431675
[1] - No, the irony of burning 2 /24s to help encourage v6 adoption is not lost on me :-) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Any luck with that TUI VMWare Image? ________________________________ From: WOOLLEY JONATHAN [mailto:Jonathan.Woolley(a)alcatel-lucent.co.nz] Sent: Fri 2/05/2008 10:23 p.m. To: Nathan Ward; nznog Subject: Re: [nznog] Tui update - please accept my routes and give mefreetransit. No really. Please? Even though we are all awesome and as smart as you(!), please provide a picture for those of us who have had too many Friday night drinks! J
-----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Friday, 2 May 2008 4:48 PM To: nznog Subject: [nznog] Tui update - please accept my routes and give me freetransit. No really. Please?
Hello all,
A few weeks back we were loaned 2 x /24s[1] and 2 x ASNs by APNIC R&D, big thanks to Geoff Huston. One ASN and /24 lives on the Tui route- server at APE, and the others on the Tui route-server at WIX. They are: - APE: AS24021 203.147.108.0/24 - WIX: AS45163 203.147.109.0/24
These /24s are used for the unit's 6to4 address, which is used for 2 things: - BGP peer address for remote Tui boxes. - Next hop for v6 routes from native exchange peers. These routes are only given to remote Tui boxes that are on networks that are visible from APE/WIX.
The first Tui route-server has been installed by Andy on WIX today, we're looking to get the APE one in next week.
If you are on WIX, can you please accept 203.147.109.0/24 from the WIX v4 route-servers. If you prefer private peering on the exchange we can do that too, drop me an email - nward(a)braintrust.co.nz.
Same for the APE /24 next week.
Now, that gets these two /24s visible to networks that are visible at APE/WIX, however that doesn't get us to networks that aren't. If you can see these two /24s, please transit them - ie. advertise them to your peers and transit providers. That let's networks that don't peer (for whatever reason) still use Tui boxes in their networks. If you transit these /24s, the only data you'll see going across your network to/from these networks is BGP traffic in 6to4. You won't see any actual data, just BGP control messages. The routing policy only gives next hops in these /24s if the remote Tui box is in a network visible to the exchange (in which case you won't transit packets for that network) - if it's not, it only gets information about other Tui boxes, and that data goes direct between Tui boxes. I've been trying to figure out how to explain this clearly in words.. hopefully that makes sense. I'll follow up with a picture if needed.
In short - please accept and re-advertise those two /24s to your peers, customers, and internationally to help out this Tui project, they are very low traffic and only carry control data, I promise. We're talking kilobits per second here, so it's really nothing.
Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you.
Big thanks go to InternetNZ for hardware and support, APNIC for v4 and ASNs, and Citylink for exchange connectivity, hardware, etc.
-- Nathan Ward Braintrust Ltd. nward(a)braintrust.co.nz +64-21-431675
[1] - No, the irony of burning 2 /24s to help encourage v6 adoption is not lost on me :-) _______________________________________________ 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 No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.7/1410 - Release Date: 1/05/2008 5:30 p.m.
On 2/05/2008, at 10:23 PM, WOOLLEY JONATHAN wrote:
Even though we are all awesome and as smart as you(!), please provide a picture for those of us who have had too many Friday night drinks!
You should have come to NZNOG'08 :-) So, Tui started out as building 6to4 and Teredo relays to give to ISPs. Scope creep and cool ideas happened, and it's now about that, AND building a full mesh of automatic v6 tunnels between ISPs with Tui, and the APE/WIX native v6 peers. Here is a summary I copied and pasted from another email: Basically, we drop route servers in to IXes, and Tui nodes in to ISPs or enterprise networks. - The Tui boxes are 6to4 and Teredo relays. - They also build a full mesh of all Tui nodes, using 6to4 as the transport mechanism (because it's efficient, and it doesn't require static tunnels - you just set the nexthop to be 2002:aabb:ccdd:: where aa.bb.cc.dd is the v4 address of the remote Tui node). ISPs advertise their v6 prefixes in to their local Tui node, which re-advertises them to other Tui nodes. - As well as a full mesh of Tui nodes, anyone who has free (from the POV of the exchange) transit to the exchange, can send traffic to/from exchange v6 peers via the route-server with that same 6to4 trick. This is all meant to be fast to deploy, and a stop-gap to make things more usable until we have good native v6 everywhere. It's not meant to be a replacement for native v6. If you put one of these in, you'll get maybe 10-20mbit/s throughput on the current hardware - once you outgrow that you can run it on a regular PC and get maybe 100mbit/s. Ideally though, you'd have good native v6 transit by that point, so you'd never actually outgrow that small hardware. Ideally. As mentioned, I talked about this at NZNOG'08, some slides are at http://www.braintrust.co.nz/tui/ that give you an overview. There's video of me talking to them somewhere as well I think. There's also a (DRAFT) deployment document there which tells you a bit more detail about how it works. I think the software image there is a bit outdated, so I'll get a new one up there ASAP. Bill - yeah I'll sort something out for you this week. My copy of VMWare is the Mac VMWare Fusion thing, which I imagine does things a little differently in terms of disk images etc., so might need to get you to do a bit of manual stuff for me if that's at all possible. Cheers all, -- Nathan Ward ps. Someone on NANOG accused me of trying to sell these things, which was fairly comical. InternetNZ bought the hardware to go at ISPs, the route servers are borrowed from Citylink, APNIC have loaned IP numbers and ASNs, and I've donated my time in between doing work for my customers. So if you're wondering, this is about making NZ's v6 network better (and anyone else who wants to join in), not about anyone making money. pps. If you're a native v6 transit provider who has presence in NZ, talk to me off-list please. People ask me fairly often, and my answer is currently a handful of local ISPs who all get all their connectivity over tunnels. I might just start putting this on the bottom of all my emails to NZNOG until someone pipes up.
participants (3)
-
Bill Walker -
Nathan Ward -
WOOLLEY JONATHAN