perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

I think the GUI intentionally leaves out the loopback interface to avoid confusion since in most cases that’s not what you want. Sounds like you have a case where you do though .  You should be able to specify it by editing the /etc/perfsonar/regulartesting.conf file and specifying the “local_interface” directive, for example:

<test>

   description     bwctl/iperf3 test

   

   local_interface lo:0

   target          host1.example

   target          host2.example

   target          host3.example

   <parameters>

       type             bwctl

       tool             iperf3

       duration         20

   </parameters>

   <schedule>

       type       regular_intervals

       interval   60

   </schedule>

</test>

Alternatively you can use “local_address” instead of local_interface and specify the IP. 

To confirm, it also sounds like interfaces like eth0:0 or similar aren’t showing up in the GUI list for you? You can obviously use the workaround above but I can’t imagine why those would be intentionally ignored, so if that is indeed the case I will file a bug.

Thanks,

Andy

On October 12, 2016 at 8:57:16 AM, Victor Olifer () wrote:

Hi,
Is it possible to use a loopback address with a public IP address assigned (as
lo:0) as an interface in the perfsonar tests? I failed to do so as a loopback
lo:0 is up, I can ping it from inside of a host but the perfsonar GUI 'Tests
configuration' doesn't show it in the drop-down Interface menu of a test. The
same happens with aliases of normal harware interfaces like eth0.

Thanks,
Victor