Re: How to set interface for Multicast server ?


Thank you Jim,
I just found your old  email:
http://archive.ncsa.uiuc.edu/lists/iperf-users/jan04/msg00003.html

- Jacob
On Thu, Feb 26, 2004 at 12:28:54PM -0500, Jim Kaba wrote:
> Jacob,
>   If I understand your question correctly, I think I ran into the same
> problem a few weeks back---i.e. there is currently not a good way to bind
> the iperf server to a multicast address on a specific network interface on
> machines that have more than one interface.
> 
> ...the way I got around it was to create a static route whenever I needed
> to do it:
> 
> route add 224.0.67.67 dev eth1  (this is assuming that "eth1" is the
> network device corresponding to the network interface whose hostname is
> "node2")
> 
> 
> ...by default mcast routes will be associated with an interface the kernel
> picks (usually the first to come up).
> 
> 
> Jim
> 
> 
> Jacob Teplitsky wrote:
> > 
> > Hi,
> > Is therte a way to bind a server to an interface:
> > 
> > node5> iperf -s -u -B 224.0.67.67 -i 1
> > ------------------------------------------------------------
> > Server listening on UDP port 5001
> > Binding to local address 224.0.67.67
> > Joining multicast group  224.0.67.67
> > Receiving 1470 byte datagrams
> > UDP buffer size: 32.0 KByte (default)
> > 
> > I how it can be done for the client:
> > 
> > /usr/local/bin/iperf -c 224.0.67.67 -u --ttl 5 -t 5 -B node2
> > 
> > Thanks
> > - Jacob
> 
> -- 
> ----------------------------------------------------------------------
> James T. Kaba                   
> Sarnoff Corporation   There are 10 kinds of people in the world:
> jkaba --at-- sarnoff.com     those who understand binary, and those who don't.
> 609-734-2246



Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index