From: Matthias Urlichs <matthias@urlichs.de>
To: netdev@vger.kernel.org
Subject: 6to4 NAT ?
Date: Mon, 7 Feb 2011 09:59:10 +0000 (UTC) [thread overview]
Message-ID: <iiofpe$1j4$1@dough.gmane.org> (raw)
Hello,
The problem: I have a 10.*/8 ipv4 network which I want to reach via ipv6.
I.e., what I need is some sort of 6to4 NAT so that traffic from [whereever]
to e.g. fec0:dead:beef:1234::10.1.2.3 ends up as coming from e.g. 10.0.0.1
on the IPv4 side.
"Classic" NAT, in other words, except that (a) one side is on IPv6, and
(b) the destination's v4 address is the tail end of the v6 address.
Cisco boxes can apparently do that. I want my Linux box to do it too. :-P
Is there something like this already out there, or do I need to copy
the NAT kernel modules and start hacking?
(This is not a tunnel: I don't want the IPv6 packets to get encapsulated
in IPv4. That'd require all the systems on the 10.* net to have their own
local tunnel interface. I can't do that.)
--
-- Matthias Urlichs
next reply other threads:[~2011-02-07 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 9:59 Matthias Urlichs [this message]
2011-02-07 10:27 ` 6to4 NAT ? Jasper Spaans
[not found] ` <20110207124138.GW3731@deee.intern.smurf.noris.de>
2011-02-07 13:55 ` Matthias Urlichs
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='iiofpe$1j4$1@dough.gmane.org' \
--to=matthias@urlichs.de \
--cc=netdev@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).