I ended up doing: bind -b '#l1' /net bind -b '#I1' /net
so that the public network is what's used by default... but in plan9.ini, I have: fs=192.168.100.1 auth=192.168.100.2 where 192.168.100.2 is the IP of the CPU/Auth server on the internal network, so whenever anything (say, auth/factotum) looks for $auth, it can't connect to 192.168.100.2... is there any way to setup this multi-network multi-stack crap, so it isn't so messy?? On Wed, Jul 21, 2010 at 3:01 PM, Akshat Kumar <[email protected]> wrote: > 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 > <[email protected]> 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? >> >
