Andy Dills wrote:
On Mon, 9 Jul 2007, Cat Okita wrote:
As far as "needing a verification system", is there something deeply
problematic about filtering your customers? It's a fine example of
thinking globally and acting locally.
That's what I'm curious about...this boils down to L3 not properly
filtering Hanaro.
Having recently turned up some L3 connectivity, I was happy to discover
that they can use any of the routing registries as the source of their
prefix filters. They told me the prefix filters are automatically
constructed based on the RR of your choice...update the RR, and their
filters will update that night, no need to bug them. Yay for that, wish
everybody worked that way.
But...why wasn't Hanaro being filtered? If the filters are being
automatically generated, I would think they would just filter all of their
peers regardless of number of prefixes etc.
Handily it's possible to query Level3's filters through a whois
interface, for example:
whois -h filtergen.level3.net RIPE::AS25577
For some reason this doesn't work:
whois -h filtergen.level3.net APNIC::AS9318
But this does, presumably this one is reading of an internal Level3 db:
whois -h filtergen.level3.net AS9318
List of prefixes returned is:
Prefix list for policy AS9318 =
LEVEL3::AS9318
61.98.32.0/19
61.98.64.0/20
61.98.96.0/20
124.111.0.0/16
210.93.131.0/24
210.93.132.0/22
211.33.96.0/20
211.49.96.0/20
211.49.144.0/20
211.49.192.0/19
211.49.240.0/20
211.59.160.0/19
211.59.208.0/20
211.59.224.0/20
211.110.160.0/19
211.110.224.0/20
211.186.0.0/19
211.186.32.0/20
211.186.64.0/19
211.186.96.0/20
211.186.144.0/20
211.186.160.0/19
211.243.144.0/20
211.243.224.0/19
211.244.0.0/20
211.244.32.0/19
211.244.64.0/20
211.244.176.0/20
211.245.48.0/20
218.49.114.0/24
218.234.87.0/24
Sam
