perfSONAR User Q&A and Other Discussion

["Andrew Lake" <>]

Hi,

That is correct, all tests setup by the web interface set -s. 

Thanks,

Andy

On Mon, Jun 15, 2015 at 9:51 AM, Joe Breen <> wrote:

Andy,

Thanks for the quick reply.  I was being a little dense and stuck in a troubleshooting tunnel.  Thank you for pulling my head out.  I am still seeing an issue in the described scenario but will do additional digging with more tcpdump.  I did some quick tests with bwctl -s <ip address> and it is binding the data plane correctly. 

Reality check follow-up question:  In the web interface test parameters, when I choose the interface for the test, the script is passing the -s flag for all tests, correct?

  --Joe

On Mon, Jun 15, 2015 at 7:26 AM, Andrew Lake <> wrote:

Hi Joe,

The -B option only affects the control connection, not the data connection (i.e. the interface your underlying iperf uses). To change the address that iperf uses, give the tool the -s option. Example: bwctl -s 10.92.2.12 -c 10.90.1.100

Hope that helps,

Andy

On Mon, Jun 15, 2015 at 9:20 AM, Joe Breen <> wrote:

Hi,

With bwctl ver. 1.5.4-1 using iperf in perfsonar toolkit 3.4.2 (3.4.2-12.pSPS), I was wondering if anyone has seen a recent issue with binding bwctl on particular interfaces?

Scenario:

perfSONAR toolkit box with 3 interfaces, 1 management with default, 1 interface for perfSONAR binding, and 1 interface setup to route to a private network using Quagga.  The scenario looks similar to the following:

             management

                      |

 10.92.2.12 --- host  --  10.1.5.1  <-> 10.1.5.2 - BGP router - l0.20.1.2 <->|
                                                                                                          ^
                                                                                                          |

                                                                                                          v

                                host 10.21.1.2  <->  10.21.1.1 -local router- 10.20.1.1

If I use bwctl with a -B or --local_address to bind the test to 10.92.2.12, the test results still show up using 10.1.5.1.  (See example below)   This fact causes issues when ACLs block or routing policy does not distribute the point to point connections.  If I use a "ping -I 10.92.2.12 10.21.1.2" to source the same address, the binding with ICMP works

###########################################
Example 1 - NOTE that the bwctl is using 10.1.5.1, though I have told it explicitly to bind to 10.92.2.12


[chpcadmin@perf2 ~]$ bwctl -B 10.92.2.12 -c 10.90.1.100
bwctl: Using tool: iperf
bwctl: 27 seconds until test results available

RECEIVER START
------------------------------------------------------------
Server listening on TCP port 5083
Binding to local address 10.90.1.100
TCP window size: 87380 Byte (default)
------------------------------------------------------------
[ 15] local 10.90.1.100 port 5083 connected with 10.1.5.1 port 40822
[ ID] Interval       Transfer     Bandwidth
[ 15]  0.0-10.3 sec  514981888 Bytes  399235215 bits/sec
[ 15] MSS size 1448 bytes (MTU 1500 bytes, ethernet)

RECEIVER END