[91278] in North American Network Operators' Group
RE: Best practices inquiry: filtering 128/1
daemon@ATHENA.MIT.EDU (Christopher L. Morrow)
Wed Jul 12 10:17:40 2006
Date: Wed, 12 Jul 2006 14:16:07 +0000 (GMT)
From: "Christopher L. Morrow" <christopher.morrow@verizonbusiness.com>
In-reply-to: <F6EA7F9A7FE80C409B346B0B9FDC56490371EF8E@hkghhtmsx01.in.reach.com>
To: "WONG, Yuen-Fung" <Yuen-Fung.WONG@reach.com>
Cc: nanog@nanog.org
Errors-To: owner-nanog@merit.edu
>
> > Do you not prefix-list customers? That'd have solved this, eh?
>
> The problem is: the route is coming from our upstreams / peers.
> that means they also did not filter it out....... :(
oh bummer ;( that's not us sending that is it? :) Honestly, prefix
filtering should apply in both directions. You'd want to be sure that your
upstream didn't send you 1918 prefixes, or bogons or even your internal
infrastructure, eh?
hopefully a simple prefix filter as in the one mentioned a few times from
cymru would fix it for you :)
