Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Andrew Gallatin
On Tue, Apr 17, 2012 at 11:11 AM, Marc Herbert wrote: > Back to your problems: it is very difficult to force Linux to send packets > outside and back to itself. That's because it is a massive waste of > resources and loss of performance. Fortunately this has been discussed > already here and else

Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Marc Herbert
2012/4/17 Tom Throckmorton > I can't believe nobody's asked this yet, but, what does scooby do? ;-) Brilliant :-) > Seriously, though - as you've described your test, you're trying to > have iperf test from one on-board NIC to another in the same host. > What is the purpose of this test? I do n

Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Tom Throckmorton
On Tue, Apr 17, 2012 at 9:16 AM, Andrew M wrote: > Yes it's linux.  arp_filter sounded like a good place to start but it > didn't fix the issue.  I still get this: > > [root@scooby ~]# ifconfig em1 192.168.123.1 > [root@scooby ~]# ifconfig em2 192.168.234.1 > [root@scooby ~]# iperf -p 777 -B192.16

Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Marc Herbert
Andrew, I did not spend enough time reading your first post and missed the fact your box is trying to send packets to itself back to back. Sorry I pointed you in the wrong direction (I thought you "only" had two interfaces connected to the same subnet, another interesting problem) Back to your

Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Andrew M
Yes it's linux. arp_filter sounded like a good place to start but it didn't fix the issue. I still get this: [root@scooby ~]# ifconfig em1 192.168.123.1 [root@scooby ~]# ifconfig em2 192.168.234.1 [root@scooby ~]# iperf -p 777 -B192.168.234.1 -c192.168.123.1

Re: [Iperf-users] client not binding to correct interface

2012-04-17 Thread Marc Herbert
Is this Linux? If yes try enabling arp_filter. I suspect iperf binds to an address, not to an interface. http://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt arp_filter - BOOLEAN 1 - Allows you to have multiple network interfaces on the same subnet, and have the ARPs f

[Iperf-users] client not binding to correct interface

2012-04-16 Thread Andrew M
I have two network interfaces in one host: em1192.168.123.1 em2192.168.234.1 I'm running: SERVER: [root@scooby ~]# iperf -fm -p 777 -B192.168.123.1 -s Server listening on TCP port 777 Binding to local address 192.168.123