nevermind, it's the network... or hardware...
I tried just the very basic setup at the top of
http://www.9grid.fr/www.9grid.fr/wiki/plan9/Drawterm_to_your_terminal/
and I get the same poor performance. network
sux!
On Thu, Jul 22, 2010 at 10:55 AM, Akshat Kumar
wrote:
> On Thu, Jul 22, 2010 at
On Thu, Jul 22, 2010 at 10:30 AM, erik quanstrom wrote:
> a bad network?
I thought so at first, but if instead of using separate /net and /net.alt
mountpoints for the two networks, I simply, as I said before,
bind -b '#l1' /net
bind -b '#I1' /net
and start auth service, etc., afterwards (so tha
On Thu Jul 22 13:26:51 EDT 2010, aku...@mail.nanosouffle.net wrote:
> if I have an 'internal' stack and interface bound to
> /net.alt and an 'external stack' and interface bound
> to /net, I get quite a lot of packet loss when trying
> to ping the computer from another computer on the
> external ne
if I have an 'internal' stack and interface bound to
/net.alt and an 'external stack' and interface bound
to /net, I get quite a lot of packet loss when trying
to ping the computer from another computer on the
external network... even drawterm is much more
lagging. Any ideas on what could be the ca
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)
l
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..
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?
On Wed Jul 21 12:13:20 EDT 2010, aku...@mail.nanosouffle.net wrote:
> I put a bind in /rc/bin/cpurc.local,
> but why the need to also put one
> in /lib/namespace.$sysname?
because /lib/namespace is used by cpu to
construct a namespace from scratch.
cpu does not use the namespace of the
process gro
oxen# cat /net/ndb
ip=192.168.100.2 ipmask=/120 ipgw=192.168.100.1
the IP for the public network isn't even
shown here...
I think the information in /net/ndb is
directly from
bootargs=il -g 192.168.100.1 ether /net/ether1 192.168.100.2 255.255.255.0
in plan9.ini
I put a bind in /rc/bin/cpurc.local,
but why the need to also put one
in /lib/namespace.$sysname?
On Wed, Jul 21, 2010 at 5:38 AM, erik quanstrom wrote:
>> now, I have one concern and one problem -
>> the concern: only ether0 is bound into /net,
>> ether1 doesn't show up in there.
>
> you need to
also, I should add that I cannot ping outside of the
local network, on the card attached to the public
network, even if I specify IP. so... there's some
problem in the setup here, it seems.
On Wed, Jul 21, 2010 at 12:58 AM, Akshat Kumar
wrote:
> I have an auth server with two cards,
> ether0 and
> now, I have one concern and one problem -
> the concern: only ether0 is bound into /net,
> ether1 doesn't show up in there.
you need to add it to /lib/namespace.$node.
you also need to do the bind by hand in cpurc.
- erik
I have an auth server with two cards,
ether0 and ether1; it's connected to
an fs server on ether1 and a public
network on ether0 - it has to get root
from the fs server:
root is from il -g 192.168.100.1 ether /net/ether1 192.168.100.2 255.255.255.0
in /cfg/$sys/cpurc, I have the following:
ip/ip
13 matches
Mail list logo
