From: Manish S M. <man...@ua...> - 2005-05-27 20:14:49
|
Do you mean, you want to specifically bind iperf to the wireless interface (your IP is say 192.168.0.3) and not the ethernet IP? If this is the case, there is a -B option on the client side which allows you to specify specific network interface you want to use. The client command should go some thing like this iperf -c <server ip> -B 192.168.0.3 -i 1 The bind option would be similar for the server side too. Manish Mittal -----Original Message----- From: own...@da... on behalf of Marc Herbert Sent: Fri 5/27/2005 6:03 AM To: ipe...@da... Cc: Subject: Re: specifiying a wireless interface On Fri, 27 May 2005, Larry McGrath wrote: > I'm trying setup iperf server and client for a > wireless interface (Cisco Aironet 350 cards in use). > Unfortunately, I don't know how to specify that I want > to use iperf for the wireless interface rather than > the ethernet interface. Could someone outline how this > can be achieved. Any suggestions are very much > appreciated. The output interface is chosen according to your routing table. Your routing holds a number of IP destination addresses subsets. For each destination, the table gives the interface (and optionally router) that will be used. The routing table is more or less cleverly/automatically configured by the system when you bring up/down the interfaces but you can modify it at will using the "route" command on Windows and "route" (or better "ip route" on linux). You'll easily find plenty of documentation about this. Be careful, you may have routing configurations where packets go out from one interface and replies come in from another interface. Cheers, Marc. -- So einfach wie möglich. Aber nicht einfacher -- Albert Einstein |