<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic IPv6 BNG issues - things just got real in IPv6 Trial</title>
    <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240203#M2760</link>
    <description>So yesterday I upgraded to an ac68 from the ac66.&lt;BR /&gt;It turns out asus on the ARM devices (ac68 is, ac66 is not) forcefully disable file caching, by sending a 1 to drop_caches variable frequently.&lt;BR /&gt;When I connect to a BNG gateway the dhcp6 process on asuswrt goes crazy, it stops and starts very frequently multiple times a second clearly malfunctioning, ASUS staff, john (maintainer of fork) and merlin have all looked into this with no clue what plusnet's gateway equipment is doing. &amp;nbsp;On the ac66 it didnt create a performance impact, it just simply flooded the log with errors.&lt;BR /&gt;On the ac68 because there is effectively no caching, i/o goes through the roof on the router and one of the cpu's gets locked into syscalls. &amp;nbsp;The only way I can prevent this is either been at hand and forcefully killing the dhcp6 master process, or disabling ipv6. &amp;nbsp;Hopping to a non BNG gateway restores normal behaviour.&lt;BR /&gt;So this problem is now bad enough that if I get dumped onto a BNG and either I am not around or I dont notice, it may burn out my router. &amp;nbsp;Currently we are looking to find a way to either enable caching again on the ac68 (I suspect asus disabled it for a reason tho, I think simply due to memory pressure with the new features) or I make a script that when it detects a out of control dhcp6 process it kills the master process. &amp;nbsp;MAking a script to auto hop when BNG is detected is also an option.&lt;BR /&gt;Really hope plusnet sort this out, because the problem is still dragging on.</description>
    <pubDate>Tue, 16 Jun 2015 15:46:45 GMT</pubDate>
    <dc:creator>chrcoluk</dc:creator>
    <dc:date>2015-06-16T15:46:45Z</dc:date>
    <item>
      <title>IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240203#M2760</link>
      <description>So yesterday I upgraded to an ac68 from the ac66.&lt;BR /&gt;It turns out asus on the ARM devices (ac68 is, ac66 is not) forcefully disable file caching, by sending a 1 to drop_caches variable frequently.&lt;BR /&gt;When I connect to a BNG gateway the dhcp6 process on asuswrt goes crazy, it stops and starts very frequently multiple times a second clearly malfunctioning, ASUS staff, john (maintainer of fork) and merlin have all looked into this with no clue what plusnet's gateway equipment is doing. &amp;nbsp;On the ac66 it didnt create a performance impact, it just simply flooded the log with errors.&lt;BR /&gt;On the ac68 because there is effectively no caching, i/o goes through the roof on the router and one of the cpu's gets locked into syscalls. &amp;nbsp;The only way I can prevent this is either been at hand and forcefully killing the dhcp6 master process, or disabling ipv6. &amp;nbsp;Hopping to a non BNG gateway restores normal behaviour.&lt;BR /&gt;So this problem is now bad enough that if I get dumped onto a BNG and either I am not around or I dont notice, it may burn out my router. &amp;nbsp;Currently we are looking to find a way to either enable caching again on the ac68 (I suspect asus disabled it for a reason tho, I think simply due to memory pressure with the new features) or I make a script that when it detects a out of control dhcp6 process it kills the master process. &amp;nbsp;MAking a script to auto hop when BNG is detected is also an option.&lt;BR /&gt;Really hope plusnet sort this out, because the problem is still dragging on.</description>
      <pubDate>Tue, 16 Jun 2015 15:46:45 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240203#M2760</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2015-06-16T15:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240204#M2761</link>
      <description>Would I be right in assuming this only happens when you're using your IPv6 test credentials?</description>
      <pubDate>Tue, 16 Jun 2015 15:56:13 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240204#M2761</guid>
      <dc:creator>bobpullen</dc:creator>
      <dc:date>2015-06-16T15:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240205#M2762</link>
      <description>I assume so since the ipv4 accounts dont have ipv6.&lt;BR /&gt;I am not keen on trying out my ipv4 account given I have just done the effort to get onto a non bng gateway that isnt congested 2 mins ago &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;</description>
      <pubDate>Tue, 16 Jun 2015 20:31:18 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240205#M2762</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2015-06-16T20:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240206#M2763</link>
      <description>Reason I ask is due to gauge the severity of the issue. If it's just the IPv6 accounts that exhibit these symptoms then it's something affecting less than ~20 people (where there's a workaround). If it was to affect IPv4 accounts as well then we'd have a much larger problem on our hands.</description>
      <pubDate>Wed, 17 Jun 2015 12:51:09 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240206#M2763</guid>
      <dc:creator>bobpullen</dc:creator>
      <dc:date>2015-06-17T12:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240207#M2764</link>
      <description>If it affected everyone I expect you would have some more posts about it.&lt;BR /&gt;I can tell you if I ignore the problem it affects the router so bad alot of stuff feels laggy as one cpu core is tied up by the dhcp6 process.</description>
      <pubDate>Wed, 17 Jun 2015 16:51:06 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240207#M2764</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2015-06-17T16:51:06Z</dc:date>
    </item>
    <item>
      <title>Re: IPv6 BNG issues - things just got real</title>
      <link>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240208#M2765</link>
      <description>pressure is off.&lt;BR /&gt;I told the dev to give up yesterday as my problem isnt his doing, to my surprise he left me a message earlier tonight he said he solved the caching issue and did a new firmware, the new firmware has reenabled caching so the router no longer sucking up cpu cycles on the bng's.</description>
      <pubDate>Wed, 17 Jun 2015 20:35:21 GMT</pubDate>
      <guid>https://community.plus.net/t5/IPv6-Trial/IPv6-BNG-issues-things-just-got-real/m-p/1240208#M2765</guid>
      <dc:creator>chrcoluk</dc:creator>
      <dc:date>2015-06-17T20:35:21Z</dc:date>
    </item>
  </channel>
</rss>

