home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!ukma!darwin.sura.net!udel!pervert!louie!tweety.cis.udel.edu!stewart
- From: stewart@tweety.cis.udel.edu (John Stewart)
- Subject: Re: NIS broadcasts over IP subnets
- Message-ID: <1992Nov17.163825.8371@udel.edu>
- Sender: usenet@udel.edu (USENET News Service)
- Nntp-Posting-Host: tweety.cis.udel.edu
- Organization: University of Delaware
- References: <1992Nov17.142856.19947@ccsun.strath.ac.uk>
- Date: Tue, 17 Nov 1992 16:38:25 GMT
- Lines: 24
-
- In article <1992Nov17.142856.19947@ccsun.strath.ac.uk> craa85@ccsun.strath.ac.uk ( D.W.Stevenson) writes:
- >I have a potential problem with NIS in the presence of subnets. Advice would
- >be appreciated.
- >
- >If a NIS client broadcasts to the subnet broadcast address (e.g. 130.159.248.255
- >in the case of 24 bit subnets), a router will not propogate the broadcast onto
- >other subnets on the LAN and hence the client won't be able to bind to a NIS
- >server unless a server is on the same subnet. If however the NIS client
- >broadcasts to the class B broadcast address (130.159.255.255) even when using
- >an 24 bit subnet mask, the router can be configured to forward all subnet
- >broadcasts and there is no problem.
- >
- >Which way does NIS do it?
-
- NIS was not designed so that clients on a LAN which have no NIS
- servers (master or slave) for a given NIS domain could participate
- in that domain. You can use "ypbind" and "ypset" in /etc/rc.local
- to do what you want (and many people, including me, do it), but it
- is a kludge at best. I understand from a "white paper" from Sun
- that NIS+ is supposed to do this better.
-
- Good luck.
-
- /jws
-