From: Florian Westphal <fw@strlen.de>
To: Martin Zaharinov <micron10@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
netfilter <netfilter@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: Bug report DNAT destination not work
Date: Thu, 2 Mar 2023 11:43:37 +0100 [thread overview]
Message-ID: <20230302104337.GA23204@breakpoint.cc> (raw)
In-Reply-To: <CALidq=VJF36a6DWf8=PNahwHLJd5FKspXVJfmzK3NFCxb6zKbg@mail.gmail.com>
Martin Zaharinov <micron10@gmail.com> wrote:
> iptables -t nat -A PREROUTING -d 100.91.1.238/32 -i bond0 -p tcp --dport
> 7878 -j DNAT --to-destination 10.240.241.99:7878
> iptables v1.8.9 (legacy): unknown option "--to-destination"
> Try `iptables -h' or 'iptables --help' for more information.
Looks like a problem with your iptables installation which can't find
libxt_DNAT.so? In v1.8.9 this should be a symlink to libxt_NAT.so.
If you run 'iptables -j DNAT --help' and it doesn't say
"DNAT target options:" at the end then it very much looks like a
problem with your iptables installation and not the kernel.
> try with kernel 6.1.11 6.1.12 6.1.13
Tested iptables-nft and iptables-legacy on 1.8.9 with kernel 6.1.14, no problems.
There were no significant kernel changes in this area that I know of in
6.1 either.
next parent reply other threads:[~2023-03-02 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALidq=VJF36a6DWf8=PNahwHLJd5FKspXVJfmzK3NFCxb6zKbg@mail.gmail.com>
2023-03-02 10:43 ` Florian Westphal [this message]
2023-03-02 11:45 ` Bug report DNAT destination not work Martin Zaharinov
2023-03-02 19:40 ` Florian Westphal
2023-03-02 10:53 ` Martin Zaharinov
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=20230302104337.GA23204@breakpoint.cc \
--to=fw@strlen.de \
--cc=micron10@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).