Hi All,
It looks like iperf2 could use some improvements with respect to v6
addressing. I'm considering the following:
*The proposal is to restrict to v6 addresses when -V is set and allow for
link local per the hints as well as support <remote v6addr>%<name> for
local device binding*. The user setting -V would get an error if there are
no v6 addresses and not attempt a v4 hunt. (The current code hunts a v4
address even when -V is set when there are no v6 addresses.)
*In the typical case, when -V is not set, the hunt will be for any address
family (v4 or v6) where a v4 address will be prioritized per the hunt*.
This way look ups (DNS or system) that only find v6 addresses (and no v4)
can use v6 w/o requiring the -V. Also, the server (without a -B) will
listen on both v4 and v6, i.e. 'iperf -s' will listen on both families
(AF_UNSPEC) allowing the client to determine which is used.
A server with 'iperf -s -V' will only listen on v6 addresses to be
consistent with *"-V means restrict to v6."*
Please feel free to comment
Thanks,
Bob
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users
