From: Eric Grosse <ehg@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: NAT
Date: Tue, 30 Sep 2003 15:38:30 -0400 [thread overview]
Message-ID: <cca1d844206a5b34f66973ddcdbf51f7@plan9.bell-labs.com> (raw)
In-Reply-To: <200309301924.h8UJObr00040@plg2.math.uwaterloo.ca>
Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca> wrote:
> Ah. I found the paper by ehg and ynl. Nice, but I don't have any
> spare network processors lying around. Of course, I wouldn't actually
> need them to do the simple/low volume stuff that I want to do.
IEEE Network, July/August 2003, 17:4,35-39
We also did it in Plan 9 on a simple PC, for comparison and to get
the code right before diving into IXP1200 assembler. As far as
Plan 9 experience is concerned, the nice part was how easily IPv6
went in. NAT itself is pretty straightforward on any OS.
The Lucent Firewall product runs (a mix of Inferno and) Plan 9.
> Any source available?
Because of the commercial products, we decided not to polish our
NAT implementation and put it into the standard distribution.
With decent home NAT devices available for $50 or less, it
hardly seemed worth the extra effort.
Eric
next prev parent reply other threads:[~2003-09-30 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 19:24 Richard C Bilson
2003-09-30 19:38 ` Eric Grosse [this message]
2003-09-30 21:13 ` vdharani
2003-09-30 20:16 ` boyd, rounin
2003-10-01 0:07 ` David Presotto
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=cca1d844206a5b34f66973ddcdbf51f7@plan9.bell-labs.com \
--to=ehg@lucent.com \
--cc=9fans@cse.psu.edu \
/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).