aboutsummaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorKristof Provost <kp@FreeBSD.org>2021-10-26 07:59:42 +0000
committerKristof Provost <kp@FreeBSD.org>2021-10-28 08:41:17 +0000
commite5c4987e3fc1997264f4c3a10d3047a9379b9b15 (patch)
tree7688e7ba73d36656d23ef1abe8719dc9f93e268f /tools
parent7fe0c3f8d3303b67e55e3abcd66cbd4a9eaa1a0d (diff)
downloadsrc-e5c4987e3fc1997264f4c3a10d3047a9379b9b15.tar.gz
src-e5c4987e3fc1997264f4c3a10d3047a9379b9b15.zip
pf: fix dummynet + NAT
Dummynet differs from ALTQ in that ALTQ schedules packets after they leave pf. Dummynet schedules them after they leave pf, but then re-injects them. We currently deal with this by ensuring we don't re-schedule a packet we get from dummynet, but this produces unexpected results when combined with NAT, as dummynet processing is done after the NAT transformation. In other words, the second time the packet is handed to pf it may have a different source and destination address. Simplify this by moving dummynet processing to after all other pf processing, and not re-processing (but always passing) packets from dummynet. This fixes NAT of dummynet delayed packets, and also reduces processing overhead (because we only do state/rule lookup for each dummynet packet once, rather than twice). MFC after: 3 weeks Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D32665
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions