update bogon routes

Hi guys and gals,

please update your bogon lists to avoid 190.0.0.0/8 that has
been asigned 
to LACNIC as you can see from:

ht
tp://www.iana.org/assignments/ipv4-address-space
htt
p://whois.arin.net/whois/?queryinput=190.5.0.0

We have had some problems of being beaten back. Our space,
being 
annocunced by AS 16592, is 190.5.128.0/19

Thanks for your time.


-- 
Miguel Mata
Gerente de Operaciones
Intercom El Salvador
mmataintercom.com.sv
voz: ++(503) 2278-5068
fax: ++(503) 2265-7024

"Intercom, sus Telecomunicaciones en buenas
manos"

Are there any pingable addresses in that block that we can
use to test 
reachability?

Miguel Mata wrote:
> Hi guys and gals,
> 
> please update your bogon lists to avoid 190.0.0.0/8
that has been asigned 
> to LACNIC as you can see from:
> 
> ht
tp://www.iana.org/assignments/ipv4-address-space
> htt
p://whois.arin.net/whois/?queryinput=190.5.0.0
> 
> We have had some problems of being beaten back. Our
space, being 
> annocunced by AS 16592, is 190.5.128.0/19
> 
> Thanks for your time.
> 
> 

yes, you can try 190.5.128.254




On 24 Jul 2006 at 16:25, Marko Milivojevic wrote:

> 
> Are there any pingable addresses in that block that we
can use to test 
> reachability?
> 

-- 
Miguel Mata
Gerente de Operaciones
Intercom El Salvador
mmataintercom.com.sv
voz: ++(503) 2278-5068
fax: ++(503) 2265-7024

"Intercom, sus Telecomunicaciones en buenas
manos"

Miguel,

> We have had some problems of being beaten back. Our
space, being
> annocunced by AS 16592, is 190.5.128.0/19

I only see 190.5.128.0/21, and because it is our policy to
ignore
more-specifics from "PA" space (including
anything more specific than
/21 from 190.0.0.0/8 and the other LACNIC ranges), we don't
accept
that route.  Couldn't you just announce the entire /19?

Regards,
-- 
Simon, AS559.