Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: sgf@cfm.brown.edu (Sam Fulcomer)
Newsgroups: comp.sys.sun
Subject: NIS binding to ypserv on different net...
Keywords: Networks
Message-ID: <1179@brchh104.bnr.ca>
Date: 10 Jan 91 15:50:21 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 11
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 10, Issue 4, message 11
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

I was annoyed enough with the problem to want to share it...

A machine on net A can bind to ypserv on net B if the client's broadcast
address is changed to that of net B. It can then be left or put back,
although if put back to the A-cast the binding may get marked bad if the
ypbind can't communicate with the ypserv (just write a daemon that checks
the binding every few minutes and swaps the broadcast addr for a while if
the binding's bad).

In our case we just leave the broadcast set to B-cast since the machine is
an effective net-B peer except for net-membership.