From: Eric <evil.function@proton.me>
To: "Mucha Marcin, Sieciuch.com" <m.mucha@sieciuch.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables 1.0.6: snat with maps
Date: Wed, 02 Aug 2023 14:36:03 +0000 [thread overview]
Message-ID: <eajtHN1X5SQfn-dagoPk2oYxeIlA4_TrjP-DS2YR2pH4JkIgOIFMFfJEKWC-pLSafs8li8RLfUl_0JJYKWrq5F3DW9gIwDZ2xd4vB75of8E=@proton.me> (raw)
In-Reply-To: <34f5ce6552e75f830d9340e8d576b73e@sieciuch.com>
On Wednesday, August 2nd, 2023 at 03:17, Mucha Marcin, Sieciuch.com <m.mucha@sieciuch.com> wrote:
>
> chain source-nat {
> type nat hook postrouting priority 100; policy accept;
> ct state invalid drop;
> oif enp7s0 ip saddr maps {10.0.0.0/24 : 192.168.10.8, 10.1.0.0/24 : 192.168.10.9};
> }
I believe you are missing the "snat" operation in the second clause of the rule:
oif enp7s0 snat ip saddr maps {10.0.0.0/24 : 192.168.10.8,
This guy ------ ^^^^
Eric
next prev parent reply other threads:[~2023-08-02 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 10:17 nftables 1.0.6: snat with maps Mucha Marcin, Sieciuch.com
2023-08-02 14:36 ` Eric [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 10:45 Mucha Marcin, Sieciuch.com
2023-08-02 11:10 ` Florian Westphal
2023-08-02 11:54 ` Mucha Marcin (Sieciuch.com)
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='eajtHN1X5SQfn-dagoPk2oYxeIlA4_TrjP-DS2YR2pH4JkIgOIFMFfJEKWC-pLSafs8li8RLfUl_0JJYKWrq5F3DW9gIwDZ2xd4vB75of8E=@proton.me' \
--to=evil.function@proton.me \
--cc=m.mucha@sieciuch.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).