nanog mailing list archives
Re: 109/8 - not a BOGON
From: Shane Short <shane () short id au>
Date: Tue, 20 Oct 2009 20:01:19 +0800
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 thathasn't been defiltered by networks? Any ideas how to get people to updatefilter lists? Matthew Walster
Current thread:
- 109/8 - not a BOGON Matthew Walster (Oct 09)
- Re: 109/8 - not a BOGON Shane Short (Oct 09)
- RE: 109/8 - not a BOGON John Stuppi (jstuppi) (Oct 09)
- Re: 109/8 - not a BOGON Leo Vegoda (Oct 09)
- Re: 109/8 - not a BOGON Matthew Palmer (Oct 10)
- Re: 109/8 - not a BOGON Matthew Walster (Oct 20)
- Re: 109/8 - not a BOGON Shane Short (Oct 20)
- Re: 109/8 - not a BOGON Tim Wilde (Oct 20)
- Re: 109/8 - not a BOGON Matthew Walster (Oct 20)