Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Daniel <tech@tootai.net>
Cc: Netfilter list <netfilter@vger.kernel.org>
Subject: Re: map problem with port range
Date: Wed, 1 Nov 2023 09:32:21 +0100	[thread overview]
Message-ID: <ZUINFUf9id6w7YUI@calendula> (raw)
In-Reply-To: <c0f8e0aa-93dd-46c6-9eda-7cb7934bf1c6@tootai.net>

On Tue, Oct 31, 2023 at 07:38:30PM +0100, Daniel wrote:
> Hi list
> 
> nft 1.02 I have following map configuration:
> 
> map forward_udp.lan {
>     type ipv6_addr . inet_service : interval ipv6_addr . inet_service
>     flags interval
>     elements = { 2001:db8::1 . 20000-24999 : 2001:db8:16e:10::ffee .
> 20000-24999 }
> }
> 
> ip6 chain prerouting
> 
> add rule ip6 nat prerouting ip6 daddr . udp dport map @forward_udp.lan

What is your intention with this rule?

Are you looking up for a matching packet in this map using

        ip6 daddr . udp dport

as key?

  reply	other threads:[~2023-11-01  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 18:38 map problem with port range Daniel
2023-11-01  8:32 ` Pablo Neira Ayuso [this message]
2023-11-01 13:28   ` Daniel
2023-11-02 10:15     ` Pablo Neira Ayuso

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=ZUINFUf9id6w7YUI@calendula \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=tech@tootai.net \
    /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