From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTintsidAgGDinZGI5puFu9lYMlaDvK5oV17PCYZG@mail.gmail.com>
References: <AANLkTimNEg-prinJ0mMTNwQX8tu3AYndLjgGn7hEWfd8@mail.gmail.com>
	<203975f49e91f93a5b4df848ead8e5c2@kw.quanstro.net>
	<AANLkTiknL35zxsXBQC2SXKK9WCIt_qYDiD6cnioOzRFa@mail.gmail.com>
	<e2c05992ac450caf99157d637b639834@kw.quanstro.net>
	<AANLkTintsidAgGDinZGI5puFu9lYMlaDvK5oV17PCYZG@mail.gmail.com>
Date: Wed, 21 Jul 2010 15:01:32 -0700
Message-ID: <AANLkTimk71pSvh9WkatIJjv8vuo-aNiPW1smOceQjgXp@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] auth server with two NICs
Topicbox-Message-UUID: 410a29c0-ead6-11e9-9d60-3106f5b1d025

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?
>