Project

General

Profile

Bug #7142

IPv6: Floating rules on 6rd enabled WAN interfaces doesn't get bound to wan_stf

Added by Kewin Christensen over 3 years ago. Updated 3 months ago.

Status:
Feedback
Priority:
Normal
Category:
Rules / NAT
Target version:
Start date:
01/19/2017
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.3.2
Affected Architecture:
amd64

Description

Found a bug in the handling of floating rules when they need to be applied to 6rd enabled interfaces (which are split into the physical interface and a wan_stf interface behind the scenes).

Tested on pfSense 2.3.2-RELEASE-p1 (amd64 full-install).

To get your bearings:

#System aliases
WAN = "{ igb1_vlan102 wan_stf }"
LAN = "{ igb0 }"
GUEST = "{ igb0_vlan10 }"

  1. Gateways
    GWWAN_6RD = " route-to ( wan_stf 2a00:fd00:fff1:79c8:448:: ) "

The rule below is created via Floating rules and only attached/assigned to "WAN" interface:

: cat rules.debug | grep Testmonkey
pass in log quick on { igb1_vlan102 } reply-to ( wan_stf 2a00:fd00:fff1:79c8:448:: ) inet6 proto tcp from any to any port 9999 tracker 1484828905 flags S/SA keep state label "USER_RULE: Testmonkey"

Notice, that the rule behind the scenes is bound to my "physical" WAN interface, and not to the wan_stf interface. (And firewall logs show that traffic is being blocked when hitting the wan_stf interface).

The same rule, now put directly on "WAN" interface:

: cat rules.debug | grep Testmonkey
pass in log quick on $WAN reply-to ( wan_stf 2a00:fd00:fff1:79c8:448:: ) inet6 proto tcp from any to any port 9999 tracker 1484829068 flags S/SA keep state label "USER_RULE: Testmonkey-on-WAN"

This time the rule is correctly mapped to the underlying 6rd interface.

/Kewin

Associated revisions

Revision bae04c37 (diff)
Added by Viktor Gurov 4 months ago

Floating rules 6RD and 6to4 interface. Fixes #7142

History

#1 Updated by Greg Fox almost 2 years ago

This is still an issue.

#2 Updated by Jim Pingle about 1 year ago

  • Category set to Rules / NAT

#4 Updated by Jim Pingle 4 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#5 Updated by Kewin Christensen 4 months ago

Viktor Gurov wrote:

Fix:
https://github.com/pfsense/pfsense/pull/4341

Wow.. two 6rd fixes in two days, you're on fire mate :)

#6 Updated by Renato Botelho 3 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Also available in: Atom PDF