Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: [nft 0.9.3 | kernel 5.4.48] cannot get NAT to work
Date: Wed, 24 Jun 2020 00:48:54 +0200	[thread overview]
Message-ID: <20200623224854.GU26990@breakpoint.cc> (raw)
In-Reply-To: <6e919ed9-50d9-7a23-a581-2c6110af5108@gmx.net>

ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> It should work then but somehow does not, any way to figure out what is
> going wrong then? I would rather prefer not having to return to IPT.

Works for me on 5.6.18:
table inet nat {
        chain prerouting {
                type nat hook prerouting priority -100; policy accept;
        }

        chain input {
                type nat hook input priority 100; policy accept;
        }

        chain output {
                type nat hook output priority -100; policy accept;
        }

        chain postrouting {
                type nat hook postrouting priority 100; policy accept;
        }
}

load with nft -f.

If it doesn't work, try 'table ip nat' or 'table ip6 nat'.

  reply	other threads:[~2020-06-23 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 20:38 [nft 0.9.3 | kernel 5.4.48] cannot get NAT to work ѽ҉ᶬḳ℠
2020-06-23 21:23 ` Florian Westphal
2020-06-23 21:34   ` ѽ҉ᶬḳ℠
2020-06-23 21:52     ` Florian Westphal
2020-06-23 22:12       ` ѽ҉ᶬḳ℠
2020-06-23 22:48         ` Florian Westphal [this message]
2020-06-23 23:11           ` ѽ҉ᶬḳ℠
2020-06-24  8:14             ` Florian Westphal
2020-06-24  8:47               ` ѽ҉ᶬḳ℠
2020-06-24  8:53                 ` Florian Westphal
2020-06-24  8:59                   ` ѽ҉ᶬḳ℠
2020-06-25  1:45                     ` Duncan Roe
2020-06-25  7:13                       ` ѽ҉ᶬḳ℠
2020-06-25  8:45                         ` ѽ҉ᶬḳ℠
2020-06-26  3:28                           ` Duncan Roe

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=20200623224854.GU26990@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter@vger.kernel.org \
    --cc=vtol@gmx.net \
    /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