perfsonar-user - Re: [perfsonar-user] bwctl OSX giving strange results
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Aaron Brown <>
- Cc: Brian Tierney <>, "" <>
- Subject: Re: [perfsonar-user] bwctl OSX giving strange results
- Date: Fri, 19 Dec 2014 09:51:35 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=sasl; b=H73ar56FTWR/Ni/Kq7Sun86p/v5AF694 9FrFSXEeY9LezbsUPKahwxzRksAnwREqzmdPndq6JCyH4i0ELdXEhNw2j/NEsA75 csccTfFd5qXOY9Naq8OVSwze/H78vaPBszitWUmY0jO9BVe4g+5HpIqGZF4kYx5k X5WkKDUudd8=
On 18/12/2014 21:26, Aaron Brown wrote:
I may be able to try this another day (v. busy right now), but I'll point out something else. Yesterday I put the perfsonar node and the Mac Mini into the production network (with the Mac Mini on the end of a GPON link), and I've enabled only throughput test and ping test (no latency/loss). The graphs I see are: * IPv4: reverse throughput and reverse ping only * IPv6: reverse throughput only I presume the ping test is using bwping -T ping? However if I do the tests from the command line, they all work fine (see below: all combinations of -c and -s, IPv6 and IPv4) I'm therefore leaning to the view that it's the core of bwctl itself which is the problem, rather than the external testing tools it invokes. As I say, I don't have time right now to continue investigation and fully understand the code paths. One useful approach might be to run bwctld under valgrind. Regards, Brian. [example@cov-perf-1 ~]$ bwping -c cov-client-1 -T ping bwping: Using tool: ping bwping: 21 seconds until test results available SENDER START PING 2001:db8:0:64::252(2001:db8:0:64::252) from 2001:db8:0:2::254 : 56 data bytes 64 bytes from 2001:db8:0:64::252: icmp_seq=1 ttl=63 time=0.532 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=2 ttl=63 time=0.451 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=3 ttl=63 time=0.486 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=4 ttl=63 time=0.470 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=5 ttl=63 time=0.460 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=6 ttl=63 time=0.454 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=7 ttl=63 time=0.447 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=8 ttl=63 time=0.490 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=9 ttl=63 time=0.450 ms 64 bytes from 2001:db8:0:64::252: icmp_seq=10 ttl=63 time=0.450 ms --- 2001:db8:0:64::252 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9000ms rtt min/avg/max/mdev = 0.447/0.469/0.532/0.025 ms SENDER END [example@cov-perf-1 ~]$ bwping -c 192.0.2.252 -T ping bwping: Using tool: ping bwping: 21 seconds until test results available SENDER START PING 192.0.2.252 (192.0.2.252) from 192.0.2.254 : 56(84) bytes of data. 64 bytes from 192.0.2.252: icmp_seq=1 ttl=63 time=0.451 ms 64 bytes from 192.0.2.252: icmp_seq=2 ttl=63 time=0.497 ms 64 bytes from 192.0.2.252: icmp_seq=3 ttl=63 time=0.436 ms 64 bytes from 192.0.2.252: icmp_seq=4 ttl=63 time=0.434 ms 64 bytes from 192.0.2.252: icmp_seq=5 ttl=63 time=0.411 ms 64 bytes from 192.0.2.252: icmp_seq=6 ttl=63 time=0.419 ms 64 bytes from 192.0.2.252: icmp_seq=7 ttl=63 time=0.443 ms 64 bytes from 192.0.2.252: icmp_seq=8 ttl=63 time=0.442 ms 64 bytes from 192.0.2.252: icmp_seq=9 ttl=63 time=0.441 ms 64 bytes from 192.0.2.252: icmp_seq=10 ttl=63 time=0.428 ms --- 192.0.2.252 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9000ms rtt min/avg/max/mdev = 0.411/0.440/0.497/0.025 ms SENDER END [example@cov-perf-1 ~]$ bwping -s cov-client-1 -T ping bwping: Using tool: ping bwping: 21 seconds until test results available SENDER START PING6(56=40+8+8 bytes) 2001:db8:0:64::252 --> 2001:db8:0:2::254 16 bytes from 2001:db8:0:2::254, icmp_seq=0 hlim=63 time=0.327 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=1 hlim=63 time=0.306 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=2 hlim=63 time=0.364 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=3 hlim=63 time=0.347 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=4 hlim=63 time=0.319 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=5 hlim=63 time=0.312 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=6 hlim=63 time=0.405 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=7 hlim=63 time=0.330 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=8 hlim=63 time=0.321 ms 16 bytes from 2001:db8:0:2::254, icmp_seq=9 hlim=63 time=0.381 ms --- 2001:db8:0:2::254 ping6 statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.306/0.341/0.405/0.031 ms SENDER END [example@cov-perf-1 ~]$ bwping -s 192.0.2.252 -T ping bwping: Using tool: ping bwping: 21 seconds until test results available SENDER START PING 192.0.2.254 (192.0.2.254) from 192.0.2.252: 56 data bytes 64 bytes from 192.0.2.254: icmp_seq=0 ttl=63 time=0.286 ms 64 bytes from 192.0.2.254: icmp_seq=1 ttl=63 time=0.413 ms 64 bytes from 192.0.2.254: icmp_seq=2 ttl=63 time=0.439 ms 64 bytes from 192.0.2.254: icmp_seq=3 ttl=63 time=0.297 ms 64 bytes from 192.0.2.254: icmp_seq=4 ttl=63 time=0.298 ms 64 bytes from 192.0.2.254: icmp_seq=5 ttl=63 time=0.324 ms 64 bytes from 192.0.2.254: icmp_seq=6 ttl=63 time=0.372 ms 64 bytes from 192.0.2.254: icmp_seq=7 ttl=63 time=0.362 ms 64 bytes from 192.0.2.254: icmp_seq=8 ttl=63 time=0.353 ms 64 bytes from 192.0.2.254: icmp_seq=9 ttl=63 time=0.298 ms --- 192.0.2.254 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.286/0.344/0.439/0.050 ms SENDER END [example@cov-perf-1 ~]$ |
- [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Tierney, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Bruce A. Mah, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/21/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/22/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/21/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Aaron Brown, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Aaron Brown, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Aaron Brown, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/20/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/23/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/23/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Steven G. Huter, 12/23/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Aaron Brown, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Candler, 12/19/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Bruce A. Mah, 12/18/2014
- Re: [perfsonar-user] bwctl OSX giving strange results, Brian Tierney, 12/18/2014
Archive powered by MHonArc 2.6.16.