Chronological Thread 

< Chronological >      < Thread >

---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Freitag, 4. Juli 2003 13:49 schrieb
evma01 AT control.auc.dk:
> Hello Michael (and others)
> I am working with Marjan Bozinovski on a project using rsplib sctplib and
> friends. The project consists of three instances of a server communicating
> in a chain and a client. The client sends requests to one server, and the
> message is passed through the chain to the other end and then back the same
> way. At some random point in the chain the communication stops or gets
> stuck. That is out main problem. We think that it has to do with the
> handling of sockets by the rsplib/socketapi because it is either when
> receiving data or when establishing a connection the error occours. That is
> our biggest problem for the time being.
>
>
> One of the formerly mentioned servers should be registered at an r-serpool
> nameserver as pool element. This does not happen, we have set up the
> nameserver to run with multicast as specified in the README. The PE
> recieves the server announcment but does not recognize it or something. We
> tried to run the rsplib example program on the same machine with the same
> results. I will add output from the example program and output from
> "ifconfig" in the bottom. Our problem could be some simple thing like some
> setup being made in a wrong way. We are really stuck with theese problems
> and cannot see how to get on with our work. So any help would be
> apreciated...
>
> Thanks in advance, regards Erling Matthiesen
>
>
> output from ifconfig:
>
> eth0 Link encap:Ethernet HWaddr 00:30:05:10:1B:95
> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::230:5ff:fe10:1b95/10 Scope:Link
> UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
> RX packets:20 errors:0 dropped:0 overruns:0 frame:0
> TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:932 (932.0 b) TX bytes:4070 (3.9 Kb)
> Interrupt:9 Base address:0x4400 Memory:c9257000-c9257c40
>
> eth1 Link encap:Ethernet HWaddr 00:04:76:27:27:2D
> inet addr:192.168.2.4 Bcast:192.168.2.255 Mask:255.255.255.0
> inet6 addr: fe80::204:76ff:fe27:272d/10 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1768 errors:0 dropped:0 overruns:0 frame:0
> TX packets:699 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:131022 (127.9 Kb) TX bytes:62106 (60.6 Kb)
> Interrupt:9 Base address:0x4800

> Server Announce:
> Last Update = 0.000 [s] ago
> Flags = Dynamic
> Addresses = { 0.0.0.0 } 9999/SCTP

There is a bug in the README file of version 0.3.x. The parameter
"-sctp=0.0.0.0:9999" is wrong. It must be "-sctp=<IP address of your
host>:9999". Using INADDR_ANY (0.0.0.0), your nameserver announces itself to
be reachable at address 0.0.0.0, which is of course wrong.

If you have more than one address, use e.g.:
"-sctp=<IP address 1>:9999,<IP address 2>,<IP address 3>"


A new version with a corrected README file will be on our website soon.


Best regards
- --
=======================================================================
Dipl.-Inform. Thomas Dreibholz

University of Essen, Room ES210
Inst. for Experimental Mathematics Ellernstraße 29
Computer Networking Technology Group D-45326 Essen/Germany
- -----------------------------------------------------------------------
E-Mail:
dreibh AT exp-math.uni-essen.de
Homepage: http://www.exp-math.uni-essen.de/~dreibh
=======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/Ds8t32BbsHYPLWURArfzAJ46UJsHdF1QG653cMpUzZ4G2ydH3ACgn4PO
8vTHeRlgCJDLLk7ISPSee9Y=
=13cr
-----END PGP SIGNATURE-----

---

• [RSPlib-Discusssion] Help with multicast, evma01, 07/04/2003
  • Re: [RSPlib-Discusssion] Help with multicast, Thomas Dreibholz, 07/11/2003

---

Archive powered by MHonArc 2.6.19+.