perfSONAR User Q&A and Other Discussion

["Karch, Roland (RRZE)" <>]

Hi,

 

such “cross compiled” packages between Debian and Ubuntu have failed for me in the past in pretty much a similar way. Older Debian versions don’t ship with a nanosecond-precision kernel but rather a microsecond one. If you run binaries that use those interfaces, they tend to become “off by a factor of 1000” kind of broken. The testing packages should likely be better, as Debian recently also moved to nanoseconds.

 

With best wishes,

Roland

 

From: [mailto:] On Behalf Of John-Paul Robinson
Sent: Monday, March 02, 2015 9:27 PM
To: Aaron Brown
Cc:
Subject: Re: [perfsonar-user] bwctl using milliseconds for interval designation on Ubuntu?

 

Maybe.

This is in the Ubuntu Universe repo (http://packages.ubuntu.com/trusty/net/bwctl-client), so it really comes from Debian upstream. (https://packages.debian.org/jessie/bwctl-client)

Looks like they have 1.5.2 in testing.  (https://packages.debian.org/sid/bwctl-client) I'll check and see about installing it.

In the mean time I'll multiply by 1000 on the Ubuntu side. :)

~jpr

On 03/02/2015 02:10 PM, Aaron Brown wrote:

Hey John-Paul,

 

Ah ok. My guess is that there may be a version mismatch going on. Is there anyway to upgrade from 1.4.1 to 1.5.3?

 

Cheers,

Aaron

 

On Mar 2, 2015, at 2:53 PM, John-Paul Robinson <> wrote:

 

Aaron,

bwctl version is:

jpr@laptop:~$ bwctl -V

Version: 1.4.1

I don't seem to have bwping installed (or available).  Here's the initial output of a bwctl command with the default interval of -i 1 specified:

bwctl -t 30 -i 1 -P 1 -d data/ -p -c 56m-ps.sox.net -s thing2.it.uab.edu

WARNING: interval too small, increasing from 0.00 to 0.5 seconds.
------------------------------------------------------------
Server listening on TCP port 5114
Binding to local address 143.215.194.125
TCP window size: 87380 Byte (default)
------------------------------------------------------------
[ 14] local 143.215.194.125 port 5114 connected with 138.26.125.8 port 5114
[ ID] Interval       Transfer     Bandwidth
[ 14]  0.0- 0.5 sec  15918048 Bytes  254688768 bits/sec
[ 14]  0.5- 1.0 sec  16030224 Bytes  256483584 bits/sec
[ 14]  1.0- 1.5 sec  16619832 Bytes  265917312 bits/sec

Here's the output for the same command with -i 1000:

------------------------------------------------------------
Server listening on TCP port 5115
Binding to local address 143.215.194.125
TCP window size: 87380 Byte (default)
------------------------------------------------------------
[ 14] local 143.215.194.125 port 5115 connected with 138.26.125.8 port 5115
[ ID] Interval       Transfer     Bandwidth
[ 14]  0.0- 1.0 sec  25800480 Bytes  206403840 bits/sec
[ 14]  1.0- 2.0 sec  18254592 Bytes  146036736 bits/sec
[ 14]  2.0- 3.0 sec  23926320 Bytes  191410560 bits/sec

Let me know what I need to do with bwping.

~jpr

On 03/02/2015 07:38 AM, Aaron Brown wrote:

Hi John-Paul,

Which version of bwctl is running on ubuntu? Also, could you send the bwping output wiht the “-v” command specified?

Cheers,

Aaron

On Feb 27, 2015, at 5:21 PM, John-Paul Robinson  wrote:

Hi,

I've installed bwctl on a variety of machines lately and have discovered

that bwctl on Ubuntu (14.04) uses milleseconds for the -i argument

instead of seconds as on other platforms.  If I use bwctl from my Ubuntu

node in local or third party tests and set "-i 1", I get an error from

the iperf layer complaining that the interval is too short and that it

has been increased to 0.5 seconds.  If I set "-i 1000", I get the

expected one second interval behavior.

Has anyone else encountered this?

~jpr

 

 

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature