Re: Specifying interface for iperf

[<cn...@ny...>]

Thanks for the note.

> Chris,
>  I posted a few months back with the same kind of problem -- doing
> multicast testing using clients/servers with multiple network 
> interface cards...
> 
> As an immediate fix for you, you should set up a static route on your
> server machine so that the kernel knows to send the join requests 
> to the
> proper interface.  (Otherwise it just picks the first one on the list,
> which in your case is probably the "other one.")
> 
> Something like this should work:
> 
> route add -net 224.0.0.0 netmask 255.225.0.0 -dev eth1
> 
>  then any multicast address 224.0.*.* would be "bound" to eth1.
...

Nope, that didn't seem to do it. <shrug>

  Search the archives for a posting from me on this 
> topic to
> get more details.

A fine idea.  If I could find the archives.  I poked around http://dast.nlanr.net/Projects/Iperf/ without any success.  Searching for "mailing list" and "archive" didn't help, either.