APEX backbone: Difference between revisions

From WirelessAfrica
Line 34: Line 34:


=== Lammerskop (May 21 13:37) ===
=== Lammerskop (May 21 13:37) ===
Meraka:


Remote:
PING 192.168.10.254 (192.168.10.254): 56 data bytes
64 bytes from 192.168.10.254: icmp_seq=0 ttl=64 time=55.760 ms
64 bytes from 192.168.10.254: icmp_seq=1 ttl=64 time=25.314 ms
64 bytes from 192.168.10.254: icmp_seq=2 ttl=64 time=23.425 ms
 
--- 192.168.10.254 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.425/34.833/55.760/14.818 ms
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.10.254, TCP port 5001
TCP window size: 32.5 KByte (default)
------------------------------------------------------------
[  5] local 192.168.10.222 port 60571 connected with 192.168.10.254 port 5001
[ ID] Interval      Transfer    Bandwidth
[  5]  0.0-16.5 sec  6.22 MBytes  3.17 Mbits/sec


=== Duhva (May 21 16:49) ===
=== Duhva (May 21 16:49) ===

Revision as of 14:48, 28 May 2009

Motorola Backbone

The Motorola backbone is a wireless network build with Motorola cannopy equipment. The network starts at Meraka and goes right up-to Mariepskop and then down to Mbuzini. See picture:


Throughput tests

The following benchmarks are for network throughputs between Meraka and each one of the remote sites. The measurement tool that was uses is iperf

Renosterkop (May 21 09:34)

PING 192.168.10.254 (192.168.10.254): 56 data bytes 64 bytes from 192.168.10.254: icmp_seq=0 ttl=64 time=40.677 ms 64 bytes from 192.168.10.254: icmp_seq=1 ttl=64 time=19.507 ms 64 bytes from 192.168.10.254: icmp_seq=2 ttl=64 time=19.293 ms

--- 192.168.10.254 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 19.293/26.492/40.677/10.030 ms


Server listening on TCP port 5001 TCP window size: 64.0 KByte (default)



Client connecting to 192.168.10.254, TCP port 5001 TCP window size: 32.5 KByte (default)


[ 5] local 192.168.10.222 port 61471 connected with 192.168.10.254 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-16.1 sec 7.62 MBytes 3.97 Mbits/sec

Lammerskop (May 21 13:37)

PING 192.168.10.254 (192.168.10.254): 56 data bytes 64 bytes from 192.168.10.254: icmp_seq=0 ttl=64 time=55.760 ms 64 bytes from 192.168.10.254: icmp_seq=1 ttl=64 time=25.314 ms 64 bytes from 192.168.10.254: icmp_seq=2 ttl=64 time=23.425 ms

--- 192.168.10.254 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 23.425/34.833/55.760/14.818 ms


Server listening on TCP port 5001 TCP window size: 64.0 KByte (default)



Client connecting to 192.168.10.254, TCP port 5001 TCP window size: 32.5 KByte (default)


[ 5] local 192.168.10.222 port 60571 connected with 192.168.10.254 port 5001 [ ID] Interval Transfer Bandwidth [ 5] 0.0-16.5 sec 6.22 MBytes 3.17 Mbits/sec

Duhva (May 21 16:49)

Meraka:

Remote:

Garangkuva (May 22 10:29)

Meraka:

Remote:

Dullstroom (May 26 08:08)

Meraka:

Remote:


Mauschberg (May 26 09:29)

Meraka:

Remote:


Kiepersol (May 26 11:28)

Meraka:

Remote:


Mariepskop (May 26 13:36)

Meraka:

Remote:


Lamomahsa (May 27 07:50)

Meraka:

Remote:


Mbuzini (May 27 10:00)

Meraka:

Remote: