home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!ukma!darwin.sura.net!sgiblab!sgigate!sgi!rhyolite!vjs
- From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
- Subject: Re: NIS broadcasts over IP subnets
- Message-ID: <sg3chj4@rhyolite.wpd.sgi.com>
- Organization: Silicon Graphics, Inc. Mountain View, CA
- References: <1992Nov17.142856.19947@ccsun.strath.ac.uk> <c241Hya0za@atlantis.psu.edu>
- Date: Tue, 17 Nov 1992 20:22:59 GMT
- Lines: 24
-
- In article <c241Hya0za@atlantis.psu.edu>, barr@pop.psu.edu (David Barr) writes:
- > 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)
-
-
- I think a better way is to use a class-D multicast address and routers
- which forward multicasts.
-
-
- Vernon Schryver, vjs@sgi.com
-