From: Nirav J. <jas...@us...> - 2004-10-21 19:00:23
|
Hi Cris, You are correctly using the -B option for binding to an interface. Here is what I used to bind to 4 different interfaces. [jasapara@emulab-localhost ~]$ ./iperf -s -B 10.1.1.2 -w 64K -p 5001 [jasapara@emulab-localhost ~]$ ./iperf -s -B 10.1.2.2 -w 64K -p 5002 [jasapara@emulab-localhost ~]$ ./iperf -s -B 10.1.3.2 -w 64K -p 5003 [jasapara@emulab-localhost ~]$ ./iperf -s -B 10.1.4.2 -w 64K -p 5004 Which gave me 4 servers listening on 4 different interfaces and 4 different ports. Are you sure the IP for the other interface is 224.0.12.34 ? Can you confirm that ? - Nirav Jasapara. -----Original Message----- From: own...@da... [mailto:own...@da...] On Behalf Of cn...@ny... Sent: Thursday, October 21, 2004 6:27 AM To: ipe...@da... Subject: Specifying interface for iperf Running iperf 2.0 on a Linux system with 2 interfaces, I do: iperf -s -u -B 224.0.55.55 -i 1 & and I see: Server listening on UDP port 5001 Binding to local address 224.0.12.34 Joining multicast group 224.0.12.34 Receiving 1470 byte datagrams UDP buffer size: 64.0 KByte (default) but I _don't_ see any join message on my network of interest. I'm guessing it went out the other interface. Can I specify the interface to use? I don't see any option for that in the docs. Thanks. Chris |