Mark Brown wrote:
On Mon, Sep 26, 2005 at 07:43:07PM +0200, Bas van der Vlies wrote:
Could you try configuring hosts.{allow,deny} for portmap to prevent
access to portmap via the infiniband network (if that is possible).
Doing something like:
portmap: 192.168.
in hosts.allow and
pormap: ALL
in hosts.deny on the servers should I think do the trick (again,
untested so this may not work).
Thanks for all the info. With this the client messages are gone. So your
idea about the portmap daemon is true ;-) Is this an feature or a bug in
the pormap daemon? The portmap daemon hsa an option to listen to an
interface but you can only list one interface ;-(
I now only get the ypserv: refused connect from 10.0.17.130 this i can
not prevent because this is a NIS-server and in the ypbind.conf:
ypserver localhost
Is this also related to portmap or does ypbind secretly an broadcast
what triggers the same bug/feature as above.
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]
