What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
mismatch in manual routing flags: mc-rx-if <--> rx_mc_if
What version of the product are you using? On what operating system?
Please provide any additional information below.
Usage: sockperf server [options] [args]...
sockperf server
sockperf server [-i ip] [-p port] [--rx_mc_if ip] [--tx_mc_if ip] same as udp_lat
sockperf server -f file [-F s/p/e] [--rx_mc_if ip] [--tx_mc_if ip]
Options:
-h,-? --help,--usage -Show the help message and exit.
--tcp -Use TCP protocol (default UDP).
-i --ip -Listen on/send to ip <ip>.
-p --port -Listen on/connect to port <port> (default 11111).
-f --file -Tread multiple ip+port combinations from file <file> (server uses select).
-F --iomux-type -Type of multiple file descriptors handle [s|select|p|poll|e|epoll](default select).
--timeout -Set select/poll/epoll timeout to <msec>, -1 for infinite (default is 10 msec).
-a --activity -Measure activity by printing a '.' for the last <N> packets processed.
-A --Activity -Measure activity by printing the duration for last <N> packets processed.
--tcp-avoid-nodelay -tcp-nodelay uses for delivering TCP Messages Immediately (default ON).
--mc-rx-if -<ip> address of interface on which to receive mulitcast packets (can be other then route table).
--mc-tx-if -<ip> address of interface on which to transmit mulitcast packets (can be other then route table).
--mc-loopback-enable -Enables mc loopback (default disabled).
--mc-ttl -Limit the lifetime of the packet (default 2).
Original issue reported on code.google.com by men...@gmail.com on 26 May 2011 at 12:26
Original issue reported on code.google.com by
men...@gmail.com
on 26 May 2011 at 12:26