From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NAT implementation
Date: Wed, 15 Apr 2009 12:06:40 -0400 [thread overview]
Message-ID: <20090415160640.GR4823@masters6.cs.jhu.edu> (raw)
In-Reply-To: <bfdb2cad0904150503o510badf5pe0aa2222ef4fd29a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Wed, Apr 15, 2009 at 02:03:35PM +0200, Patrick Kristiansen wrote:
> I'm thinking of writing a NAT implementation for plan 9.
I would suggest instead that it might be easier to write an adaptor program
for non-Plan 9 hosts which made their network stacks talk to a /net. That
is, you'd want a program which spoke TAP/TUN out one end to the host kernel
and out the other dialed and imported /net from the Plan 9 gateway. AFAIK
TAP/TUN-like things exist on most OSes, and there's good example code in
OpenVPN (for example).
The program would have to know enough about the on-the-wire representation
of TCP/IP and UDP/IP to do connection tracking etc. (much like NAT, I
suppose) but the advantage is that it wouldn't impact the Plan 9 kernel.
--nwf;
P.S. This idea shamelessly stolen from vsrinivas, but he's mailing-list shy.
[-- Attachment #2: Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2009-04-15 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 12:03 Patrick Kristiansen
2009-04-15 12:32 ` Devon H. O'Dell
2009-04-15 13:44 ` Patrick Kristiansen
2009-04-15 12:46 ` erik quanstrom
2009-04-15 16:06 ` Nathaniel W Filardo [this message]
2009-04-15 16:29 ` Anthony Sorace
2009-04-15 16:41 ` Devon H. O'Dell
2009-04-15 16:31 ` Devon H. O'Dell
2009-04-15 16:44 ` Anthony Sorace
2009-04-15 17:32 ` blstuart
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=20090415160640.GR4823@masters6.cs.jhu.edu \
--to=nwf@cs.jhu.edu \
--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).