All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Martin Zaharinov <micron10@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter <netfilter@vger.kernel.org>,
	netfilter-devel@vger.kernel.org
Subject: Re: Bug report DNAT destination not work
Date: Thu, 2 Mar 2023 20:40:05 +0100	[thread overview]
Message-ID: <20230302194005.GA9239@breakpoint.cc> (raw)
In-Reply-To: <ABA514EB-3C64-4A16-8D07-1318FB9AB63F@gmail.com>

Martin Zaharinov <micron10@gmail.com> wrote:
> Hi Florian
> 
> 
> i recheck and libxt_DNAT.so is symlink to libxt_NAT.so
> 
> and i try : 
> 
> iptables v1.8.9 (nf_tables)

What did you try?

>   --modprobe=<command>		try to insert modules using this command
>   --set-counters -c PKTS BYTES	set the counter during insert/append
> [!] --version	-V		print package version.
> 
> 
> and show help .

No idea what you did or what you are trying to show.
IFF you ran "iptables -j DNAT --help", then libxt_DNAT is not
found resp. iptables is looking at the wrong place.

$ iptables-legacy -V
iptables v1.8.9 (legacy)
$ iptables -j DNAT --help
[..]
DNAT target options:
 --to-destination [<ipaddr>[-<ipaddr>]][:port[-port[/port]]]
                  Address to map destination to.
[--random] [--persistent]
$

I can only guess what the problem might be.

Maybe 'strace -f -e file iptables -j DNAT --help' will give a clue,
there should be lines like this:

newfstatat(AT_FDCWD, "/usr/lib64/xtables/libipt_DNAT.so", 0x7ffe94e3f180, 0) = -1 ENOENT
newfstatat(AT_FDCWD, "/usr/lib64/xtables/libxt_DNAT.so", {st_mode=S ... = 0
openat(AT_FDCWD, "/usr/lib64/xtables/libxt_DNAT.so", O_RDONLY|O_CLOEXEC) = 4

  reply	other threads:[~2023-03-02 19:40 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 ` Bug report DNAT destination not work Florian Westphal
2023-03-02 11:45   ` Martin Zaharinov
2023-03-02 19:40     ` Florian Westphal [this message]
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=20230302194005.GA9239@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 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.