From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/signed;
	boundary="Apple-Mail=_FDDA273F-4D25-4417-BFE5-57052C7B1A94";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Anthony Sorace <a@9srv.net>
In-Reply-To: <20141011193552.876B0A0112@smtp.hushmail.com>
Date: Sat, 11 Oct 2014 15:54:45 -0400
Message-Id: <E03BD3DE-5EA3-48AA-8D3D-DE9FE4DE1B5A@9srv.net>
References: <20141010125645.2AE0D609AD@smtp.hushmail.com>
	<1412955711.23424.YahooMailBasic@web184705.mail.ne1.yahoo.com>
	<20141011193552.876B0A0112@smtp.hushmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] DNS/DHCP/AUTH with Raspberry Pi?
Topicbox-Message-UUID: 1a4229ac-ead9-11e9-9d60-3106f5b1d025


--Apple-Mail=_FDDA273F-4D25-4417-BFE5-57052C7B1A94
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 11, 2014, at 15:35 , brankush@hushmail.com wrote:

> It might be silly, but how about this:
>=20
> ISP router ----- Plan9 ----- Linux+P9P
>=20
> 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.


--Apple-Mail=_FDDA273F-4D25-4417-BFE5-57052C7B1A94
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlQ5iwsACgkQyrb52b5lrs5XQgCeJ0Mkdz/bJIYTLg+muW9sWy3a
8dsAnijC5dMV3TqF5wqEQptGdl9Ltxs/
=2N01
-----END PGP SIGNATURE-----

--Apple-Mail=_FDDA273F-4D25-4417-BFE5-57052C7B1A94--