Page MenuHomeFreeBSD

pf: distinguish forwarding and output cases for pf_refragment6()
Needs ReviewPublic

Authored by kp on Mar 13 2023, 5:19 PM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 10 2024, 10:09 AM
Unknown Object (File)
Sep 26 2024, 10:02 PM
Unknown Object (File)
Sep 26 2024, 9:23 AM
Unknown Object (File)
Sep 26 2024, 9:23 AM
Unknown Object (File)
Sep 26 2024, 9:23 AM
Unknown Object (File)
Sep 25 2024, 6:45 AM
Unknown Object (File)
Sep 24 2024, 9:00 AM
Unknown Object (File)
Sep 24 2024, 3:40 AM

Details

Reviewers
None
Group Reviewers
network
pfsense
Summary

Re-introduce PFIL_FWD, because pf's pf_refragment6() needs to know if
we're ip6_forward()-ing or ip6_output()-ing.

ip6_forward() relies on m->m_pkthdr.rcvif, at least for link-local
traffic (for in6_get_unicast_scopeid()). rcvif is not set for locally
generated traffic (e.g. from icmp6_reflect()), so we need to call the
correct output function.

Sponsored by: Rubicon Communications, LLC ("Netgate")

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 50354
Build 47246: arc lint + arc unit

Event Timeline

kp requested review of this revision.Mar 13 2023, 5:19 PM
sys/net/pfil.c
204–205

This somewhat relaxes the old assertion. I think it is still important to protect against dumb case of two directions. Maybe add two assertions?

sys/netpfil/pf/pf.c
7956
		action = pf_refragment6(ifp, m0, mtag, pflags & PFIL_FWD);
sys/netpfil/pf/pf_norm.c
47

This won't be needed if using bool argument.

945–946

I'd suggest to use bool forward here instead of int pflags, but it is up to you.

1016–1017

Style: should be one line

kp marked 5 inline comments as done.Mar 14 2023, 10:26 AM