From: sorcus@inwebse.com
To: Anton Danilov <littlesmilingcloud@gmail.com>
Cc: Netfilter <netfilter@vger.kernel.org>
Subject: Re: What wrong with snat in nftables?
Date: Mon, 17 Jul 2017 21:24:00 +0000 [thread overview]
Message-ID: <3160df4f931c5b244f092aebdfa409b5@inwebse.com> (raw)
In-Reply-To: <b9e98380dacecbec99d0e0aea7847042@inwebse.com>
Solved. http://marc.info/?l=netfilter-devel&m=150027256708621&w=2
You are probably lacking the reply NAT chain, which needs to be
registered.
https://wiki.nftables.org/wiki-nftables/index.php/Performing_Network_Address_Translation_(NAT)
I'm updating right now the wiki to put this in bold.
On 2017-07-15 22:47, sorcus@inwebse.com wrote:
> Output for command nft --debug all -f ruleset
>
> https://gist.github.com/MrSorcus/2c8c65461e3c65fb70364f3a70d95439
prev parent reply other threads:[~2017-07-17 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 13:36 What wrong with snat in nftables? sorcus
2017-07-11 10:10 ` Anton Danilov
[not found] ` <e55eeed4d10d0209dc4441a83b1bc922@inwebse.com>
2017-07-14 1:06 ` sorcus
2017-07-15 22:47 ` sorcus
2017-07-17 21:24 ` sorcus [this message]
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=3160df4f931c5b244f092aebdfa409b5@inwebse.com \
--to=sorcus@inwebse.com \
--cc=littlesmilingcloud@gmail.com \
--cc=netfilter@vger.kernel.org \
/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