9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fernan Bolando <fernanbolando@mailc.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ape sockets and plan9
Date: Tue, 28 Dec 2010 21:23:12 +0800	[thread overview]
Message-ID: <AANLkTinT_t5zAg_M1S6SNOg-Bf_QXvYEJEkLFYogVOVi@mail.gmail.com> (raw)
In-Reply-To: <20101225194105.4D5425B42@mail.bitblocks.com>

On Sun, Dec 26, 2010 at 3:41 AM, Bakul Shah <bakul+plan9@bitblocks.com> wrote:
> On Sat, 25 Dec 2010 17:04:01 GMT "Steve Simon" <steve@quintile.net>  wrote:
>> 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.  This 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?



  reply	other threads:[~2010-12-28 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-25  5:06 Fernan Bolando
2010-12-25 17:04 ` Steve Simon
2010-12-25 19:41   ` Bakul Shah
2010-12-28 13:23     ` Fernan Bolando [this message]
2010-12-28 16:34       ` erik quanstrom
2010-12-28 17:41         ` Devon H. O'Dell
2010-12-28 18:39           ` Bakul Shah
2010-12-28 18:50             ` erik quanstrom
2010-12-28 19:45               ` Bakul Shah
2010-12-29  4:02               ` ron minnich
2011-01-01  1:36                 ` Fernan Bolando
2011-01-01 14:59                   ` erik quanstrom
2011-01-01 15:28                   ` ron minnich

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=AANLkTinT_t5zAg_M1S6SNOg-Bf_QXvYEJEkLFYogVOVi@mail.gmail.com \
    --to=fernanbolando@mailc.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).