Re: blocking AS30060

[Haesu <haesu () towardex com>]

I am already filtering _30060_ and I currently see no problems.

Of course... seeing that email bounces may pile up, I should start routing that /24 to a box on our network pretty 
quick...

-hc

-- 
Sincerely,
  Haesu C.
  TowardEX Technologies, Inc.
  WWW: http://www.towardex.com
  E-mail: haesu () towardex com
  Cell: (978) 394-2867


On Tue, Sep 16, 2003 at 01:04:18PM -0400, William Allen Simpson wrote:
> Mark Vevers wrote:
> > On Tuesday 16 Sep 2003 6:41 am, John Brown wrote:
> > > we've burned a AS for this, ICK
> >
> > Yup - and 2 /24's ....
> >
> > #show ip bgp regexp _30060$
> >    Network          Next Hop            Metric LocPrf Weight Path
> > *>i12.158.80.0/24   xxx.xxx.xxx.xxx         305    100      0 1239 7018 26134
> >  30060 ? *>i64.94.110.0/24   xxx.xxx.xxx.xxx       305    100      0 1239
> >  7018 26134 30060 ?
> >
> > > based on the ASNAME, its seems a nice little route-map
> > > /dev/null will be real easy.  As long as they keep prefixs
> > > used in this really dumb idea for this idea.
> >
> > If you have a full table (i.e. no default) just drop inbound routes with a
> > AS path _30060$
> Are there any adverse side effects, that anybody can think of?
>
> -- 
> William Allen Simpson
>     Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32