From: "Mucha Marcin, Sieciuch.com" <m.mucha@sieciuch.com>
To: netfilter@vger.kernel.org
Subject: nftables 1.0.6: snat with maps
Date: Wed, 02 Aug 2023 12:17:58 +0200 [thread overview]
Message-ID: <34f5ce6552e75f830d9340e8d576b73e@sieciuch.com> (raw)
Hello,
I'm having trouble with moving from this snat rule:
chain source-nat {
type nat hook postrouting priority 100; policy accept;
ct state invalid drop;
ip saddr 10.0.0.0/24 oif enp7s0 snat to 192.168.10.8 persistent;
ip saddr 10.1.0.0/24 oif enp7s0 snat to 192.168.10.9 persistent;
}
to the one that uses maps based on
https://wiki.nftables.org/wiki-nftables/index.php/Multiple_NATs_using_nftables_maps
:
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};
}
My problem is - I'm getting syntax error after checking config with "nft
-cf /etc/nftables.conf":
"/etc/nftables.conf:43:83-83: Error: syntax error, unexpected newline
oif enp7s0 ip saddr maps {10.0.0.0/24 : 192.168.10.8, 10.1.0.0/24 :
192.168.10.9};
^"
Could I ask you for a help?
System: Debian 12, Nftables 1.0.6
uname -a: 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2
(2023-07-27) x86_64 GNU/Linux
--
Thank you for your help!
Mucha Marcin
next reply other threads:[~2023-08-02 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 10:17 Mucha Marcin, Sieciuch.com [this message]
2023-08-02 14:36 ` nftables 1.0.6: snat with maps Eric
-- 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=34f5ce6552e75f830d9340e8d576b73e@sieciuch.com \
--to=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).