From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] nat
Date: Sun, 16 Nov 2008 17:54:37 +0200 [thread overview]
Message-ID: <10d8f6d9308f84b67b6bcb2ea6924867@proxima.alt.za> (raw)
In-Reply-To: <fec7c4379555cf2f090b38caac39f061@quanstro.net>
> i've got a lot of folk in the house who run whatever.
> i'd really like to decommission the non-plan 9 machine.
> the one thing i need from it is nat. (and i don't want
> to be stuck fiddling more stuff on the dsl appliance.)
> doing nat just isn't that hard. i just need to find the time.
> this is about a summer-of-code sized project. i don't think
> it would require anything from the kernel.
I beg to differ. NAT adds complications to the already complex IP.
Adding NAT to the Plan 9 IP stack can only make it more fragile, why
not leave the job to the appliances that have been designed and
constructed to deal with the problem and have been subject to very
broad testing?
++L
next prev parent reply other threads:[~2008-11-16 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96BA4878DB039F3DAE38CCF2@192.168.1.2>
2008-11-16 15:09 ` [9fans] Do we have a catalog of 9P servers? sqweek
2008-11-16 15:22 ` [9fans] nat erik quanstrom
2008-11-16 15:54 ` lucio [this message]
2008-11-16 15:52 ` erik quanstrom
2008-11-16 16:21 ` lucio
2008-11-18 5:43 ` Sergey Zhilkin
2008-11-16 17:41 ` [9fans] Do we have a catalog of 9P servers? Charles Forsyth
2008-11-16 16:49 [9fans] nat erik quanstrom
2008-11-16 17:28 ` Eris Discordia
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 19:47 [9fans] NAT Richard C Bilson
2003-09-30 20:13 ` boyd, rounin
2003-09-30 19:14 Richard C Bilson
2003-09-30 20:42 ` vdharani
2003-09-30 21:25 ` Lyndon Nerenberg
2003-09-30 22:29 ` Charles Forsyth
2003-09-30 18:05 Richard C Bilson
2003-09-30 18:12 ` Brantley Coile
2003-09-30 18:25 ` ynl
2003-09-30 19:44 ` vdharani
2003-09-30 18:36 ` Brantley Coile
2003-09-30 18:39 ` Charles Forsyth
2003-09-30 18:52 ` boyd, rounin
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=10d8f6d9308f84b67b6bcb2ea6924867@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).