Limiter appears to break IPv6 connectivity
|Affected version:||2.1||Affected Architecture:|
IPv6 connectivity through pfSense appears to be blocked when directed through a limiter (accessed under Firewall -> Traffic Shaper.) The applied traffic shapers work properly when IPv4 traffic is directed through them.
Attached is a screen cap of the limiter output when attempting to access IPv6 and IPv4 resources simultaneously.
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.
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.
For informational purposes, this bug is still present. If a limiter is applied on an IPv6 rule, the traffic no longer passes.
#4 Updated by Chris Buechler 9 months ago
- Category set to Traffic Shaper
- Priority changed from Normal to High
- Target version set to 2.1
- Affected version set to 2.1
#5 Updated by Ermal Luçi 8 months ago
- Status changed from New to Feedback
Brought limiters up-to-speed with IPv6.