From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20101225194105.4D5425B42@mail.bitblocks.com> References: <20101225194105.4D5425B42@mail.bitblocks.com> Date: Tue, 28 Dec 2010 21:23:12 +0800 Message-ID: From: Fernan Bolando To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] ape sockets and plan9 Topicbox-Message-UUID: 8e70e74e-ead6-11e9-9d60-3106f5b1d025 On Sun, Dec 26, 2010 at 3:41 AM, Bakul Shah wro= te: > On Sat, 25 Dec 2010 17:04:01 GMT "Steve Simon" =A0wr= ote: >> I think this is an artifact of 9vx (not 100% sure though), > > Indeed. Programs under 9vx can make outgoing connections but > can't accept incoming ones because it doesn't really create a > virtual machine -- 9vx makes the connections on behalf of the > program. IIRC there was some additional code to add a proper > ethernet device (via tap or pcap filtering) but I've never > played with it. =A0This program works under p9/qemu because > qemu creates a proper VM (I then bridge its tap device with > the underlying machine's phys ethernet). > >> try running 9fx as root on your unix box - though that would more >> likely solve problems if the port number was < 1024. > > Yes. Here it is a different cause. > > ape sockets should just work under a real plan9 cpu server?