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.