Connecting spread daemons with different segment configurations
Timo Korthals <[email protected]> Thu, 29 Jan 2015 11:20:54 +0100
| Newsgroups | gmane.network.spread.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============3129942738094774975==
Content-Type: multipart/alternative;
boundary="------------080703060409090609040005"
This is a multi-part message in MIME format.
--------------080703060409090609040005
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Dear Spread users,
we are using spread daemons for our distributed robot network.
We know already, that each device needs exact the same configuration=20
regarding the segments, otherwise the spread daemons wont connect to=20
each other.
But is there a way to not have the same segment configurations?
So lets assume the following scenario of three participants {1,2,3}.
*1. is a server, which knows the participants 2 and 3*
/spreadOne.conf:/
Spread_Segment 192.168.0.255:4803 {
one 192.168.0.1
}
Spread_Segment 192.168.0.255:4803 {
two 192.168.0.2
}
Spread_Segment 192.168.0.255:4803 {
three 192.168.0.3
}
*2. and 3. are just clients, which are allowed to talk with the server,=20
but not with each other*
/spreadTwo.conf:/
Spread_Segment 192.168.0.255:4803 {
one 192.168.0.1
}
Spread_Segment 192.168.0.255:4803 {
two 192.168.0.2
}
/spreadThree.conf:/
Spread_Segment 192.168.0.255:4803 {
one 192.168.0.1
}
Spread_Segment 192.168.0.255:4803 {
three 192.168.0.3
}
Obviously this does not work with spread, am I right?
But if so, how can I make it work?
Is spread just comparing the hashes of the configs, and refusing=20
connections, if hashes mismatch?
What happens if I remove the checks regarding the configuration check?
Has anyone done this before?
Greetings,
Timo
--=20
Timo Korthals, M.Sc.
Universit=C3=A4t Bielefeld
AG Kognitronik & Sensorik
Exzellenzcluster Cognitive Interaction Technology (CITEC)
Inspiration 1 (Zehlendorfer Damm 199)
33619 Bielefeld - Germany
Office : 3.037
Phone : +49 521 106-67368
eMail : [email protected]
Internet: http://www.ks.cit-ec.uni-bielefeld.de/
--------------080703060409090609040005
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf=
-8">
</head>
<body text=3D"#000000" bgcolor=3D"#FFFFFF">
Dear Spread users,<br>
<br>
we are using spread daemons for our distributed robot network.<br>
We know already, that each device needs exact the same configuration
regarding the segments, otherwise the spread daemons wont connect to
each other.<br>
But is there a way to not have the same segment configurations?<br>
So lets assume the following scenario of three participants {1,2,3}.<=
br>
<br>
<b>1. is a server, which knows the participants 2 and 3</b><br>
<i>spreadOne.conf:</i><br>
Spread_Segment=C2=A0 192.168.0.255:4803 {<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 one =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.1<br>
}<br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 two =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.2<br>
}<br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 three =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.3<br>
}<br>
<br>
<b>2. and 3. are just clients, which are allowed to talk with the
server, but not with each other</b><br>
<i>spreadTwo.conf:</i><br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 one =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.1<br>
}<br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 two =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.2<br>
}<br>
<br>
<i>spreadThree.conf:</i><br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 one =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.1<br>
}<br>
Spread_Segment=C2=A0 192.168.0.255:4803 {=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 three =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.0.3<br>
}<br>
<br>
<br>
Obviously this does not work with spread, am I right?<br>
But if so, how can I make it work?<br>
Is spread just comparing the hashes of the configs, and refusing
connections, if hashes mismatch?<br>
What happens if I remove the checks regarding the configuration
check?<br>
Has anyone done this before?<br>
<br>
Greetings,<br>
Timo<br>
<br>
<pre class=3D"moz-signature" cols=3D"72">--=20
Timo Korthals, M.Sc.
Universit=C3=A4t Bielefeld =20
AG Kognitronik & Sensorik
Exzellenzcluster Cognitive Interaction Technology (CITEC)
Inspiration 1 (Zehlendorfer Damm 199)
33619 Bielefeld - Germany
Office : 3.037
Phone : +49 521 106-67368
eMail : <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:tkorthals@=
cit-ec.uni-bielefeld.de">[email protected]</a>
Internet: <a class=3D"moz-txt-link-freetext" href=3D"http://www.ks.cit-ec=
.uni-bielefeld.de/">http://www.ks.cit-ec.uni-bielefeld.de/</a></pre>
</body>
</html>
--------------080703060409090609040005--
--===============3129942738094774975==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users
--===============3129942738094774975==--