On Thu, Nov 09, 2006 at 03:09:39PM +0000, zarrar yousaf wrote: > Hi, Hello Zarrar,
I don't know why your test fails, but just a few things you might want to try out. > I am trying to use IPerf 1.7.0 to send UDP and TCP traffic in my > MIPL2.0.1 test bed. IPerf runs fine as long as the MN is in the home > network. Is there a reason for not using the latest MIPL version 2.0.2? It's easier for us not to go chasing something that might be already fixed in the latest version. > When the MN enters the visit network, the IPerf client terminates > with the follwoing message: > > " Warning: did not recieve ACK for the last datagrams after 10 trials " > > I must mention here that i am sendign and receiving udp packets adn > I certainly dont expect ACKs for the packets. If you look at the iperf code, where that warning originates, it does indeed try to ack your UDP packet. So you are expecting an ack. It seems you could arrive in a situation like this if the write() in PerfSocket_UDP.cpp:167 fails. But there should be a preceeding error message saying "write failed: ..." or something. > Also when i restart the IPerf client once the MN is in the visit > network, the client freezes/hangs. > > following is the IPerf command i issue: > > ON MN: > iperf -u -c 2001:106:2600::2 -V -B 2001:106:1200::2 -i 0.5 -t 3600 > (where 2001:106:2600::2 is the address of the CN) Is there a reason to bind on the client side? Try without -B just to see what happens. Kernel should prefer a home address over other addresses. > Any help will be appreciated. I don't expect this to solve the problem, but at least to give some suggestion what is happening. Also, have you verified that your setup works in the first place? Regards, Antti _______________________________________________ mipl mailing list [email protected] http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
