Re: Binding to an Interface

To: iperf-users --at-- dast.nlanr.net
Subject: Re: Binding to an Interface
From: "Jeff W. Boote" <boote --at-- internet2.edu>
Date: Fri, 31 Aug 2007 09:17:59 -0600
Content-transfer-encoding: 8bit
Content-type: text/plain; charset=windows-1252; format=flowed
In-reply-to: <20070831140906.9E3E2D08020@lin3.netandhost.com>
References: <20070831140906.9E3E2D08020@lin3.netandhost.com>
Reply-to: iperf-users --at-- dast.nlanr.net
Sender: owner-iperf-users --at-- dast.nlanr.net
User-agent: Thunderbird 2.0.0.6 (Macintosh/20070728)

anand wrote:

Iperf –s <interface address>
Iperf –c <interface address>
Do we have such functionality already in the iperf?

Funny you should ask. It is not currently there, but I was just looking for it yesterday. (I put it on my list to consider adding to bwctl, so I was looking to see if iperf had it yet.)

In fact, it should be fairly trivial to add using the sockopt SO_BINDTODEVICE. But, it would probably be easier to implement using actual interface names such as eth0, etc.

Given the interface address, it would be possible to see what addresses are currently configured on each interface and then do this. But, I'm not sure it is worth it. (There are some potentially complex cases.)

I'm off on vacation for the next couple of days, but if no one as done this by the time I get back I will take a look.

jeff

References:
- Binding to an Interface
  - From: anand

Prev by Date: Binding to an Interface
Previous by thread: Binding to an Interface

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