From: Daniel <tech@tootai.net>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Creating a map programmatically with libnftnl
Date: Mon, 27 Mar 2023 19:27:14 +0200 [thread overview]
Message-ID: <f6576546-966c-8e3a-804e-498227eec24e@tootai.net> (raw)
In-Reply-To: <CAOg40qgbgCoVZbv5UFhR9Gxp2MSYsAuBMs4nFeAyzj5imqSfCw@mail.gmail.com>
Hello
Le 27/03/2023 à 19:22, Kiernan George a écrit :
> Hello,
>
> I asked this on 2022-06-30, but never received a response. Could you
> post an example using the libnftnl functions to create a map of the
> following type and insert elements:
>
> type ipv4_addr . inet_service : ipv4_addr
>
> I see an example for creating a set, but I can't figure out how to
> create a map and insert elements into it.
add map ip nat forward_tcp.lan { type ipv4_addr . inet_service :
interval ipv4_addr . inet_service; flags interval; }
add element ip nat forward_tcp.lan { 192.168.10.24 . 58194-58198 :
192.168.10.4 . 58194-58198 }
--
Daniel
prev parent reply other threads:[~2023-03-27 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 17:22 Creating a map programmatically with libnftnl Kiernan George
2023-03-27 17:27 ` Daniel [this message]
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=f6576546-966c-8e3a-804e-498227eec24e@tootai.net \
--to=tech@tootai.net \
--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).