9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu server to vmware auth server ... so close ....
Date: Tue, 15 Apr 2003 12:47:36 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0304151241440.1417-100000@maxroach.lanl.gov> (raw)


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



             reply	other threads:[~2003-04-15 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 18:47 ron minnich [this message]
2003-04-15 19:53 ` rsc
2003-04-15 20:33   ` ron minnich
2003-04-15 21:23     ` rsc

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=Pine.LNX.4.44.0304151241440.1417-100000@maxroach.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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).