From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] DNS/DHCP/AUTH with Raspberry Pi?
Date: Sat, 11 Oct 2014 15:54:45 -0400 [thread overview]
Message-ID: <E03BD3DE-5EA3-48AA-8D3D-DE9FE4DE1B5A@9srv.net> (raw)
In-Reply-To: <20141011193552.876B0A0112@smtp.hushmail.com>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Oct 11, 2014, at 15:35 , brankush@hushmail.com wrote:
> It might be silly, but how about this:
>
> ISP router ----- Plan9 ----- Linux+P9P
>
> Mount the /net from Plan9 machine on the Linux machine, and add some iptables rules.
> Do you think it will work?
Not without substantial development work (I'd bet more than simply putting NAT on Plan 9). Once you get Plan 9's /net on the linux box, nothing's going to know what to do with it. The existing p9p code won't use it directly, nor will iptables know how to send packets there.
If you want Plan 9 to do NAT, just do that.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
next prev parent reply other threads:[~2014-10-11 19:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 12:56 brankush
2014-10-10 15:41 ` Brian L. Stuart
2014-10-10 18:16 ` Jeremy Jackins
2014-10-11 19:35 ` brankush
2014-10-11 19:54 ` Anthony Sorace [this message]
2014-10-11 20:33 ` Quintile
2014-10-11 21:31 ` brankush
2014-10-11 22:04 ` David du Colombier
2014-10-13 16:18 ` erik quanstrom
2014-10-13 18:23 ` cinap_lenrek
2014-10-13 20:47 ` brankush
2014-10-14 4:31 ` lucio
2014-10-14 6:11 ` cinap_lenrek
2014-10-14 6:27 ` lucio
2014-10-15 3:51 ` Iruatã Souza
2014-10-10 20:56 ` Quintile
2014-10-10 21:08 ` erik quanstrom
2014-10-10 21:39 ` Quintile
2014-10-11 22:00 ` brankush
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=E03BD3DE-5EA3-48AA-8D3D-DE9FE4DE1B5A@9srv.net \
--to=a@9srv.net \
--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).