From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun, 12 Oct 2014 00:04:10 +0200
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Message-ID: <20141012000410.523eff3e@zinc.9fans.fr>
In-Reply-To: <20141011213139.95170A0112@smtp.hushmail.com>
References: <20141010125645.2AE0D609AD@smtp.hushmail.com>
	<1412955711.23424.YahooMailBasic@web184705.mail.ne1.yahoo.com>
	<20141011193552.876B0A0112@smtp.hushmail.com>
	<E03BD3DE-5EA3-48AA-8D3D-DE9FE4DE1B5A@9srv.net>
	<E03B429F-9E0C-42D6-B1CF-DD255E7168CD@quintile.net>
	<20141011213139.95170A0112@smtp.hushmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] DNS/DHCP/AUTH with Raspberry Pi?
Topicbox-Message-UUID: 1a54c558-ead9-11e9-9d60-3106f5b1d025

One can still take a look to the simple stateless
NAPT implementation I did few years ago.

http://9legacy.org/9legacy/patch/nat.diff

It works, but it's incomplete. However, I think
it's simple enough to be used as an example to
work on a more complete implementation.

Another approach would be to implement translation
in user space instead of kernel space.

--
David du Colombier