From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] DNS/DHCP/AUTH with Raspberry Pi?
Date: Sun, 12 Oct 2014 00:04:10 +0200 [thread overview]
Message-ID: <20141012000410.523eff3e@zinc.9fans.fr> (raw)
In-Reply-To: <20141011213139.95170A0112@smtp.hushmail.com>
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
next prev parent reply other threads:[~2014-10-11 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 12:56 brankush
2014-10-10 15:41 ` Brian L. Stuart
2014-10-10 18:16 ` Jeremy Jackins
2014-10-11 19:35 ` brankush
2014-10-11 19:54 ` Anthony Sorace
2014-10-11 20:33 ` Quintile
2014-10-11 21:31 ` brankush
2014-10-11 22:04 ` David du Colombier [this message]
2014-10-13 16:18 ` erik quanstrom
2014-10-13 18:23 ` cinap_lenrek
2014-10-13 20:47 ` brankush
2014-10-14 4:31 ` lucio
2014-10-14 6:11 ` cinap_lenrek
2014-10-14 6:27 ` lucio
2014-10-15 3:51 ` Iruatã Souza
2014-10-10 20:56 ` Quintile
2014-10-10 21:08 ` erik quanstrom
2014-10-10 21:39 ` Quintile
2014-10-11 22:00 ` brankush
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=20141012000410.523eff3e@zinc.9fans.fr \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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).