Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!uunet!brunix!sgf
From: sgf@cfm.brown.edu (Sam Fulcomer)
Newsgroups: comp.sys.sgi
Subject: Re: yp problem
Message-ID: <75502@brunix.UUCP>
Date: 13 May 91 16:15:25 GMT
Article-I.D.: brunix.75502
References: <9105120711.AA01176@> <103360@sgi.sgi.com>
Sender: news@brunix.UUCP
Organization: Brown University Center for Fluid Mechanics
Lines: 27

In article <103360@sgi.sgi.com> vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
>In article <9105120711.AA01176@>, brad@lsr-vax.UUCP (Brad J Zoltick) writes:
>> 
>> Has anyone had difficulty getting a SGI yp client
>> to work with a Sun yp master when a router is involved
>> on the subnet?  
>
>If the router is between the client and the server, then you don't have much
>hope, at least until the next release.  This is because NIS (gotta keep
>those lawyers and PTT's happy) uses UDP/IP broadcasts for ypbind on

Eh?, I haven't found this to be a problem. Let's assume subnets "a.b.c" and
"1.2.3" and say a machine on "a.b.c" wants to ypbind through a router to
a server on "1.2.3". All the client needs to do is change its broadcast address
to "1.2.3.255" (assuming the server's using 255) before the ypbind. 

Since all our remote NIS clients don't have much association with other machines
on their subnet I just leave the b-cast set to our local subnet. That avoids the
complication of the client losing a binding and hanging if one of the intervening 
routers goes down.


-- 
_/**/Sam_Fulcomer	sgf@cfm.brown.edu	What, me panic: uba crazy

Associate Director for Computing Facilities and Scientific Visualization
Brown University Center for Fluid Mechanics, Turbulence and Computation