From: Ray Soucy <rps@maine.edu>
To: netfilter@vger.kernel.org
Subject: RFC6296 (NPTv6) for ip6tables
Date: Mon, 16 Jul 2012 13:42:03 -0400 [thread overview]
Message-ID: <CALFTrnP3xr89ej_f9CEd4LdoUZ5=a4OP__5oPuVa2gto1FSFUA@mail.gmail.com> (raw)
A while back Kaber posted a kind of "fist stab" at implementations for
NPTv6 and other "NAT" -like functionality.
https://github.com/kaber/nf-nat-ipv6
Understanding that the use of "NAT" with v6 can be a religious issue;
I'm not trying to start a flame war on it or anything.
Two questions:
1) Are there any plans to include this functionality in a production
release of iptables (perhaps even just having it be a compile option
disabled by default)
2) Has any more work been done on this since the work by Kaber
mentioned above? If so, where can I find it?
--
Ray Soucy
Epic Communications Specialist
Phone: +1 (207) 561-3526
Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/
reply other threads:[~2012-07-16 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALFTrnP3xr89ej_f9CEd4LdoUZ5=a4OP__5oPuVa2gto1FSFUA@mail.gmail.com' \
--to=rps@maine.edu \
--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 NNTP newsgroup(s).