[118363] in North American Network Operators' Group
Re: 109/8 - not a BOGON
daemon@ATHENA.MIT.EDU (Shane Short)
Tue Oct 20 08:02:26 2009
From: Shane Short <shane@short.id.au>
In-Reply-To: <c2af1d7d0910200151j4121875cq4d2e525e7434bf1a@mail.gmail.com>
Date: Tue, 20 Oct 2009 20:01:19 +0800
To: Matthew Walster <matthew@walster.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I've found pinging a polite email to the whois contact on the ASN -
sometimes- gives useful results, but not always.
Be aware that you're not only dealing with router black-holes, but
seemingly some people have applied bogon filtering to their BIND name
servers also.
If you can provide a non bogon IP within the same AS, it can be useful
for the person at the other end-- shows them they have a problem.
-Shane
On 20/10/2009, at 4:51 PM, Matthew Walster wrote:
> 2009/10/10 Matthew Palmer <mpalmer@hezmatt.org>
>
>> A pingable address in the problem range would help people to quickly
>> evaluate whether they have a problem in their network or upstreams...
>>
>
> The router has the address "109.68.64.1" - saves giving out
> customer's IP.
>
> Does anyone have any recommendations for dealing with BOGON space that
> hasn't been defiltered by networks? Any ideas how to get people to
> update
> filter lists?
>
> Matthew Walster
