<div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> > Does that Netcomm and other gear in that same leage actually support v6</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> > properly?</span>
</div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">I did a bit of work with Netcomm after Mark / Matthew left Internode in testing the firmware and it worked well. There was only one minor concern before I would have been ready to Netcomm to release it although never had a chance to have it resolved before I left Helpdesk.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">>put @ipv6 into the username field (i think they default to ipv6 for new customers now?)</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Correct, IPv6 is set on the backend by default, the setting can be changed in My Internode. Default = having to use @ipv6.internode Enabled = Dual stack using @<a href="http://internode.on.net">internode.on.net</a> Disabled = Off</span></div>
</div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div>>I have a Billion 7401VGP-M, and there's no firmware upgrade at all which would provide IPv6 support</span> <div>
<br></div><div>None of the M series are IPv6 compatible unfortunately.</div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">>... and an NBN connection, with new dual-stack CPE replacing their</span><br style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">>5-year-old v4-only ADSL modem.</span>
</div><div><span style="font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br></span></div><div><span style="background-color:rgb(255,255,255)"><font face="arial, sans-serif">Which reminds me the NP805N was released recently and it was actually out of box IPv6, in addition to the Siemens C610 which is slated to get IPv6 later this year and the end point is definitely getting there.</font></span></div>
<div><br></div><div><div><br></div><div><br clear="all">Thanks,<div><br></div><div>Grant Moritz</div><div><br></div><br>
<br><br><div class="gmail_quote">On Wed, Mar 14, 2012 at 5:19 PM, Smith, Mark <span dir="ltr"><<a href="mailto:mark.smith@nn.com.au">mark.smith@nn.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Variable length addresses have been done before (TCPv1 (TCP/IP before TCP and IP were split), CLNS), and the majority of humans tend to simple fixed length addressing, even when they have a choice. My understanding is that address lookups would also be harder or at least the hardware to make them fast would also be more expensive.<br>
<br>
(TCPv1 supported variable length addresses composed of a number of 4 bit components, with the number of components also encoded as 4 bits, ranging in value from 1 to 15, giving a maximum variable length address size of 60 bits.)<br>
<div class="im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a> [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Mark Delany<br>
Sent: Wednesday, 14 March 2012 5:08 PM<br>
To: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br>
Subject: Re: [AusNOG] My Predictions for the ISP Industry<br>
<br>
</div><div class="HOEnZb"><div class="h5">On 14Mar12, Mark Newton allegedly wrote:<br>
> On Wed, Mar 14, 2012 at 03:10:30PM +1000, Terry Sweetser wrote:<br>
><br>
> > On 14/03/12 12:17, Noel Butler wrote:<br>
> > > facebook (god help them)<br>
> ><br>
> > <a href="https://www.v6.facebook.com/" target="_blank">https://www.v6.facebook.com/</a><br>
><br>
> Which is, of course, 2620:0:1cfe:face:b00c::3<br>
> ^^^^^^^^^<br>
><br>
> I prefer to put dead:beef:c00f:ee into my addresses.<br>
<br>
Anyone remember the suggestion to make v6 addresses be variable length strings?<br>
<br>
Route my packet to com.facebook.www please.<br>
<br>
Or route my packet to org.dotat.atdot@newton where org.dotat.atdot decides what to do with anything following its own prefix.<br>
<br>
Crazy? Maybe. I do note however that both "com.facebook.www" and "org.dotat.atdot" fit in the same space as a v6 address and present a self-encoded CIDR-like address.<br>
<br>
<br>
Mark.<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" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
<br>
</div></div><div class="im HOEnZb">This email is intended for the named recipient only. The information contained in this message may be confidential, or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of the email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately and please delete this message completely from any systems. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you.<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit <a href="http://www.symanteccloud.com" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<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" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br></div></div>