9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] auth server with two NICs
Date: Wed, 21 Jul 2010 15:01:32 -0700	[thread overview]
Message-ID: <AANLkTimk71pSvh9WkatIJjv8vuo-aNiPW1smOceQjgXp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTintsidAgGDinZGI5puFu9lYMlaDvK5oV17PCYZG@mail.gmail.com>

the real problem I'm having is that in the process
of getting its root fs, the auth server associates
#I with #l; I would like for it to associate #I1 with
#l instead. If I switch ether0 and ether1 around,
it will associate #I with #l1, but in that case, I
would like #I1 to be associated with #l1... so
this problem persists no matter what. Any
setup suggestions? how do people usually
handle multiple networks on multiple interfaces?

with the current setup, I'd have to start all my
listeners on /net.alt, where #I1 is bound, but
that seems messier than just fixing one thing.


On Wed, Jul 21, 2010 at 2:50 PM, Akshat Kumar
<akumar@mail.nanosouffle.net> wrote:
> the following bootargs line:
>
> bootargs=il -x /net.alt -g 192.168.100.1 ether /net.alt/ether0
> 192.168.100.2 255.255.255.0
>
> gives the following startup error:
>
> boot: bind #I: %r
> : '/net/net.alt': does not exist
>
> what's the proper way to bind the interface from which I get root,
> into /net.alt?
>



  reply	other threads:[~2010-07-21 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  7:58 Akshat Kumar
2010-07-21 12:38 ` erik quanstrom
2010-07-21 16:12   ` Akshat Kumar
2010-07-21 16:24     ` Akshat Kumar
2010-07-21 17:31     ` erik quanstrom
2010-07-21 21:50       ` Akshat Kumar
2010-07-21 22:01         ` Akshat Kumar [this message]
2010-07-21 23:38           ` Akshat Kumar
2010-07-22 17:25             ` Akshat Kumar
2010-07-22 17:30               ` erik quanstrom
2010-07-22 17:55                 ` Akshat Kumar
2010-07-22 20:15                   ` Akshat Kumar
2010-07-21 16:03 ` Akshat Kumar

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=AANLkTimk71pSvh9WkatIJjv8vuo-aNiPW1smOceQjgXp@mail.gmail.com \
    --to=akumar@mail.nanosouffle.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).