Mark,
I have switched from ypserv.securenets to ypserv.conf and the problem
still exists ;-( The ypbind broadcast clients gets once in an while the
wrong nis server name and uses an interface that is not allowed in the
ypserv.conf, eg:
gb-r7n15 (192.168.17.130) and ib-r7n15 (10.0.17.130)
# New SARA syntax from Debian NIS maintainer, BvdV thanks
#
127.0.0.1 : * : * : none
192.168.16.0/255.255.252.0 : * : * : none
# Deny the rest
#
* : * : * : deny
--- client broadcast, yp.conf:
domain elsacafe broadcast
On gb-r8n1 (192.168.17.135) en ib-r8n1 (10.0.17.135)
# /etc/init.d/nis restart
# ypwhich
ib-r7n15 <------------------------- This not allowed!!!!!!
Sylog gb-r7n15:
Sep 22 14:40:01 gb-r7n15 ypserv[23579]: refused connect from
10.0.17.135:997 to procedure ypproc_all (elsacafe,group.byname;-1)
It is still an bug and maybe it is correlated with the other one. Or can
nis not handle two interfaces with broadcast mode?
Regards
--
--
********************************************************************
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Services phone: +31 20 592 8012 *
* Kruislaan 415 fax: +31 20 6683167 *
* 1098 SJ Amsterdam *
* *
********************************************************************
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
