From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20140612072922.GD14836@iota.offblast.org> From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= Date: Thu, 12 Jun 2014 11:56:10 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] [GSOC] port forwarding Topicbox-Message-UUID: fa6a271a-ead8-11e9-9d60-3106f5b1d025 If you don't want to PXE-boot, you don't need two NICs on the fs/auth server. As Charles mentioned, QEMU can boot an ELF kernel directly. I would recommend PXE-booting, however, simply because you don't have to do the extra step of getting kernels out of the Plan 9 system and onto Unix. I'm lazy. If you want to PXE-boot, just set up two NICs on the fs/auth server. You do this to create two broadcast domains (so bridging is out), you don't want your external DHCP server to respond to your Plan 9 machines. You don't need to set up two alternate network stacks (as Nick does with his systems), it's fine to have a single stack and have ip/dhcpd listen on your external interface too. ip/dhcpd can be configured not to respond to requests from unknown MAC addresses, so it shouldn't interfere with your external DHCP server. You can give your CPU server two NICs too, that way you can configure it to be accessible from the outside with no extra steps. In effect you only use the private network for PXE-booting and connecting to the file server. All other I/O is on the other NIC. I don't do this wiht my QEMU CPU servers because the version of QEMU I am using has a bug where it can't PXE-boot with more than one NIC. On my CPU servers I just import /net from my primary fs/cpu/auth server, and to access the CPU server directly I just use aux/trampoline. --=20 Aram H=C4=83v=C4=83rneanu