*BSD News Article 82127


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!hunter.premier.net!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!news.msfc.nasa.gov!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul
From: wpaul@ctr.columbia.edu (Bill Paul)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Bind YP server on other subnet???
Date: 1 Nov 1996 16:18:59 GMT
Organization: Columbia University Center for Telecommunications Research
Lines: 63
Message-ID: <55d7tj$hhb@sol.ctr.columbia.edu>
References: <55cdm7$ett@ccnews.ncku.edu.tw>
NNTP-Posting-Host: startide.ctr.columbia.edu
X-Newsreader: TIN [version 1.2 PL2]

Daring to challenge the will of the almighty Leviam00se, Chung-Kie Tung
 (tung@garfield.ee.ncku.edu.tw) had the courage to say:

: [ Article crossposted from comp.sys.sun.admin ]
: [ Author was Chung-Kie Tung ]
: [ Posted on 1 Nov 1996 08:48:13 GMT ]

: Hi...

: Recently I started to install 8 BSD machines as yp client to a 
: sparc running sun OS 4.1.3.(A0)

: One(A1) of these BSDs is on the same subnet as the yp server, the others 
: is not(B1, B2....). Now the problem is clients on different subnet could 
: not bind to the yp server

: I have enable -tpset option in ypbind, but it always return errors when
: running "ypset"...:(

And naturally these error messages are top secret so you're not going to
share them with us.

- What error messages did you see? Exactly? Don't say: "oh, I forgot" or
  "oh, it was something like ..." Write them down if you have to, but quote
  them verbatim as they appeared on your screen. I hate it when people come
  to me and say "I tried this but I got an error" without telling me what
  the error was.

- What version of FreeBSD are you using? (It would help to know this, though
  it should work with anything from 2.0.5 and up.)

Without knowing exactly what error you got, it's hard for me to say what
the problem is. In any case, there are two ways for setting up NIS across
subnets:

- Start ypbind with the -ypsetme option and use ypset to force a binding
  to the desired server. The problem with this approach is that if for some
  reason the server crashes or becomes unreachable, ypbind will invalidate
  the binding and broadcast in search of another server. But since the server
  is unable to hear ypbind's broadcasts, it will never respond and the
  client will be stuck without a binding until someone does a ypset again.
  (In other words, if the clients lose their bindings, they'll never be
  able to rebind without help.)

- Configure at least one machine on the remote subnet as an NIS slave server.
  When maps are updated on the master, they will be pushed to the slave
  server via a direct TCP link, so there will be no problem with broadcasts
  getting lost between the subnets. The clients on the remote subnet will
  then be able to bind to the NIS slave server instead of the NIS master.

  If you are running FreeBSD 2.1.0 or later, you should be able to configure
  one of the FreeBSD machines as a slave server.

-Bill

--
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
 "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you."
=============================================================================