From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 13 Oct 2014 12:18:35 -0400 To: 9fans@9fans.net Message-ID: <980aa95b9b42f028be8aedca7d081577@ladd.quanstro.net> In-Reply-To: References: <20141010125645.2AE0D609AD@smtp.hushmail.com> <1412955711.23424.YahooMailBasic@web184705.mail.ne1.yahoo.com> <20141011193552.876B0A0112@smtp.hushmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] DNS/DHCP/AUTH with Raspberry Pi? Topicbox-Message-UUID: 1aeabda6-ead9-11e9-9d60-3106f5b1d025 > 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. i'm not proud of this solution, but i'm using a ubiquity wifi router as my nat. it routes all external traffic to /net.alt on the main cpu server, and routes outbound traffic through a nat. i would much prefer a p9 based solution, but i'm also busy and lazy. - erik