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
On Tue, Sep 27, 2005 at 11:40:35AM +0200, Bas van der Vlies wrote:
Is this also related to portmap or does ypbind secretly an broadcast
what triggers the same bug/feature as above.
Hrm. It should jump immediately to trying to access the specified
server directly unless something goes wrong
Mark Brown wrote:
On Fri, Sep 23, 2005 at 09:04:19AM +0200, Bas van der Vlies wrote:
After reading your mail i have now configured both ypserv files: (see
attachments)
OK, I'm stumped. Your securenets configuration looks like it will do
what you're looking for and the ypserv logs you
On Mon, Sep 26, 2005 at 07:43:07PM +0200, Bas van der Vlies wrote:
After an day of debugging and restarting some servers. I have a strace
of binding to the wrong server. Hopefully t is enough.
Right, this is great.
sendto(7, %$e\202\0\0\0\0\0\0\0\2\0\1\206\244\0\0\0\2\0\0\0\1\0\0..., 52,
On Fri, Sep 23, 2005 at 09:04:19AM +0200, Bas van der Vlies wrote:
After reading your mail i have now configured both ypserv files: (see
attachments)
OK, I'm stumped. Your securenets configuration looks like it will do
what you're looking for and the ypserv logs you provided in the other
Mark Brown wrote:
On Thu, Sep 22, 2005 at 02:49:10PM +0200, Bas van der Vlies wrote:
It is still an bug and maybe it is correlated with the other one. Or can
nis not handle two interfaces with broadcast mode?
Could you please describe your entire current configuration, including
the
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)
On Thu, Sep 22, 2005 at 11:06:32AM +0200, Bas van der Vlies wrote:
Thanks a lot it is an bit confusing that there are two config files
where we can specify access rules. In one config it works as desired an
in the other not. Will the ypserv.securenets file be obsoleted in the
future?
They
On Thu, Sep 22, 2005 at 02:49:10PM +0200, Bas van der Vlies wrote:
It is still an bug and maybe it is correlated with the other one. Or can
nis not handle two interfaces with broadcast mode?
Could you please describe your entire current configuration, including
the ypserv.conf and
Debian Bug Tracking System wrote:
On Wed, Sep 21, 2005 at 02:53:54PM +0200, root wrote:
On our NIS servers we only allow binding to eth0 interface, ypserv.conf:
# Always allow access for localhost
255.0.0.0 127.0.0.0
255.255.252.0 192.168.16.0 (eth0)
That's not the documented
Debian Bug Tracking System wrote:
On our NIS servers we only allow binding to eth0 interface, ypserv.conf:
# Always allow access for localhost
255.0.0.0 127.0.0.0
255.255.252.0 192.168.16.0 (eth0)
That's not the documented format for ypserv.conf. It should say
something more
11 matches
Mail list logo
