<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Limiter appears to break IPv6 connectvitity]]></title><description><![CDATA[<p dir="auto">Has anyone else noticed that traffic limiters appear to break IPv6 connectivity and effectively block it.</p>
<p dir="auto">I created a bug report for this issue.</p>
<p dir="auto">http://redmine.pfsense.org/issues/2526</p>
<p dir="auto">Attached is what the limiter info page shows when IPv6 traffic hits it.<br />
<img src="/public/_imported_attachments_/1/Limiter.JPG" alt="Limiter.JPG" class=" img-fluid img-markdown" /><br />
<img src="/public/_imported_attachments_/1/Limiter.JPG_thumb" alt="Limiter.JPG_thumb" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/46450/limiter-appears-to-break-ipv6-connectvitity</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 16:35:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/46450.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 30 Jun 2012 18:53:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Limiter appears to break IPv6 connectvitity on Tue, 03 Jul 2012 01:41:16 GMT]]></title><description><![CDATA[<p dir="auto">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>
]]></description><link>https://forum.netgate.com/post/345136</link><guid isPermaLink="true">https://forum.netgate.com/post/345136</guid><dc:creator><![CDATA[foxale08]]></dc:creator><pubDate>Tue, 03 Jul 2012 01:41:16 GMT</pubDate></item></channel></rss>