Linux NIS client to Solaris NIS server on another subnet

[Tom Buskey]

On 1/25/06, Paul Lussier <p.lussier at comcast.net> wrote:
>
> Tom Buskey <tom at buskey.name> writes:
>
> > 1.  (*) text/plain          ( ) text/html
> >
> > I've been trying to get this setup and failing.  I'm able to get a
> Solaris
> > (8 and 10) client to work.
> > Linux is FC 4 fwiw.
> >
> > nismaster is xxx.xxx.48.38
> > client is xxx.xxx.54.11
> > There's a router between them and the 54 subnet can't transmit
> broadcasts.
> > ping nismaster works
>
> The 54 subnet can't transmit broadcasts?  Do you mean the router
> between the 48 and the 54 won't transmit a broadcast on one to the
> other?


Yes.  Broadcasts on the 54 subnet won't reach the 48 subnet.  For example I
have a dhcp server on the 54 net because it won't reach the rest of the
network.


> $ /etc/init.d/ypbind start fails
> >
> > So I go manual:
> > $ /usr/sbin/ypbind -ypsetme
> > $ ypset nistmaster
> > $  ypwhich
> > can't yp_bind: Reason: Domain not bound
>
> Yeah, I vaguely remember this problem.  It's a few years since I've
> played with NIS, but I would have expected the linux implementation to
> have matured by now...


You would, but it's good enough, mostly and most people needing more then
linux NIS offers have moved to LDAP, etc.  Such as yourself :-)


Have you tried running ypbind with -debug?  Also, I vaguely remember


I'll try that.

that despite the documentation, you *had* to have a valid /etc/yp.conf


Yep.  ypbind -c also passes.

file, which explicitly stated the server you wanted to bind to.  Which
> sort of defeats the purpose of the -broadcast or -ypset options.  At
> the very least, make sure your yp.conf file has the something like the
> following line in it:
>
>   domain nisdomain broadcast


domain gps server nismaster
Should bind explicity to nismaster from the docs.....


I've always thought the concept of having a yp.conf very foreign
> coming from the Sun world where NIS "just worked", and was actually
> more difficult to *disable* :)


Things have changed in the Sun world too.  Pre solaris 8 wouldn't work in
this scenario but 8 (9) and 10 do.
Heck, the NFS & NIS version 2 book finally covers Solaris NIS.  And NFS v3.
Too bad it doesn't cover Linux, HP-UX, SGI, NFSv4, FreeBSD, etc.  *sigh*.

I kind of like yp.conf.  Instead of /etc/defaultdomain and ypinit -c (with
/var/yp/ypservers). and others scattered about /etc.

Linux NIS feels partly finished.  Like the docs say it should work this way,
but it doesn't.  Hence this question :-(




--
A strong conviction that something must be done is the parent of many bad
measures.
  - Daniel Webster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20060125/ac23294a/attachment.html