From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx as a cpu server?
Date: Sun, 1 Feb 2009 16:40:14 -0500 [thread overview]
Message-ID: <9ab217670902011340p3739b0f4r147302a3f3232d69@mail.gmail.com> (raw)
In-Reply-To: <614eaa1fdb126c41fb92fd215356eae8@smgl.fr.eu.org>
2009/2/1 Mathieu <lejatorn@gmail.com>:
>> > As I naively see it, the two main problems are:
>> > 1) to have 9vx running a cpu server kernel instead of a stand alone
>> > terminal one (I don't even know if that's the case actually).
>>
>> i think there would be a little work in getting this going.
>
> Ok, so it's possible then. :)
> I'll see if I can understand the 9vx code and have a go at that.
>
>> > 2) to have the host forwarding whatever packets should go to 9vx.
>>
>> is this enough?
>>
>> http://9fans.net/archive/2008/12/501
>> http://9fans.net/archive/2008/12/505
>
> Hmm I'm not sure, do these modifications imply that the Linux/FreeBSD
> host can "see" 9vx as another host? Hence making it possible to NAT the
> relevant traffic to it?
> If yes, then that's indeed what I'm after, thx.
You add an IP address to your system; with the changes, 9vx creates a
virtual network device. You assign the IP address to the 9vx virtual
network interface and it does the right thing. It isn't NAT, it's
passive traffic listening / injecting. I still have some work to do to
get the tap driver running, but it's been on the back burner.
--dho
> Cheers,
> Mathieu
>
>
>
next prev parent reply other threads:[~2009-02-01 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 18:19 Mathieu
2009-02-01 18:29 ` erik quanstrom
2009-02-01 21:29 ` Mathieu
2009-02-01 21:40 ` Devon H. O'Dell [this message]
2009-02-02 4:27 ` Russ Cox
2009-02-02 16:29 ` Roman V. Shaposhnik
2009-02-02 16:54 ` roger peppe
2009-02-02 17:07 ` ron minnich
2009-02-02 17:10 ` erik quanstrom
2009-02-02 19:11 ` Charles Forsyth
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=9ab217670902011340p3739b0f4r147302a3f3232d69@mail.gmail.com \
--to=devon.odell@gmail.com \
--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).