Hi. A formerly fine working installation of us needed some updates after a hardware breakdown, so that I was forced to upgrade from an 2 1/2 year old Debian (testing, Kernel 2.6.9) and OpenSG (new Nvidia-Drivers, new libstdc++ etc. -> new OpenSG) to recent versions (good old apt-get dist-upgrade) with Kernel 2.6.18, libstdc++ 6 , gcc/g++ 4.1 etc. Now, my new hardware works but I've got big troubles with Multicast (as always) setup. As the client pushes a lot of animated vertices to 10 Clients, Streamsock (woking fine) is unfortunately no option here.
First, let me describe the symptoms: No matter if I use the my app or the cluster tutorials, I've got the following problems (Log level set to debug, client and server on the same machine (worked fine formerly), doesn't work with client and server on the different machines either): Client output: INFO: Connect to test1 INFO: send request to:224.245.211.234 INFO: send request to:255.255.255.255 INFO: send request to:224.245.211.234 INFO: send request to:255.255.255.255 INFO: Found at address 192.168.0.200:49826 Server output: INFO: Waiting for request of test1 INFO: wait for request by broadcast INFO: Request for test1 Multicast INFO: Connection bound to 0.0.0.0:49826 INFO: Response Multicast:pear:49826 INFO: Connection accepted pear:49826 After the connection accepted, nothing happens anymore. The client uses 99% of the CPU and waits for ever. Wireshark (formerly etherreal) shows me, that there are no packets on the wire. I have the same problem on my notebook (running Kubuntu edgy with 2.6.17 kernel) On my old setup, I had the following routing table: Ziel Router Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0 The last line (dumping everything to eth0) always seemed always a little bit suspect to me but was necessary to get things to work. So, what am I missing? I tried a lot of different setups (no / different switches, routing everything to lo etc.) but nothing happens. Do I have to activate anything in the kernel? Do I have to set anything in /proc/sys/...? In wireshark, I saw that the (few) packets exchanged had errornous checksums, but modifiying OSGDgramSocket.cpp with setsockopt SO_NO_CHECK didn't changed anything (albeit that the checksum is now 0x00 (not used)). If you have only the slightest idea what the reason could be or you need more infos, please write. This is really, really urgent. Thanks, Dominik ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
