https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162012-06-28T13:57:41ZpfSense bugtrackerpfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=93042012-06-28T13:57:41ZAlex Foxfoxale08@gmail.com
<ul></ul><p>This bug applies to 2.1 dev from June 28th as far back as June 20th. Prior to that dates build I was not using 2.1 and cannot comment.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=93342012-07-02T21:17:45ZAlex Foxfoxale08@gmail.com
<ul></ul><p>On review of the screenshot it appears that the limiter is not assigning a bucket for IPv6 traffic denoted by "BKT 0". Additionally it appears that the limiter is not identifying the source/destination of IPv6 traffic properly as denoted by "::/0" for source and destination for each connection. IPv4 traffic has "0.0.0.0/0" for either source or destination and an IPv4 address for the other.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=96372012-08-14T09:32:53ZJim Pingle
<ul></ul><p>For informational purposes, this bug is still present. If a limiter is applied on an IPv6 rule, the traffic no longer passes.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=96392012-08-14T17:56:18ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Category</strong> set to <i>Traffic Shaper (ALTQ)</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>2.1</i></li><li><strong>Affected Version</strong> set to <i>2.1</i></li></ul> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=98392012-10-09T14:28:51ZErmal Luçieri@pfsense.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Brought limiters up-to-speed with IPv6.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=100082012-11-24T13:54:41ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=116712013-06-13T14:18:24ZAlex Foxfoxale08@gmail.com
<ul></ul><p>This problem appears to be present in the Wed Jun 12 06:19:03 EDT 2013 build. IPv6 Traffic hits the limiter as shown below but fails to pass. I did a clean install and created new limiters to be sure. The same limiter was applied to both default pass rules for IPv4 and IPv6. Using Chrome, the error message "Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data." is received when loading IPv6 enabled websites and IPv6 connectivity tests in multiple browsers fail.</p>
<p>*=redacted</p>
<p>Limiters:<br />00001: 14.000 Mbit/s 0 ms burst 0 <br />q131073 50 sl. 0 flows (1 buckets) sched 65537 weight 0 lmax 0 pri 0 droptail<br /> sched 65537 type FIFO flags 0x0 1024 buckets 0 active<br />00002: 2.500 Mbit/s 0 ms burst 0 <br />q131074 50 sl. 0 flows (1 buckets) sched 65538 weight 0 lmax 0 pri 0 droptail<br /> sched 65538 type FIFO flags 0x0 1024 buckets 0 active</p>
<p>Queues:<br />q00001 50 sl. 3 flows (256 buckets) sched 1 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0x00000000/0x0000 -> 0xffffffff/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp<br /> 23 ip 0 ::/0 2601:4:100:1b:f465:b85:****:23d3/0 14 1056 0 0 0<br /> 81 ip 0.0.0.0/0 192.168.***.1/0 45 5045 0 0 0<br /> 94 ip 0.0.0.0/0 192.168.***.14/0 4 396 0 0 0<br />q00002 50 sl. 0 flows (256 buckets) sched 1 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0x00000000/0x0000 -> 0xffffffff/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp<br />q00003 50 sl. 0 flows (256 buckets) sched 1 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0x00000000/0x0000 -> 0xffffffff/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp<br />q00004 50 sl. 5 flows (256 buckets) sched 2 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0xffffffff/0x0000 -> 0x00000000/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp<br /> 88 ip 192.168.***.248/0 0.0.0.0/0 1 76 0 0 0<br /> 90 ip 192.168.***.249/0 0.0.0.0/0 1 76 0 0 0<br />142 ip 0 2601:4:100:1b:f465:b85:****:23d3/0 ::/0 48 15722 0 0 0<br />170 ip 192.168.***.1/0 0.0.0.0/0 27 1520 0 0 0<br />180 ip 192.168.***.14/0 0.0.0.0/0 4 268 0 0 0<br />q00005 50 sl. 0 flows (256 buckets) sched 2 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0xffffffff/0x0000 -> 0x00000000/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp<br />q00006 50 sl. 0 flows (256 buckets) sched 2 weight 1 lmax 0 pri 0 droptail<br /> mask: 0x00 0xffffffff/0x0000 -> 0x00000000/0x0000<br />BKT Prot <em><i>Source IP/port</i></em>_ _<em><i>Dest. IP/port</i></em>_ Tot_pkt/bytes Pkt/Byte Drp</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=171262015-01-31T13:19:32ZCino .cinony@gmail.com
<ul></ul><p>This issue is still not resolved</p>
<p><a class="external" href="https://forum.pfsense.org/index.php?topic=77506.new;topicseen#new">https://forum.pfsense.org/index.php?topic=77506.new;topicseen#new</a></p>
<p>Can this ticket be reopened?</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=173022015-02-12T13:27:55ZErmal Luçieri@pfsense.org
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Feedback</i></li><li><strong>Target version</strong> changed from <i>2.1</i> to <i>2.2.1</i></li><li><strong>Affected Version</strong> changed from <i>2.1</i> to <i>All</i></li></ul><p>A patch has been pushed which will fix limiters with ipv6.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=175942015-03-04T00:57:00ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>confirmed, limiters work correctly on v6 now.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=178472015-03-21T14:02:26ZKill Bill
<ul></ul><p>Ermal Luçi wrote:</p>
<blockquote>
<p>A patch has been pushed which will fix limiters with ipv6.</p>
</blockquote>
<p>Sorry, that did not help. Confirmed at <a class="external" href="https://forum.pfsense.org/index.php?topic=77506.0">https://forum.pfsense.org/index.php?topic=77506.0</a>. No luck with this even with latest 2.2.2-DEV snapshots.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=180932015-04-09T01:17:58ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> set to <i>Chris Buechler</i></li><li><strong>Target version</strong> changed from <i>2.2.1</i> to <i>2.2.3</i></li></ul><p>this is still an issue in some circumstances. To me to better quantify the circumstances where it's an issue.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=186912015-06-07T16:14:27ZErmal Luçieri@pfsense.org
<ul></ul><p>Can you specify the scenario to check it?<br />Normally the only thing i see might be missing some parameter passing to dummynet to calculate the proper flow apart that i do not see any issue.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=186962015-06-07T17:49:06ZErmal Luçieri@pfsense.org
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Feedback</i></li></ul><p>To be retested with a new snapshot there might have been issue with operator precedence in previous patch.</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=188152015-06-15T16:34:04ZKill Bill
<ul></ul><p>Well I think it looks good now.</p>
<p>Tested with bunch of speedtest stuff like <a class="external" href="http://ipv6-test.com/speedtest/">http://ipv6-test.com/speedtest/</a>, <a class="external" href="http://ipv6-speedtest.net/">http://ipv6-speedtest.net/</a>, <a class="external" href="http://www.thinkbroadband.com/ipv6/speed-test.html">http://www.thinkbroadband.com/ipv6/speed-test.html</a>, some browsing, FTP, wget...</p> pfSense - Bug #2526: Limiter appears to break IPv6 connectivityhttps://redmine.pfsense.org/issues/2526?journal_id=188332015-06-16T20:08:33ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>works here too, looks good all around.</p>