---------- Forwarded message ----------
From: Nick Wagner <[EMAIL PROTECTED]>
Date: Jul 26, 2007 11:24 AM
Subject: Re: [Openslp-users] DA configuration problem - more details
To: rmoser <[EMAIL PROTECTED]>
Cc: Johannes Gutleber <[EMAIL PROTECTED]>
On the slpd attempting to use the remote DA, try setting passiveDA detection
to true and active to false. The say slpd currently works is that it
attempts to query the configured DA for the list of DAs it knows about. The
DA returns itself, but if passive is turned off the reply is ignored by the
local slpd.
Let me know if this does what you need without the patch.
On 7/26/07, Nick Wagner <[EMAIL PROTECTED]> wrote:
Setting up a test with my understanding does show the problem -- I'll take
a quick look at it.
--Nick
On 7/26/07, Nick Wagner <[EMAIL PROTECTED] > wrote:
>
> Good spot on the extra ;, I don't often build with security enabled.
> You're patch seems to be duplicating what SLPDKnownDAEcho is supposed to
> do. Is the configured DA not being added correctly to G_slpdKnownDAs?
>
> Just to be certain I understand the setup:
>
> 1) you have a remote machine running slpd configured to be a DA.
> 2) you have a local machine running slpd configured to be an SA with the
> remote DA statically configured. You also have a "device" on the local
> machine that you register with the local slpd.
> 3) you are attempting to not use multicast/broadcast to discover other
> DAs. (this doesn't disable multicast completely, as the protocol
> implementation uses mcast as a fallback for queries if the DA doesn't
> answer).
> 3) the local slpd does not appear to be updating the statically
> configured DA.
>
> On 7/26/07, rmoser <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > The problem we encountered occurs when we have a DA running in one
> > subnet and one or multiple SAs running in another one. As the routers do not
> > forward broadcast and multicast messages, the (multicast) registration
> > messages are lost between the SA and the DA.
> >
> > To configure our system, we want to deactivate multicast and only use
> > unicast. Therefore we configured one slp as a DA and set DAAddresses on all
> > other Agents. According to documentation, we can set the following
> > variables:
> > net.slp.ActiveDADetection = false
> > net.slp.PassiveDADetection = false
> >
> > Using this configuration the static configured DA is not found. To be
> > able to find it, we had to set ActiveDADetection=false and
> > DAActiveDiscoveryInterval=1. In this case the SA still sends multicast
> > messages! We expected, however, that only unicast communication would be
> > used.
> >
> > To additionally send a unicast package to the found DAs we echo each
> > registration/deregistration package from the SA to the DA using unicast. A
> > patch against the svn from today is attached. This patch solves our problem
> > but is most likely not the proper patch. Please verify it and let us know
> > your opinion.
> >
> > Currently there seems to be no option to deactivate multicast and
> > broadcast and use unicast only when using a static configured DA.
> >
> > In slpd_process.c line 1091, there seems to be an additional semicolon
> > at the end of the if statement.
> > "if (errorcode==0);"
> >
> > Regards,
> > Roland and Johannes
> >
> > On 7/26/07 8:45 AM, "Johannes Gutleber" < [EMAIL PROTECTED]>
> > wrote:
> >
> > Hi Nick,
> >
> > On Jul 25, 2007, at 20:15 , Nick Wagner wrote:
> >
> > Have you tried sniffing the connection? Also, I'm not sure where the
> > sf1512548 came from. If you "svn info" in the trunk directory, what is the
> > Revision number?
> >
> >
> > Well spotted: I am sorry this is our internal tracking number. I
> > looked it up and saw that the version is from 2006-06-27. Unfortunately I do
> > not know
> > the svn information, since we checked it out and imported it "by
> > value" into our own development tree in order to be able to fix problems
> > easier.
> > If you think there was a problem with DA configuration by that time,
> > please let me know which version to grab from svn.
> > Thanks
> > Johannes
> > .
> >
> >
> >
> >
> > --Nick
> >
> >
> >
> > On 7/25/07, *Johannes Gutleber* < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]> >
> > wrote:
> >
> > Dear experts,
> >
> > in addition to my previous e-mail concerning the DA configuration
> > problem, I'd like to provide more information:
> >
> > I am working with SLP version svn trunk sf1512548
> >
> > The DA has the following configuration in slp.conf:
> >
> > net.slp.DAAddresses = 10.176.37.214
<http://10.176.37.214/><http://10.176.37.214/>
> > net.slp.isDA = true
> > net.slp.interfaces = 10.176.37.214
<http://10.176.37.214/><http://10.176.37.214/>
> > net.slp.traceDATraffic = true
> >
> > A remote slpd daemon attempting to use the DA for publishing and
> > finding services has the following in its slp.conf :
> >
> > net.slp.DAAddresses = 10.176.37.214
<http://10.176.37.214/><http://10.176.37.214/>
> > net.slp.passiveDADetection = false
> > net.slp.activeDADetection = true
> > net.slp.traceDATraffic = true
> >
> >
> > I tried already various combinations of addresses and DA
> > configuration settings, but didn't succeed.
> > It seems that somehow a slpd daemon that wishes to connect to a
> > statically configured DA does either
> > not succeed sendind a request (the trace in the DA remains empty, no
> > messages incoming) or does not
> > send the request properly.
> >
> > The platform I am working on is Linux, kernel 2.6:
> >
> > uname -a
> > Linux srv-C2D06-20 2.6.9-55.EL.cernsmp #1 SMP Thu May 10 18:16:29
> > CEST 2007 i686 i686 i386 GNU/Linux
> > cat /etc/redhat-release
> > Scientific Linux CERN SLC release 4.4 (Beryllium)
> >
> > gcc 3.4.6
> >
> > Kind regards
> > Johannes
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a
> > browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
<http://get.splunk.com/>
> >
> > _______________________________________________
> > Openslp-users mailing list
> > Openslp-users@lists.sourceforge.net
<mailto:Openslp-users@lists.sourceforge.net><Openslp-users@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/openslp-users
<https://lists.sourceforge.net/lists/listinfo/openslp-users>
> >
> >
> >
> >
> >
> >
> >
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openslp-users mailing list
Openslp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-users
