From mboxrd@z Thu Jan  1 00:00:00 1970
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Message-ID: <Pine.LNX.4.44.0304151241440.1417-100000@maxroach.lanl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [9fans] cpu server to vmware auth server ... so close ....
Date: Tue, 15 Apr 2003 12:47:36 -0600
Topicbox-Message-UUID: 902d91b4-eacb-11e9-9e20-41e7f4b1d025


First, I'm using the linux dhcpd. The hardware is on 10.0.4.x net on eth0,
vmnet8 is 172.16.189.x.

The auth server is vmware host 172.16.189.132. The cpu server needs to be
172.16.189.133.

- route add 172.16.189.133 dev eth
  set up the route
- in dhdpd.conf on linux, set up a shared-network 'net', containing
  subnets 172.16.189.x and serving 172.16.189.133, and subnets
  10.0.4.1. This allows dhcpd on linux to server 172.16.189.x addresses
  on eth0.
- arp -s 172.16.189.133 <ethernet address of CPU server)
  This is needed as at some point dhcpd on linux ARPs the cpu server
  and 9load doesn't respond to arps. Interesting ...

at this point, the cpu server comes up, downloads a plan 9 kernel, and the
kernel comes up on the cpu server!

In fact all works well until ....

the cpu server arps the auth server. I can't get the arp from the cpu
server at .133 to be satisfied. I tried this:
arp -s -i eth0 172.16.189.132 <ethernet address of auth server>
but no dice.

Any clever ideas out there?

ron
p.s. on other option is to leave the cpu server with a 10. address and
hand-add a route into the auth server for that address. Anybody done hand
route stuff on Plan 9?

ron