home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!portal!lll-winken!fnnews.fnal.gov!mp.cs.niu.edu!uxa.ecn.bgu.edu!psuvax1!atlantis.psu.edu!barr
- From: barr@pop.psu.edu (David Barr)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: NIS broadcasts over IP subnets
- Message-ID: <c241Hya0za@atlantis.psu.edu>
- Date: 17 Nov 92 16:07:55 GMT
- References: <1992Nov17.142856.19947@ccsun.strath.ac.uk>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Penn State Population Research Institute
- Lines: 18
-
- 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.
-
- The best (and recommended by Sun) solution is to have an NIS slave on every
- subnet. It is not a good idea in general to configure your router to route
- broadcasts outside of a subnet. (The purpose of a router is to decrease
- traffic, not increase it)
-
- --Dave
-