From: "Kevin P. Fleming" <lists.netfilter@kevin.km6g.us>
Cc: netfilter@vger.kernel.org
Subject: Re: How to configure "full cone" NAT using iptables
Date: Tue, 16 May 2023 07:18:07 -0400 [thread overview]
Message-ID: <a659096f-6142-4193-8b6a-500de4a8467a@app.fastmail.com> (raw)
In-Reply-To: <CAF_hPjOsjMJqvgPLSgfzLqaQ21GTvLUXGNmHCCkxHEbvNCo1ZQ@mail.gmail.com>
On Tue, May 16, 2023, at 07:07, Shane Wang wrote:
> Thanks for your reply.
>
> I think the "--to-destination 10.0.0.1" rule will be matched, and the
> "--to-destination 10.0.0.2" rule will never be matched.
> Does iptables unsupported "full cone" NAT for multiple internal IP addresses?
Does *any* platform support such a configuration? Based on my understanding of what 'full cone' means, every internal address needs a separate external address to be fully mapped to it. Your example shows that you have one external address, which means you can only provide 'full cone' mapping for one internal address, no matter which tool you use.
next prev parent reply other threads:[~2023-05-16 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:58 How to configure "full cone" NAT using iptables Shane Wang
2023-05-16 10:15 ` Reindl Harald
2023-05-16 11:07 ` Shane Wang
2023-05-16 11:17 ` Reindl Harald
2023-05-16 11:18 ` Kevin P. Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 14:32 Joshua Moore
2023-05-16 14:48 ` Reindl Harald
2023-05-16 14:59 ` Joshua Moore
2023-05-16 15:11 ` Reindl Harald
[not found] ` <CAKbpK3xkw5oryaxGdgFmNyxRpgGsh5OnZXsDEjN9DKaJZqhnsw@mail.gmail.com>
2023-05-16 15:16 ` Reindl Harald
2023-05-16 18:36 ` imnozi
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=a659096f-6142-4193-8b6a-500de4a8467a@app.fastmail.com \
--to=lists.netfilter@kevin.km6g.us \
--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).