I learned something today. There are times when netperf will fall back to not
using the address you specified, or --local-bind is not working right for
netperf. I have multiple ipv6 addresses... and in this case, I wanted to go
back and forth between testing an ipv6 tunnel and ipv6 native.
flent -6 --local-bind 2600:3c01:e001:9301::2 -H flent-fremont.bufferbloat.net
-t wireguard_really_v6 rrul
netperf -L 2600:3c01:e001:9301::2 -H wherever
does the same thing. Negotiates the control connection over the first, but
falls back to the native one. I was initially jumping for joy at wireguard
"getting it right"... but....
d 3242 0.0 0.0 24556 2500 pts/27 S+ 09:23 0:00
/usr/local/bin/netperf -P 0 -v 0 -D -0.20 -6 -Y CS5 CS5 -H
flent-fremont.bufferbloat.net -p 12865 -t TCP_STREAM -l 60 -F /dev/urandom -f m
-L 2600:3c01:e001:9301::1 -- -L 2600:3c01:e001:9301::1 -H
flent-fremont.bufferbloat.net -k
THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD
I guess a sanity check would be nice that checked that the address you used was
the one that was used.... short of a packet cap and
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/155
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
