Hacker News new | ask | show | jobs
by toomuchtodo 4484 days ago
Transit providers will null route traffic that's inbound to you if you request it. This lets you stop the traffic at their core, instead of overwhelming your edge gear.

You are the customer after all; you have a say in what traffic makes it to your edge from your upstream provider.
1 comments
scurvy 4484 days ago
He was referring to being nullrouted by transit providers that he's not a customer of. Short of something like a replay of the Morris worm, I can't see that happening.

Transit providers get paid to provide transit. They don't filter traffic that isn't bound for their customers.

link
toomuchtodo 4484 days ago
They do it all the time. Feel free to check out the NANOG mailing list archives regarding the recent NTP UDP amplification attacks: https://www.nanog.org/list/archives/historical
link
scurvy 4484 days ago
No, they don't. Transit providers acting in a pure transit manner do not null route destination networks that they're not responsible for. Provider B, providing transit from AS A to AS C, will not block traffic bound for C or beyond. They might block some things bound for AS B or a customer of AS B, but they're not acting in a pure transit capacity there.

Content and eyeball networks are free to do whatever they want with regards to routing and blocking. Transit providers? No, they just provide transit. That's the business they want to be in. They're not in the blocking business.

Thanks for the NANOG tip though. I'm a member and active participant. See you in Seattle.

The main NANOG threads are about detecting the NTP traffic and blocking malicious requests in content and eyeball networks -- not transit. There's also the OpenNTP project discussion -- http://openntpproject.org/

link