Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#57 big-endian udp server apparently sends bad reports

open
nobody
None
5
2013-09-13
2012-09-18
Greg Troxel
No

With iperf 2.0.5, a netbsd-5/i386 client sending udp to a netbsd-4/sparc server resulted in an core dump on the sparc, and the client printing:
{{{
------------------------------------------------------------
Client connecting to [SERVER-FQDN], UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 9.00 KByte (default)
------------------------------------------------------------
[ 5] local [CLIENT] port 52655 connected with [SERVER] port 5001
read failed: Connection refused
[ 5] WARNING: did not receive ack of last datagram after 1 tries.
[ ID] Interval Transfer Bandwidth
[ 5] 0.0-10.0 sec 1812476889390 bits 8305442605072999647184515680952s/sec
[ 5] Sent 892 datagrams
}}}

The problem has also been observed when both client and server are netbsd-6/evbppc. It seems likely there is an endian issue; all is well when both ends are i386.

Discussion

  • m.
    m.
    2013-09-13

    I see similar behavior when sending from mipsel client to amd64 server (amd64 to amd64 is fine). This is only when trying to limit bandwidth via -b:
    $ /home/root/iperf -c 192.168.100.200 -p 5002 -b 20M
    WARNING: option -b implies udp testing


    Client connecting to 192.168.100.200, UDP port 5002
    Sending 1470 byte datagrams
    UDP buffer size: 101 KByte (default)


    [ 3] local 192.168.100.44 port 1025 connected with 192.168.100.200 port 5002
    [ ID] Interval Transfer Bandwidth
    [ 3] 0.0-10.0 sec 60.0 GBytes 51.6 Gbits/sec
    [ 3] Sent 17007 datagrams