netdev - Re: IPv4 header extension for IPv6 translation support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bohu6cdt.fsf@xmission.com>
Date:	Tue, 28 Aug 2012 12:32:30 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Vlad Maraev <maraevvb@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: IPv4 header extension for IPv6 translation support

Vlad Maraev <maraevvb@...il.com> writes:

> Hi,
> I would be happy to get some feedback on my idea that is described below.
> I need to tell that I'm a newbie in Linux kernel development but it
> would be interesting for me to estimate complexity and to implement
> this in practice.

You are going over territory that has been rather thoroughly explored
already.

You might want to make a study of the rfcs from the ietf that document
why the existing solutions were chosen.

But for a few hints.
- It is possible to implement prefix translation and avoid the need for
  huge NAT state tables.  State tables are only needed when you don't
  have enough addresses or want the benefits of connection tracking.

- Any extention to ipv4 to give it larger addresses is roughly of the
  same difficulty as implementing ipv6.  In fact it is more difficult
  because ipv6 is present in most end devices today, it is the network
  links that are the bottle-neck in rolling out ipv6.

For the best interoperatiblity the best transition strategy remains
dual-stack.  With native ipv6 connectivity and some flavor of ipv4
connectivity (native, dual-stack-lite, or 646xlate).

Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html