From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NAT
Date: Tue, 30 Sep 2003 19:39:49 +0100 [thread overview]
Message-ID: <92f848eb1b18661062ea870639204301@caldo.demon.co.uk> (raw)
In-Reply-To: <200309301805.h8UI50l24099@plg2.math.uwaterloo.ca>
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
i'm not sure it is inherently a bad idea.
it's as messy as it is (and frankly it's not that bad),
mainly because many important ipv4 things were designed
before it, and the ipv6 people apparently thought they
needn't even try, similar to the length field in 802.?
[-- Attachment #2: Type: message/rfc822, Size: 2097 bytes --]
From: Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] NAT
Date: Tue, 30 Sep 2003 14:05:00 -0400 (EDT)
Message-ID: <200309301805.h8UI50l24099@plg2.math.uwaterloo.ca>
I realize that there are a number of reasons why network address
translation is a bad idea, but I'm curious: has anyone ever implemented
it using a plan 9 system, and, if so, what have your experiences been?
next prev parent reply other threads:[~2003-09-30 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-09-30 18:52 ` 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 19:47 Richard C Bilson
2003-09-30 20:13 ` boyd, rounin
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
2008-11-16 15:52 ` erik quanstrom
2008-11-16 16:21 ` lucio
2008-11-18 5:43 ` Sergey Zhilkin
2008-11-16 16:49 erik quanstrom
2008-11-16 17:28 ` Eris Discordia
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=92f848eb1b18661062ea870639204301@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).