IPsec VTI: Assigned interface firewall rules are never parsed
Traffic entering an assigned VTI interface never hits firewall rules on that specific interface tab even if they are present.
Traffic must still be passed on the main IPsec tab.
This is potentially confusing, it's not the expected behavior that other interface types exhibit.
#1 Updated by Jim Pingle over 2 years ago
- Subject changed from IPSec VTI: Assigned interface firewall rules are never parsed to IPsec VTI: Assigned interface firewall rules are never parsed
- Description updated (diff)
- Assignee deleted (
Issue #8685 will work around this for now, but we can use this issue to track the longer-term problem of how these rules interact. We may have to wait for FreeBSD to solve this one since it appears to be an issue in how pf and if_ipsec interact, and how traffic shows up both on enc0 and the specific ipsecXXXX interface.
#2 Updated by Jim Pingle 11 months ago
Re-tested this since we have a new base OS on 2.5.0. Unfortunately, this still behaves the same way on 12.1-STABLE:
Adding a pf rule on a VTI interface, it does not function as expected. With no rules on enc0, and a pass all rule on ipsec4000, no traffic is passed.
@145(1528159274) pass in quick on ipsec4000 reply-to (ipsec4000 10.6.106.2) inet all flags S/SA keep state label "USER_RULE: VTI Test Rule" [ Evaluations: 16050 Packets: 0 Bytes: 0 States: 0 ] [ Inserted: pid 21034 State Creations: 0 ]
Note that the evaluations counter increases, but it never matches.
tcpdump does not show any packets arriving on the ipsec4000 interface with this rule present.
If you add a rule to enc0 to pass the traffic, it works and then traffic also appears in tcpdump captures on ipsec4000 as it flows.
Packets are always visible in tcpdump on enc0.
#3 Updated by Ari Suutari 10 months ago
Is this related:
filtertunnel sysctls seem to be 0 in pfsense.
#4 Updated by Jim Pingle 10 months ago
If it works, we can document it at least. But we'd also have to check for regressions in behavior of tunneled (non-VTI) IPsec, transport mode IPsec, and general IPsec throughput/performance.
#6 Updated by Jim Pingle 7 months ago
I thought it was noted here but I don't see it. There is another FreeBSD issue at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248474 in which they recommend disabling pfil for if_enc and setting filtertunnel similar to the above:
net.enc.out.ipsec_filter_mask=0 net.enc.in.ipsec_filter_mask=0 net.inet.ipsec.filtertunnel=1 net.inet6.ipsec6.filtertunnel=1
However, that cripples policy-based tunnels since there would now be no way to filter their traffic.
There is still no acceptable solution that allows both to work at once.
#7 Updated by Jim Pingle 2 months ago
In addition to the above, the BPF mask also needs changed.
The complete set of required sysctl values are:
sysctl net.inet.ipsec.filtertunnel=1 sysctl net.inet6.ipsec6.filtertunnel=1 sysctl net.enc.out.ipsec_bpf_mask=0 sysctl net.enc.in.ipsec_bpf_mask=0 sysctl net.enc.out.ipsec_filter_mask=0 sysctl net.enc.in.ipsec_filter_mask=0
And then change source:src/etc/inc/filter.inc#L101 to:
$filter_interface_blacklist = array();
With that in place, rules on assigned VTI interface tabs are respected and rules on the IPsec tab (enc0) are ignored. Since it's default deny, no traffic on enc0 will pass. (Meaning that policy-based tunnels cannot pass traffic no matter what, only assigned VTI w/rules on tabs can)
#8 Updated by Jim Pingle 2 months ago
I made patch (attached) that adds a GUI option to toggle between the two behaviors: Filtering on enc0 (tunnel+vti), and filtering on the assigned VTI interfaces (but blocks all tunnel mode traffic). With the option set, firewall rule tabs are visible for the assigned VTI interfaces, the IPsec tab is hidden. NAT rules on VTI interfaces work.
It works, but obviously it's a big trade-off.
It's better than not having a choice, though, at least until a solution can be found in FreeBSD.