All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
	Florian Westphal <fw@strlen.de>
Subject: Re: [nft 0.9.3 | kernel 5.4.48] cannot get NAT to work
Date: Wed, 24 Jun 2020 10:14:43 +0200	[thread overview]
Message-ID: <20200624081443.GV26990@breakpoint.cc> (raw)
In-Reply-To: <f67206b8-aebc-47b5-a3e2-d2d07d2bb53e@gmx.net>

ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> Afraid, neither variation works, each throwing
> 
> /etc/fw/test.conf:2:15-24: Error: Could not process rule: No such file or
> directory
>         chain prerouting {
>               ^^^^^^^^^^
> /etc/fw/test.conf:6:15-19: Error: Could not process rule: No such file or
> directory
>         chain input {
>               ^^^^^
> /etc/fw/test.conf:10:15-20: Error: Could not process rule: No such file or
> directory
>         chain output {
>               ^^^^^^
> /etc/fw/test.conf:14:15-25: Error: Could not process rule: No such file or
> directory
>         chain postrouting {
>               ^^^^^^^^^^^
> 
> Don't know whether txt attachments are accepted on this ML but enclosed full
> debug output (if its gets through), through it does not seem to reveal
> anything useful?

No.

> Could this be a bug in the kernel?

Its a kernel bug, or misconfiguration. Nat hook is provided via

 modinfo nft_chain_nat
 filename:
 /lib/modules/5.6.18/kernel/net/netfilter/nft_chain_nat.ko.gz
 alias:          nft-chain-1-nat
 alias:          nft-chain-10-nat
 alias:          nft-chain-2-nat
 license:        GPL
 srcversion:     45E82B99D3993871BD6131E
 depends:        nf_nat,nf_tables
 intree:         Y
 name:           nft_chain_nat
 vermagic:       5.6.18 SMP preempt mod_unload modversions 

  reply	other threads:[~2020-06-24  8:14 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
2020-06-23 23:11           ` ѽ҉ᶬḳ℠
2020-06-24  8:14             ` Florian Westphal [this message]
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=20200624081443.GV26990@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.