Greetings,
Well, to start with, I can see you using the "
bing" utility (no relation to the search engine) to check what the actual bandwidth between boxes is. As an example:
Code:
dev1 ~ # bing 192.168.2.221 192.168.2.250
BING 192.168.2.221 (192.168.2.221) and 192.168.2.250 (192.168.2.250)
44 and 108 data bytes (1024 bits)
192.168.2.250: minimum delay difference is zero, can't estimate link throughput
192.168.2.250: 6.781Mbps 0.151ms 0.147461us/bit
192.168.2.250: 6.606Mbps 0.155ms 0.151367us/bit
192.168.2.250: 6.400Mbps 0.160ms 0.156250us/bit
192.168.2.250: 6.360Mbps 0.161ms 0.157227us/bit
192.168.2.250: 6.440Mbps 0.159ms 0.155273us/bit
192.168.2.250: 6.400Mbps 0.160ms 0.156250us/bit
192.168.2.250: 6.440Mbps 0.159ms 0.155273us/bit
192.168.2.250: 6.400Mbps 0.160ms 0.156250us/bit
192.168.2.250: 6.360Mbps 0.161ms 0.157227us/bit
192.168.2.250: 6.400Mbps 0.160ms 0.156250us/bit
192.168.2.250: 6.360Mbps 0.161ms 0.157227us/bit
192.168.2.250: 3.048Mbps 0.336ms 0.328125us/bit
192.168.2.250: 3.122Mbps 0.328ms 0.320313us/bit
^C
--- 192.168.2.221 statistics ---
bytes out in dup loss rtt (ms): min avg max std dev
44 5632 5632 0% 0.013 0.014 0.057 0.001
108 5632 5632 0% 0.012 0.014 0.018 0.001
--- 192.168.2.250 statistics ---
bytes out in dup loss rtt (ms): min avg max std dev
44 5632 5632 0% 0.472 0.669 7.963 0.121
108 5631 5631 0% 0.800 0.824 1.651 0.031
--- estimated link characteristics ---
host bandwidth ms
warning: rtt big 192.168.2.221 0.012ms < rtt small 192.168.2.221 0.013ms
192.168.2.250 3.122Mbps 0.459
dev1 ~ #
Now that was an interactive usage where I had to Ctrl+C out of it, but you should get the idea. There are ways of using
bing programmatically, to include using a specific file to transfer to check the network usage. Check the
man page for the options. Also, you really only need to do it from the box that has
bing installed. The other boxes don't need any additional software installed.
HTH. Let us know.
