<story><title>IPv6 privacy addresses crashed the MIT CSAIL network</title><url>http://blog.bimajority.org/2014/09/05/the-network-nightmare-that-ate-my-week/</url></story><parent_chain><item><author>ay</author><text>The &amp;quot;issues with IPv6&amp;quot; are with education, operation, configuration.&lt;p&gt;I personally ran WiFi networks with 8000+ wireless clients on a &lt;i&gt;single&lt;/i&gt; &amp;#x2F;64 subnet (my employer&amp;#x27;s CiscoLive conference), and assisted&amp;#x2F;consulted in running the networks with more than 25000 clients on a single &amp;#x2F;64 subnet (Mobile World Congress).&lt;p&gt;The default kinda suck, and the bugs may happen. but the statement &amp;quot;IPv6 is not ready for production&amp;quot; is wrong.&lt;p&gt;I&amp;#x27;d be happy to volunteer a reasonable amount of time to work with the OP or others having a network of &amp;gt;1000 hosts, to debug the issues like this, time permitting, vendor independent. (glass houses and all that).&lt;p&gt;There are bazillion knobs in IPv6 and a lot of things can be fixed by just tweaking the defaults (which kinda suck).&lt;p&gt;Network of &amp;lt;500-700 nodes generally don&amp;#x27;t need to bother much. It&amp;#x27;s not optimal a lot of times with the defaults but it will work.&lt;p&gt;EDIT:&lt;p&gt;the seeming &amp;quot;charity&amp;quot; of volunteering the time isn&amp;#x27;t. I want to understand what is broken, so we can bring it up back to IETF and get it fixed + make better educational publicity to prevent folks shooting themselves in the foot. It&amp;#x27;ll make it to the stacks in another decade, but it will.
IPv6 is powering nontrivial millions of hosts &lt;i&gt;now&lt;/i&gt; - so the correct words to use &amp;quot;needs tweaking for my network&amp;quot;, not &amp;quot;not ready for production&amp;quot;. Let&amp;#x27;s see what the tweaks are and if we can incorporate them into the protocol, if necessary.</text></item></parent_chain><comment><author>cesarb</author><text>Playing devil&amp;#x27;s advocate: your experiences of &amp;quot;CiscoLive conference&amp;quot; and &amp;quot;Mobile World Congress&amp;quot; sound like conferences, which are the kind of scenario where most hosts are connected to the network for less than a day each time.&lt;p&gt;If I understood it correctly, his privacy addresses issue wouldn&amp;#x27;t show up in that scenario, since it needs several days using the same network connection continuously for each host to accumulate enough privacy addresses.</text></comment>
<story><title>IPv6 privacy addresses crashed the MIT CSAIL network</title><url>http://blog.bimajority.org/2014/09/05/the-network-nightmare-that-ate-my-week/</url></story><parent_chain><item><author>ay</author><text>The &amp;quot;issues with IPv6&amp;quot; are with education, operation, configuration.&lt;p&gt;I personally ran WiFi networks with 8000+ wireless clients on a &lt;i&gt;single&lt;/i&gt; &amp;#x2F;64 subnet (my employer&amp;#x27;s CiscoLive conference), and assisted&amp;#x2F;consulted in running the networks with more than 25000 clients on a single &amp;#x2F;64 subnet (Mobile World Congress).&lt;p&gt;The default kinda suck, and the bugs may happen. but the statement &amp;quot;IPv6 is not ready for production&amp;quot; is wrong.&lt;p&gt;I&amp;#x27;d be happy to volunteer a reasonable amount of time to work with the OP or others having a network of &amp;gt;1000 hosts, to debug the issues like this, time permitting, vendor independent. (glass houses and all that).&lt;p&gt;There are bazillion knobs in IPv6 and a lot of things can be fixed by just tweaking the defaults (which kinda suck).&lt;p&gt;Network of &amp;lt;500-700 nodes generally don&amp;#x27;t need to bother much. It&amp;#x27;s not optimal a lot of times with the defaults but it will work.&lt;p&gt;EDIT:&lt;p&gt;the seeming &amp;quot;charity&amp;quot; of volunteering the time isn&amp;#x27;t. I want to understand what is broken, so we can bring it up back to IETF and get it fixed + make better educational publicity to prevent folks shooting themselves in the foot. It&amp;#x27;ll make it to the stacks in another decade, but it will.
IPv6 is powering nontrivial millions of hosts &lt;i&gt;now&lt;/i&gt; - so the correct words to use &amp;quot;needs tweaking for my network&amp;quot;, not &amp;quot;not ready for production&amp;quot;. Let&amp;#x27;s see what the tweaks are and if we can incorporate them into the protocol, if necessary.</text></item></parent_chain><comment><author>x0x0</author><text>And somehow juniper (and juniper support engineers for large routers) is unaware of these things?  I&amp;#x27;m skeptical.  Particularly for ongoing problems where second and third level support get involved.</text></comment>