Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 May 2021 15:58:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        ipfw@FreeBSD.org
Subject:   [Bug 255928] ipfw: nat64 not working on 13.0-RELEASE
Message-ID:  <bug-255928-8303-ff1EYIPkUq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-255928-8303@https.bugs.freebsd.org/bugzilla/>
References:  <bug-255928-8303@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255928

--- Comment #5 from PaulC <paul.chakravarti@gmail.com> ---
I've done some more testing with a cut-down ruleset and it looks like the
problem is caused by the 'net.inet.ip.fw.nat64_direct_output=3D1' sysctl. I=
 had
set this to 1 to make sure the NAT64 traffic wasn't re-evaluated by ipfw so
that I could still use the host IPv4 address locally (using a keep-state
outgoing rule to avoid all the traffic being grabbed by the nat64 rule) how=
ever
with a bit of fiddling with the ruleset I can do this using tags with
'net.inet.ip.fw.nat64_direct_output=3D0'.

It does look like there is still a regression (this worked on 12.2) but cou=
ld
be a pretty unusual case.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255928-8303-ff1EYIPkUq>