Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Giorgio <giorgio.nicole@arcor.de>
To: netfilter@vger.kernel.org
Subject: nft rule to redirect multiple ports using maps
Date: Thu, 8 Oct 2015 22:12:30 +0200	[thread overview]
Message-ID: <5616CE2E.1070200@arcor.de> (raw)

Hi,

in the answer at:

marc.info/?l=netfilter&m=144286539313019&w=2

there is a cool example of how to use nft maps to write a rule
that defines multiple dnats:

nft add rule nat prerouting dnat \
      tcp dport map { 1000 : 1.1.1.1, 2000 : 1.1.1.1 } : \
      tcp dport map { 1000 : 1234, 1001 : 2222 }


Now I would like to do something similar with port redirections
to generalize rules like:

nft add rule nat prerouting tcp dport 22 redirect to 2222

found on the nftable wiki:

http://wiki.nftables.org/wiki-nftables/index.php/Performing_Network_Address_Translation_%28NAT%29

Here is my (faulty) command line:

# nft add rule nat prerouting redirect to tcp dport map { 22 : 2222, 23
: 2323 }
<cmdline>:1:37-74: Error: transport protocol mapping is only valid after
transport protocol match
add rule nat prerouting redirect to tcp dport map { 22 : 2222, 23 : 2323 }

I want to redirect a list of dports (22 and 23) to a correspondent list
of new dports (2222 and 2323).

I know that there is a way to do it but can't get the logic behind the
syntax of this.

giorgio

             reply	other threads:[~2015-10-08 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 20:12 Giorgio [this message]
2015-10-09 10:56 ` nft rule to redirect multiple ports using maps Pablo Neira Ayuso
2015-10-09 18:09   ` Neal P. Murphy

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=5616CE2E.1070200@arcor.de \
    --to=giorgio.nicole@arcor.de \
    --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