From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] NAT
Date: Tue, 30 Sep 2003 16:42:39 -0400 [thread overview]
Message-ID: <32217.135.214.42.162.1064954559.squirrel@www.infernopark.com> (raw)
In-Reply-To: <200309301914.h8UJEXN29405@plg2.math.uwaterloo.ca>
>> We (ehg, ynl) implemented a stateful IPv6-IPv4 nat
>> (address/port/protocol translator) in Plan9. Works fine.
>
> Any source available?
>
> I just learned today that my ISP charges $10 per month per extra IP
> address (how's *that* for a profit margin), so it has become something
> more than a casual interest for me. I'm not particularly trusting of
> those little NAT firewall boxes that everyone seems so enamored with
> these days.
whats wrong with it? I think those boxes works well (and act as plug-and-
play firewalls).
> I realize that IPv6-IPv4 is a different kind of translation, but it
> would be nice to have something to start with.
this is for use in the IPv6/IPv4 network. if your ISP gives you IPv4
network connectivity, you wouldnt need it. am i right? or am i missing
something?
dharani
next prev parent reply other threads:[~2003-09-30 20:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 19:14 Richard C Bilson
2003-09-30 20:42 ` vdharani [this message]
2003-09-30 21:25 ` Lyndon Nerenberg
2003-09-30 22:29 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2008-11-16 16:49 [9fans] nat erik quanstrom
2008-11-16 17:28 ` Eris Discordia
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
2003-09-30 19:47 [9fans] NAT Richard C Bilson
2003-09-30 20:13 ` boyd, rounin
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=32217.135.214.42.162.1064954559.squirrel@www.infernopark.com \
--to=vdharani@infernopark.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).