<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Arial">Below is a basically summary of
the steps involved, rest assured its not for the faint hearted
and I lost a couple of weeks working on it!<br>
<br>
Inspired by
<a class="moz-txt-link-freetext" href="http://www.anchor.com.au/blog/2009/05/testing-your-connectivity/">http://www.anchor.com.au/blog/2009/05/testing-your-connectivity/</a><br>
<br>
1. Retrieve a copy of the full routing table (I used
<a class="moz-txt-link-freetext" href="http://archive.routeviews.org/oix-route-views/">http://archive.routeviews.org/oix-route-views/</a>)<br>
<br>
2. Wrote a vb.net program to extract the first subnet for each
ASN.<br>
<br>
For example our subnet appears as:<br>
* 103.4.212.0/22 85.114.0.217 0 0 0
8492 3356 24130 24473 24473 i<br>
<br>
The ASN we use is 24473<br>
<br>
3. Once I had the subnet list (approximately 38000 entries) I
wrote another program to ping the first 50 ip addresses of every
subnet on my ADSL connection trying to find a pingable address.<br>
Using multithreading and a 1mbit upload, this took around a
couple of hours.<br>
<br>
4. The final list of 28000 entries is on our website
<a class="moz-txt-link-freetext" href="http://www.studiocoast.com.au/downloads/asn-reach-test.txt">http://www.studiocoast.com.au/downloads/asn-reach-test.txt</a> (as
always, use at own risk)<br>
The test was completed last weekend from an Internode ADSL
connection, many of the IP addresses may no longer be reachable.<br>
<br>
5. The final list was then pinged simultanously from both
103.4.212.0/22 and another debogoned range on the same network.<br>
<br>
6. The result was about 400 ASNs that could not be accessed. I
then used the various IP whois servers to retrieve the technical
email contacts and send them an email requesting the prefix be
de-bogoned.<br>
Only around 250 ASNs had contact emails that I could find.<br>
In the email I referenced
<a class="moz-txt-link-freetext" href="http://www.ris.ripe.net/cgi-bin/debogon.cgi">http://www.ris.ripe.net/cgi-bin/debogon.cgi</a>, Cymru and the IETF
draft.<br>
<br>
7. Around 120 ASNs responded and fixed their filters. <br>
<br>
Regards,<br>
<br>
Martin Sinclair<br>
StudioCoast<br>
</font></font><br>
On 25/08/2011 12:15 PM, Martin - StudioCoast wrote:
<blockquote cite="mid:4E55B04A.4070004@studiocoast.com.au"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font size="-1"><font face="Arial">Hi,<br>
<br>
Just thought I would let everyone know that the bogon
filtering issues on the 103.0.0.0 block are now resolved
amongst australian isps.<br>
As far as I can tell, visibility is 100% in Australia now that
Three have removed their filter.<br>
<br>
I have also completed an ASN scan of the greater internet (all
38000 of them!) and identified 300 ASNs that may be blocking
the prefix.<br>
Each ASN owner was contacted and so far 130 or so have removed
the filter.<br>
<br>
If anbody would like some further information on how the tests
were conducted let me know.<br>
<br>
Regards,<br>
<br>
Martin Sinclair<br>
StudioCoast<br>
<br>
</font></font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
</body>
</html>