If memory serves me right, Bob McMahon wrote: > Hi Bruce, > > We used the *%<dev>* for both tx and and rx device binding in iperf 2. Just > something to consider for consistency between the two tools. > > *To affect the physical output interface (e.g. dual homed systems) either > use -c <host>%<dev> (requires root) which bypasses this host route table > lookup, or configure policy routing per each -B source address and set the > output interface appropriately in the policy routes. On the server or > receive, only packets destined to -B IP address will be received. It's also > useful for multicast. For example, iperf -s -B 224.0.0.1%eth0 will only > accept ip multicast packets with dest ip 224.0.0.1 that are received on the > eth0 interface, while iperf -s -B 224.0.0.1 will receive those packets on > any interface, Finally, the device specifier is required for v6 link-local, > e.g. -c [v6addr]%<dev> -V, to select the output interface.*
Hi Bob-- That looks like a good idea and not too hard to implement either. Thanks! Bruce.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
