On Fri, 20 Jul 2007 09:19:15 +0200 "Reither Robert" <[EMAIL PROTECTED]> wrote:
> > Hi Francois , > > i can spare some time now, so i ask: > Would it help, if i code/send u a tool to simulate your multicast packet > scenario ? > Buts its possible for me to reproduce the problem with e.g. nc -u 224.1.1.1 > 10500 <dummy_file (does show me the same bad behaviour). > Or can i help in another way ? iperf also works as simple multicast test. ----------------------------------------------- http://dast.nlanr.net/Projects/Iperf/ Running the multicast server and client Use the -B option while starting the server to bind it to a multicast address. E.g. :-iperf -s -u -B 224.0.55.55 -i 1. This will have the Iperf server listening for datagrams (-u) from the address 224.0.55.55(-B 224.0.55.55), with a periodic reporting interval of 1s (-i 1). Now, start a client sending packets to this multicast address, with a TTL depending on your Network Topology (if you are unsure, use a high TTL like 64 or higher). E.g. : iperf -c 224.0.55.55 -u -T 32 -t 10 -i 1. This will have a UDP client (-u) connected to the multicast address 224.0.55.55(-c 224.0.55.55), with a TTL of 32 (-T 32), sending data for 10 seconds (-t 10), with a periodic reporting interval of 1s (-i 1). Start multiple clients as explained above, sending data to the same multicast server. (If you have multiple servers listening on the multicast address, each of the servers will be getting the data) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
