nanog mailing list archives
Best Common Practice - Listening to local routes from peers?
From: "Michael Smith" <mksmith () noanet net>
Date: Thu, 26 Feb 2004 20:22:59 -0800
Hello: We have a customer of a customer who is attempting to send traffic from IP space we control, through the Internet and back into us via one of our transit connections. I have filters in place that block all inbound traffic from the blocks I announce coming in over my transit and peering connections. This is breaking the downstream customer ability to route from them, through UUNet, and back to me. I'm curious what the Best Common Practice is for this type of scenario. I have always used this type of filtering as a way to bury source-spoofed traffic in a DDOS situation but I'm not sure if it's appropriate, generally speaking. If other operators would like to reply directly to me I would be more than happy to summarize to the list. Thank you for any assistance you can provide. Michael Smith mksmith () noanet net
Current thread:
- Best Common Practice - Listening to local routes from peers? Michael Smith (Feb 26)
- Re: Best Common Practice - Listening to local routes from peers? Patrick W . Gilmore (Feb 26)
- Re: Best Common Practice - Listening to local routes from peers? James Edwards (Feb 26)
- Re: Best Common Practice - Listening to local routes from peers? Patrick W . Gilmore (Feb 27)
- Re: Best Common Practice - Listening to local routes from peers? james (Feb 27)
- Re: Best Common Practice - Listening to local routes from peers? Patrick W . Gilmore (Feb 27)
- Re: Best Common Practice - Listening to local routes from peers? Patrick W . Gilmore (Feb 27)
- Re: Best Common Practice - Listening to local routes from peers? Stephen J. Wilcox (Feb 27)