This infodoc explains the situation where a NIS server is installed as
a router with two or more ethernet interfaces connected to it.
 
Assume the following setup:
 
                           |
                           S3
                           |
                           |
                           C
                        --------
                        |      |
   ---------S1---------A|  R   |B-----S2------------
                        |      |
                        --------
             
In the above figure, R is the Router with three interfaces (A, B, C)
connecting subnets S1, S2 & S3.
 
Normally, you would need three NIS servers (one per each subnet),
since YPBIND does not broadcast through Router R. Configuring Router R
as a NIS server (i.e. NIS master) obviates the need for two more NIS
servers, since YPSERV listens-in on all the interfaces (A, B & C) for
broadcasts from YPBIND. Thus, NIS server R (which also is the router)
can service NIS requests from any client on subnets S1, S2 and S3.
                                             
The only problem in the above setup are that the machine R becomes the
critical point of failure, and the fact that it must be powerful
enough to serve as both router and NIS server effectively.

SunWeb Home SunWeb Search SunSolve Home Simple Search

Sun Proprietary/Confidential: Internal Use Only