<div dir="ltr"><div><div>Don't speak too soon that 240/8 is unused. Stay tune for the Canonical sponsored RFC that wants to reserve 240/8 for Fan Net:<br><br><a href="http://www.zdnet.com/article/canonical-introduces-fan-networking-for-containers/">http://www.zdnet.com/article/canonical-introduces-fan-networking-for-containers/</a><br><br></div>Kind regards<br><br></div>Paul Wilkins<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 April 2016 at 13:03, Edwin Groothuis <span dir="ltr"><<a href="mailto:edwin@mavetju.org" target="_blank">edwin@mavetju.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 22/04/2016 11:31 am, Ben Hohnke wrote:<br>
> That site does state that those ranges aren't advertised publicly, and<br>
> only used internally - at lease I'm not receiving them on my feeds:<br>
> xxx-xxx-BDR01#sh ip bgp 30.0.0.0<br>
> % Network not in table<br>
</span>> xxx-xxx-BDR01#sh ip bgp <a href="http://30.0.0.0/8" rel="noreferrer" target="_blank">30.0.0.0/8</a> <<a href="http://30.0.0.0/8" rel="noreferrer" target="_blank">http://30.0.0.0/8</a>> longer-prefixes<br>
<span class="">> xxx-xxx-BDR01#<br>
><br>
> Doesn't make it right, however I'm sure in a network of Telstra's scale,<br>
> RFC1918 exhaustion is would be an issue!<br>
<br>
</span><a href="http://240.0.0.0/4" rel="noreferrer" target="_blank">240.0.0.0/4</a> is only unused because "Many implementations of the TCP/IP<br>
protocol stack have the <a href="http://240.0.0.0/4" rel="noreferrer" target="_blank">240.0.0.0/4</a> address block marked as<br>
experimental, and prevent the host from forwarding IP packets with<br>
addresses drawn from this address block.". However, since this is only<br>
for their internal network WAN links, the only hosts who need to be able<br>
to access this are the hosts inside that network. Since that is a small<br>
subset of devices, I find it hard to believe that Telstra couldn't<br>
convince their vendors to make a (hidden) knob somewhere to make this IP<br>
space reachable on their software.<br>
<br>
See also <a href="https://tools.ietf.org/html/draft-wilson-class-e-02" rel="noreferrer" target="_blank">https://tools.ietf.org/html/draft-wilson-class-e-02</a> and<br>
<a href="http://packetlife.net/blog/2010/oct/14/ipv4-exhaustion-what-about-class-e-addresses/" rel="noreferrer" target="_blank">http://packetlife.net/blog/2010/oct/14/ipv4-exhaustion-what-about-class-e-addresses/</a><br>
<br>
But yeah don't steal other peoples IP space, people will get upset if<br>
you start to leak that.<br>
<br>
Edwin<br>
<span class=""><br>
<br>
<br>
><br>
><br>
> On Fri, Apr 22, 2016 at 11:21 AM Nathan Brookfield<br>
> <<a href="mailto:Nathan.Brookfield@simtronic.com.au">Nathan.Brookfield@simtronic.com.au</a><br>
</span><span class="">> <mailto:<a href="mailto:Nathan.Brookfield@simtronic.com.au">Nathan.Brookfield@simtronic.com.au</a>>> wrote:<br>
><br>
> Thus rending anyone who may actually want to reach DOD IP's in those<br>
> ranges unable to do so and going against RFC's and network best<br>
> practise.<br>
><br>
><br>
> Anyone who does that is questionable, in my opinion at least . . . .<br>
><br>
><br>
</span>> ------------------------------------------------------------------------<br>
> *From:* AusNOG <<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a><br>
> <mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>>> on behalf of Damien Luke<br>
> <<a href="mailto:damien.luke@gmail.com">damien.luke@gmail.com</a> <mailto:<a href="mailto:damien.luke@gmail.com">damien.luke@gmail.com</a>>><br>
> *Sent:* Friday, 22 April 2016 11:17 AM<br>
> *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a> <mailto:<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>><br>
> *Subject:* Re: [AusNOG] Telstra using US DOD IP's like they are RFC1918<br>
<span class="">><br>
> I've generally seen it used when they join two MPLS VPNs, they do a<br>
> NAT in between to keep the routing domains separate.<br>
><br>
> Damien<br>
><br>
> On Fri, Apr 22, 2016 at 11:09 AM, Bradley Amm<br>
> <<a href="mailto:Bradley.Amm@telethonkids.org.au">Bradley.Amm@telethonkids.org.au</a><br>
</span>> <mailto:<a href="mailto:Bradley.Amm@telethonkids.org.au">Bradley.Amm@telethonkids.org.au</a>>> wrote:<br>
><br>
> Do they have a MPLS.____<br>
><br>
> They do it their MPLS network____<br>
><br>
> __ __<br>
><br>
> __ __<br>
><br>
> *From:*AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a><br>
> <mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>>] *On Behalf Of *Nathan<br>
> Brookfield<br>
> *Sent:* Friday, 22 April 2016 8:44 AM<br>
> *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a> <mailto:<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>><br>
> *Subject:* [AusNOG] Telstra using US DOD IP's like they are<br>
> RFC1918____<br>
><br>
> __ __<br>
><br>
> Morning All,____<br>
><br>
> __ __<br>
<span class="">><br>
> So I've been asked by a customer to explain a traceroute, after<br>
> reviewing it and telling them to contact Telstra because the hop<br>
> count out of the Telstra network is putrid, I noticed something<br>
</span>> else unusual/concerning:____<br>
><br>
> __ __<br>
><br>
> image001.png____<br>
><br>
> __ __<br>
<span class="">><br>
> Any idea's on why Telstra are using 30.0.0.0 addresses as if<br>
> it's RFC1918 private IP space, surely this is the oversight of<br>
</span>> someone who needs to find a new job.____<br>
><br>
> __ __<br>
><br>
> This IP space belongs to the US Department of Defense.... WTF?____<br>
><br>
> __ __<br>
><br>
> Kindest Regards,____<br>
><br>
> Nathan Brookfield (VK2NAB)____<br>
><br>
> ____<br>
><br>
> Chief Executive Officer____<br>
><br>
> Simtronic Technologies Pty Ltd____<br>
><br>
> ____<br>
><br>
> *Local:* (02) 4749 4949<br>
> <tel:%2802%29%204749%204949> *|* *Fax:* (02) 4749<br>
> 4950 *|* *Direct:* (02) 4749 4951 <tel:%2802%29%204749%204951>____<br>
><br>
> *Web*: <a href="http://www.simtronic.com.au" rel="noreferrer" target="_blank">http://www.simtronic.com.au</a><br>
> <<a href="http://www.simtronic.com.au/" rel="noreferrer" target="_blank">http://www.simtronic.com.au/</a>> *|* *E-mail*: <a href="mailto:nathan.brookfield@simtronic.com.au">nathan.brookfield@simtronic.com.au</a><br>
> <mailto:<a href="mailto:nathan.brookfield@simtronic.com.au">nathan.brookfield@simtronic.com.au</a>>____<br>
><br>
> ____<br>
><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a> <mailto:<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>><br>
<span class="">> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
</span>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a> <mailto:<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> AusNOG mailing list<br>
> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br></div>