From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tom Hacohen <tom@stosb.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables: masquerade sets wrong source address
Date: Thu, 15 Dec 2016 22:29:30 +0100 [thread overview]
Message-ID: <20161215212930.GA13769@salvia> (raw)
In-Reply-To: <CAEvi_o-B50n-qZyRxHC9cmpsjiweidcufFifB0SYsp515THwzQ@mail.gmail.com>
Hi Tom,
On Thu, Dec 15, 2016 at 11:34:57AM +0000, Tom Hacohen wrote:
> Hey,
>
> Thanks for your reply.
>
> I'm sorry, but I don't have access to older kernels. Furthermore,
> this worked with iptables on the same kernel version using the same
> rules as far as I can tell.
Hm, this is working with the same kernel version in iptables? What
kernel version are you using?
> I therefore suspect (without knowing the code) that maybe nftables is trying
> to masquerade all packets while iptables maybe has a noop when there was no
> NAT applied, or if the address is already set correctly? That is the best
> explanation that comes to mind given your assertion about them sharing the
> masquerade code.
Both nft and iptables share the same codebase for NAT/masquerade, so
if this works with iptables, it shoud work with nft too in the same
way.
Please, confirm this, it would be good if we get to the core of the
problem. If the behaviour differs, or started to differ from some
kernel version on, then this is a bug.
Thanks.
next prev parent reply other threads:[~2016-12-15 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 13:28 nftables: masquerade sets wrong source address Tom Hacohen
2016-12-13 14:32 ` /dev/rob0
2016-12-13 14:53 ` Tom Hacohen
2016-12-14 22:28 ` Pablo Neira Ayuso
2016-12-15 11:34 ` Tom Hacohen
2016-12-15 21:29 ` Pablo Neira Ayuso [this message]
2016-12-15 22:47 ` Tom Hacohen
2016-12-16 0:04 ` Tom Hacohen
2016-12-17 14:18 ` Liping Zhang
2016-12-19 2:25 ` Liping Zhang
2016-12-20 15:16 ` Tom Hacohen
2016-12-21 2:39 ` Liping Zhang
2016-12-22 10:26 ` Tom Hacohen
2016-12-22 10:34 ` Florian Westphal
[not found] ` <CAEvi_o8wV5GNk8JvSg96kP3WdDsVsf8PubRe=K1ZiD2+nBaYTg@mail.gmail.com>
2016-12-22 22:40 ` Tom Hacohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161215212930.GA13769@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=tom@stosb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox