wiki:PlasticSlices/BaselineEvaluation/Baseline3Details

  1. plastic-101
    1. Commands run on each client
    2. Round 1
      1. Results
      2. Analysis
    3. Round 2
      1. Results
      2. Analysis
    4. Round 3
      1. Results
      2. Analysis
    5. Round 4
      1. Results
      2. Analysis
    6. Round 5
      1. Results
      2. Analysis
    7. Round 6
      1. Results
      2. Analysis
  2. plastic-102
    1. Commands run on each client
    2. Round 1
      1. Results
      2. Analysis
    3. Round 2
      1. Results
      2. Analysis
    4. Round 3
      1. Results
      2. Analysis
    5. Round 4
      1. Results
      2. Analysis
    6. Round 5
      1. Results
      2. Analysis
    7. Round 6
      1. Results
      2. Analysis
  3. plastic-103
    1. One-time prep commands run on each client and server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  4. plastic-104
    1. One-time prep commands run on each client and server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  5. plastic-105
    1. One-time prep commands run on each client and server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  6. plastic-106
    1. One-time prep commands run on each client and server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  7. plastic-107
    1. One-time prep commands run on each server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  8. plastic-108
    1. One-time prep commands run on each server
    2. Commands run on each server
    3. Commands run on each client
    4. Round 1
      1. Results
      2. Analysis
    5. Round 2
      1. Results
      2. Analysis
    6. Round 3
      1. Results
      2. Analysis
    7. Round 4
      1. Results
      2. Analysis
    8. Round 5
      1. Results
      2. Analysis
    9. Round 6
      1. Results
      2. Analysis
  9. plastic-109
    1. One-time prep commands run on each server
    2. One-time prep commands run on each client
    3. Commands run on each server
    4. Commands run on each client
    5. Round 1
      1. Results
      2. Analysis
    6. Round 2
      1. Results
      2. Analysis
    7. Round 3
      1. Results
      2. Analysis
    8. Round 4
      1. Results
      2. Analysis
    9. Round 5
      1. Results
      2. Analysis
    10. Round 6
      1. Results
      2. Analysis
  10. plastic-110
    1. One-time prep commands run on each server
    2. One-time prep commands run on each client
    3. Commands run on each server
    4. Commands run on each client
    5. Round 1
      1. Results
      2. Analysis
    6. Round 2
      1. Results
      2. Analysis
    7. Round 3
      1. Results
      2. Analysis
    8. Round 4
      1. Results
      2. Analysis
    9. Round 5
      1. Results
      2. Analysis
    10. Round 6
      1. Results
      2. Analysis

Here are the details of Baseline 3, divided by slice.

In this baseline, we ran six rounds of experiments, one per day; except that too many things were down on the second day, so we ran two on the last day. In rounds 1 through 5, we ran all ten experiments simultaneously; in round 6, we ran them sequentially.

The Stanford FlowVisor was suffering from significant instabilities during this baseline. We were originally planning to use of-planet3.stanford.edu and of-planet4.stanford.edu in three experiments, but those plnodes were VMs, and were frequently unreachable. We switched to using of-planet1 and ofplanet2, which are on dedicated hardware, for round 1, but the FlowVisor problems also left them unreachable too much of the time, so we dropped the Stanford plnodes from this baseline entirely for rounds 2 - 6. The tables of client/server pairs are for rounds 2 - 6.

We ran a 'screen' process for each slice, and connected to each plnode in a window in that 'screen' process; we then logged each session using the 'screenlog' feature, which saves files in the same format as the 'typescript' command, i.e. including all keystrokes entered, terminal escape sequences, etc. The raw logs are at http://www.gpolab.bbn.com/plastic-slices/baseline-logs/baseline-3/, with a subdirectory for the logs for each round.

plastic-101

GigaPing, using count=100000, and this table of client/server pairs:

client server server address
ganel.gpolab.bbn.com planetlab5.clemson.edu server=10.42.101.105
planetlab4.clemson.edu plnode2.cip.gatech.edu server=10.42.101.101
plnode1.cip.gatech.edu pl5.myplc.grnoc.iu.edu server=10.42.101.73
pl4.myplc.grnoc.iu.edu orbitplc2.orbit-lab.org server=10.42.101.112
orbitplc1.orbit-lab.org pl02.cs.washington.edu server=10.42.101.81
pl01.cs.washington.edu wings-openflow-3.wail.wisc.edu server=10.42.101.96
wings-openflow-2.wail.wisc.edu gardil.gpolab.bbn.com server=10.42.101.52

Commands run on each client

server=<ipaddr>
sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server

Round 1

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99979 received, 0% packet loss, time 768419ms
rtt min/avg/max/mdev = 59.355/59.580/604.942/7.380 ms, pipe 71

planetlab4.clemson.edu:

+$ server=10.42.101.101

+$ sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server
write failed: Broken pipe

plnode1.cip.gatech.edu:

+$ server=10.42.101.73

+$ sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server
write failed: Broken pipe

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 0 received, 100% packet loss, time 1009280ms

orbitplc1.orbit-lab.org:

--- 10.42.101.91 ping statistics ---
100000 packets transmitted, 0 received, 100% packet loss, time 1099200ms

of-planet1.stanford.edu:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 88364 received, 11% packet loss, time 787022ms
rtt min/avg/max/mdev = 152.667/206.759/24389.256/963.374 ms, pipe 3866

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 66226 received, 33% packet loss, time 854819ms
rtt min/avg/max/mdev = 59.682/70.918/1729.623/93.323 ms, pipe 166

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 95409 received, 4% packet loss, time 892338ms
rtt min/avg/max/mdev = 29.549/29.626/330.938/3.001 ms, pipe 36

Analysis

Many things were down here: Clemson couldn't ping GT, GT couldn't ping Indiana, Indiana couldn't ping Rutgers, Rutgers couldn't ping Stanford. Stanford could ping Washington, but with noticeable packet loss. Similarly, washington could ping Wisconsin, with substantial packet loss. And Wisconsin to BBN also showed noticeable packet loss. Only BBN - Clemson worked as expected.

Round 2

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99976 received, 0% packet loss, time 733756ms
rtt min/avg/max/mdev = 59.349/59.807/928.933/13.945 ms, pipe 122

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 417969ms
rtt min/avg/max/mdev = 3.637/4.153/429.045/5.168 ms, pipe 58

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
100000 packets transmitted, 97946 received, 2% packet loss, time 774548ms
rtt min/avg/max/mdev = 29.901/38.231/974.494/17.523 ms, pipe 116

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 98093 received, 1% packet loss, time 741679ms
rtt min/avg/max/mdev = 54.919/55.374/897.318/7.951 ms, pipe 92

orbitplc1.orbit-lab.org:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 99851 received, 0% packet loss, time 697039ms
rtt min/avg/max/mdev = 104.710/105.800/1894.081/20.882 ms, pipe 193

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 99919 received, 0% packet loss, time 708275ms
rtt min/avg/max/mdev = 59.680/61.142/1598.649/28.375 ms, pipe 156

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 808493ms
rtt min/avg/max/mdev = 29.542/29.655/414.374/4.188 ms, pipe 39

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99952 received, 0% packet loss, time 732747ms
rtt min/avg/max/mdev = 59.355/59.778/818.038/12.381 ms, pipe 82

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
100000 packets transmitted, 99959 received, 0% packet loss, time 410174ms
rtt min/avg/max/mdev = 3.637/4.177/698.329/9.334 ms, pipe 80

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
100000 packets transmitted, 98020 received, 1% packet loss, time 734371ms
rtt min/avg/max/mdev = 35.821/38.364/1006.562/19.234 ms, pipe 119

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 98395 received, 1% packet loss, time 752356ms
rtt min/avg/max/mdev = 54.918/55.650/1148.200/16.149 ms, pipe 137

orbitplc1.orbit-lab.org:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 99904 received, 0% packet loss, time 697980ms
rtt min/avg/max/mdev = 104.709/106.310/1567.510/30.249 ms, pipe 189

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 99821 received, 0% packet loss, time 703188ms
rtt min/avg/max/mdev = 59.679/60.998/1260.797/21.920 ms, pipe 124

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 99981 received, 0% packet loss, time 815183ms
rtt min/avg/max/mdev = 29.548/29.618/324.155/2.258 ms, pipe 32

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99979 received, 0% packet loss, time 700018ms
rtt min/avg/max/mdev = 59.351/59.788/867.854/12.797 ms, pipe 108

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
100000 packets transmitted, 99982 received, 0% packet loss, time 413115ms
rtt min/avg/max/mdev = 3.634/4.065/232.682/2.564 ms, pipe 78

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
100000 packets transmitted, 98109 received, 1% packet loss, time 736730ms
rtt min/avg/max/mdev = 34.272/38.328/959.634/17.570 ms, pipe 121

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 98061 received, 1% packet loss, time 732580ms
rtt min/avg/max/mdev = 54.919/56.453/1568.651/32.915 ms, pipe 188

orbitplc1.orbit-lab.org:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 99847 received, 0% packet loss, time 701361ms
rtt min/avg/max/mdev = 104.711/106.201/1806.041/28.749 ms, pipe 203

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 99839 received, 0% packet loss, time 701006ms
rtt min/avg/max/mdev = 59.676/60.452/1169.483/6.409 ms, pipe 106

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 99975 received, 0% packet loss, time 852944ms
rtt min/avg/max/mdev = 29.549/29.686/486.283/5.477 ms, pipe 46

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99980 received, 0% packet loss, time 750269ms
rtt min/avg/max/mdev = 59.354/59.640/627.871/7.776 ms, pipe 78

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
100000 packets transmitted, 99949 received, 0% packet loss, time 412301ms
rtt min/avg/max/mdev = 3.655/4.328/927.277/14.406 ms, pipe 149

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
100000 packets transmitted, 97869 received, 2% packet loss, time 742460ms
rtt min/avg/max/mdev = 35.739/37.899/1086.931/13.812 ms, pipe 113

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 98204 received, 1% packet loss, time 748710ms
rtt min/avg/max/mdev = 77.411/78.521/2037.362/30.145 ms, pipe 210

orbitplc1.orbit-lab.org:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 99748 received, 0% packet loss, time 677663ms
rtt min/avg/max/mdev = 127.202/128.201/2648.787/23.825 ms, pipe 243

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 99843 received, 0% packet loss, time 703998ms
rtt min/avg/max/mdev = 59.682/60.386/289.054/0.906 ms, pipe 26

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 810044ms
rtt min/avg/max/mdev = 29.546/29.597/35.906/0.227 ms, pipe 7

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

ganel.gpolab.bbn.com:

--- 10.42.101.105 ping statistics ---
100000 packets transmitted, 99949 received, 0% packet loss, time 701316ms
rtt min/avg/max/mdev = 59.353/59.531/464.789/5.077 ms, pipe 51

planetlab4.clemson.edu:

--- 10.42.101.101 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 387940ms
rtt min/avg/max/mdev = 3.659/3.857/420.573/4.878 ms, pipe 79

plnode1.cip.gatech.edu:

--- 10.42.101.73 ping statistics ---
100000 packets transmitted, 99293 received, 0% packet loss, time 712263ms
rtt min/avg/max/mdev = 35.792/37.971/818.182/14.758 ms, pipe 88

pl4.myplc.grnoc.iu.edu:

--- 10.42.101.112 ping statistics ---
100000 packets transmitted, 99242 received, 0% packet loss, time 718932ms
rtt min/avg/max/mdev = 54.922/55.644/1063.326/14.887 ms, pipe 114

orbitplc1.orbit-lab.org:

--- 10.42.101.81 ping statistics ---
100000 packets transmitted, 99805 received, 0% packet loss, time 656381ms
rtt min/avg/max/mdev = 104.710/106.274/1607.809/31.262 ms, pipe 176

pl01.cs.washington.edu:

--- 10.42.101.96 ping statistics ---
100000 packets transmitted, 99885 received, 0% packet loss, time 686622ms
rtt min/avg/max/mdev = 59.679/60.413/1048.385/7.722 ms, pipe 109

wings-openflow-2.wail.wisc.edu:

--- 10.42.101.52 ping statistics ---
100000 packets transmitted, 99990 received, 0% packet loss, time 737095ms
rtt min/avg/max/mdev = 29.551/29.648/417.063/4.069 ms, pipe 51

Analysis

All results seem consistent with what we'd expect.

plastic-102

GigaPing, using count=100000, and this table of client/server pairs:

client server server address
sardis.gpolab.bbn.com planetlab4.clemson.edu server=10.42.102.104
planetlab5.clemson.edu plnode1.cip.gatech.edu server=10.42.102.100
plnode2.cip.gatech.edu pl4.myplc.grnoc.iu.edu server=10.42.102.72
pl5.myplc.grnoc.iu.edu orbitplc1.orbit-lab.org server=10.42.102.111
orbitplc2.orbit-lab.org pl01.cs.washington.edu server=10.42.102.80
pl02.cs.washington.edu wings-openflow-2.wail.wisc.edu server=10.42.102.95
wings-openflow-3.wail.wisc.edu bain.gpolab.bbn.com server=10.42.102.54

Commands run on each client

server=<ipaddr>
sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server

Round 1

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 99817 received, 0% packet loss, time 800241ms
rtt min/avg/max/mdev = 164.715/165.578/1646.129/27.737 ms, pipe 179

planetlab5.clemson.edu:

+$ server=10.42.102.100

+$ sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server
write failed: Broken pipe

plnode2.cip.gatech.edu:

+$ server=10.42.102.72

+$ sudo ping -i .001 -s $((1500-8-20)) -c 100000 $server
write failed: Broken pipe

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 0 received, 100% packet loss, time 1005458ms

orbitplc2.orbit-lab.org:

--- 10.42.102.91 ping statistics ---
100000 packets transmitted, 0 received, 100% packet loss, time 1098507ms

of-planet1.stanford.edu:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 95045 received, 4% packet loss, time 759672ms
rtt min/avg/max/mdev = 20.055/38.484/18150.472/522.726 ms, pipe 2243

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 68156 received, 31% packet loss, time 861675ms
rtt min/avg/max/mdev = 59.674/76.396/2832.148/112.947 ms, pipe 262

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 92299 received, 7% packet loss, time 829997ms
rtt min/avg/max/mdev = 29.549/29.679/438.234/4.634 ms, pipe 38

Analysis

As with plastic-101, many things didn't work well here. BBN - Clemson was ok, but everything else either failed outright or had noticeable packet loss.

Round 2

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 772977ms
rtt min/avg/max/mdev = 164.721/164.819/167.688/0.408 ms, pipe 26

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 405927ms
rtt min/avg/max/mdev = 3.617/3.964/14.311/0.795 ms, pipe 2

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
100000 packets transmitted, 97826 received, 2% packet loss, time 741235ms
rtt min/avg/max/mdev = 141.199/144.697/2080.797/43.868 ms, pipe 212

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 97995 received, 2% packet loss, time 763904ms
rtt min/avg/max/mdev = 160.272/160.794/435.929/8.174 ms, pipe 56

orbitplc2.orbit-lab.org:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 99887 received, 0% packet loss, time 726023ms
rtt min/avg/max/mdev = 102.663/103.868/2026.528/21.638 ms, pipe 223

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 99863 received, 0% packet loss, time 699013ms
rtt min/avg/max/mdev = 59.678/61.212/1814.763/34.051 ms, pipe 166

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 99792 received, 0% packet loss, time 841824ms
rtt min/avg/max/mdev = 29.549/29.611/543.194/1.675 ms, pipe 46

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 99889 received, 0% packet loss, time 798706ms
rtt min/avg/max/mdev = 164.715/165.987/1898.260/38.342 ms, pipe 198

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
100000 packets transmitted, 99975 received, 0% packet loss, time 412976ms
rtt min/avg/max/mdev = 3.628/4.054/409.919/2.842 ms, pipe 43

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
100000 packets transmitted, 98030 received, 1% packet loss, time 750086ms
rtt min/avg/max/mdev = 141.131/145.164/1972.823/43.363 ms, pipe 223

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 97980 received, 2% packet loss, time 753394ms
rtt min/avg/max/mdev = 160.273/162.610/2362.202/51.804 ms, pipe 227

orbitplc2.orbit-lab.org:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 99883 received, 0% packet loss, time 715493ms
rtt min/avg/max/mdev = 102.661/104.424/2077.621/34.760 ms, pipe 255

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 99980 received, 0% packet loss, time 696294ms
rtt min/avg/max/mdev = 59.678/61.015/1312.818/23.602 ms, pipe 143

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 99859 received, 0% packet loss, time 866608ms
rtt min/avg/max/mdev = 29.544/29.648/324.374/3.002 ms, pipe 30

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 99907 received, 0% packet loss, time 773482ms
rtt min/avg/max/mdev = 164.715/165.754/1599.676/30.777 ms, pipe 163

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
100000 packets transmitted, 99960 received, 0% packet loss, time 414580ms
rtt min/avg/max/mdev = 3.620/4.150/582.808/6.535 ms, pipe 52

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
100000 packets transmitted, 98058 received, 1% packet loss, time 741332ms
rtt min/avg/max/mdev = 141.125/146.878/3625.371/89.308 ms, pipe 383

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 98086 received, 1% packet loss, time 748395ms
rtt min/avg/max/mdev = 160.275/160.944/893.925/11.989 ms, pipe 92

orbitplc2.orbit-lab.org:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 99761 received, 0% packet loss, time 717184ms
rtt min/avg/max/mdev = 102.660/103.565/867.662/7.272 ms, pipe 80

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 99821 received, 0% packet loss, time 698649ms
rtt min/avg/max/mdev = 59.678/60.398/1514.723/8.577 ms, pipe 141

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 99780 received, 0% packet loss, time 851839ms
rtt min/avg/max/mdev = 29.548/29.607/113.857/0.342 ms, pipe 10

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 99849 received, 0% packet loss, time 818273ms
rtt min/avg/max/mdev = 164.717/166.034/1964.661/40.587 ms, pipe 205

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
100000 packets transmitted, 99893 received, 0% packet loss, time 413830ms
rtt min/avg/max/mdev = 3.634/4.037/708.316/2.872 ms, pipe 64

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
100000 packets transmitted, 98235 received, 1% packet loss, time 727206ms
rtt min/avg/max/mdev = 133.152/143.193/1175.137/8.928 ms, pipe 118

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 98160 received, 1% packet loss, time 759348ms
rtt min/avg/max/mdev = 182.766/183.235/1399.004/12.609 ms, pipe 132

orbitplc2.orbit-lab.org:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 99988 received, 0% packet loss, time 692098ms
rtt min/avg/max/mdev = 125.157/125.922/129.937/0.572 ms, pipe 24

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 99976 received, 0% packet loss, time 697788ms
rtt min/avg/max/mdev = 59.678/61.071/1346.900/25.112 ms, pipe 144

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 99827 received, 0% packet loss, time 846289ms
rtt min/avg/max/mdev = 29.546/29.637/413.063/2.665 ms, pipe 35

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

sardis.gpolab.bbn.com:

--- 10.42.102.104 ping statistics ---
100000 packets transmitted, 99643 received, 0% packet loss, time 711075ms
rtt min/avg/max/mdev = 164.724/165.979/1648.242/33.843 ms, pipe 184

planetlab5.clemson.edu:

--- 10.42.102.100 ping statistics ---
100000 packets transmitted, 100000 received, 0% packet loss, time 386195ms
rtt min/avg/max/mdev = 3.643/3.831/376.925/4.487 ms, pipe 54

plnode2.cip.gatech.edu:

--- 10.42.102.72 ping statistics ---
100000 packets transmitted, 99270 received, 0% packet loss, time 762441ms
rtt min/avg/max/mdev = 141.124/143.952/1245.122/22.314 ms, pipe 128

pl5.myplc.grnoc.iu.edu:

--- 10.42.102.111 ping statistics ---
100000 packets transmitted, 99148 received, 0% packet loss, time 679802ms
rtt min/avg/max/mdev = 160.274/161.387/2029.446/25.898 ms, pipe 205

orbitplc2.orbit-lab.org:

--- 10.42.102.80 ping statistics ---
100000 packets transmitted, 99865 received, 0% packet loss, time 661499ms
rtt min/avg/max/mdev = 102.664/103.395/1662.669/13.554 ms, pipe 162

pl02.cs.washington.edu:

--- 10.42.102.95 ping statistics ---
100000 packets transmitted, 99856 received, 0% packet loss, time 691389ms
rtt min/avg/max/mdev = 59.673/60.730/1182.688/17.436 ms, pipe 115

wings-openflow-3.wail.wisc.edu:

--- 10.42.102.54 ping statistics ---
100000 packets transmitted, 99976 received, 0% packet loss, time 779334ms
rtt min/avg/max/mdev = 29.553/29.584/146.857/0.436 ms, pipe 13

Analysis

All results seem consistent with what we'd expect.

plastic-103

GigaPerf TCP, using port=5103, size=350, and this table of client/server pairs:

client server server address
pl02.cs.washington.edu navis.gpolab.bbn.com server=10.42.103.55
ganel.gpolab.bbn.com orbitplc1.orbit-lab.org server=10.42.103.111
orbitplc2.orbit-lab.org pl01.cs.washington.edu server=10.42.103.80

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -B $server -p 5103 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -c $server -p 5103 -n 350M

Round 1

Results

of-planet1.stanford.edu:

+$ server=10.42.103.55

+$ nice -n 19 iperf -c $server -p 5103 -n 250M
connect failed: Connection timed out

ganel.gpolab.bbn.com:

+$ server=10.42.103.111

+$ nice -n 19 iperf -c $server -p 5103 -n 250M
connect failed: Connection timed out
write1 failed: Broken pipe
write2 failed: Broken pipe
------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 44169 connected with 10.42.103.111 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec

orbitplc2.orbit-lab.org:

+$ server=10.42.103.80

+$ nice -n 19 iperf -c $server -p 5103 -n 250M
connect failed: Connection timed out
write1 failed: Broken pipe
write2 failed: Broken pipe
------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 0.0.0.0 port 40359 connected with 10.42.103.80 port 5103
[  3]  0.0- 0.0 sec  0.00 Bytes  0.00 bits/sec

pl02.cs.washington.edu:

+$ server=10.42.103.91

+$ nice -n 19 iperf -c $server -p 5103 -n 250M
connect failed: Connection timed out

Analysis

Everything failed here... Stanford couldn't even connect to BBN. BBN got a couple of failures trying to connect to Rutgers, then got through, but then couldn't transfer any data. Ditto Rutgers to Washington; and then Washington couldn't even connect to Stanford.

Round 2

Results

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 59620 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-777.0 sec   350 MBytes  3.78 Mbits/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 33661 connected with 10.42.103.111 port 5103
[  3]  0.0-768.2 sec    350 MBytes  3.82 Mbits/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 52876 connected with 10.42.103.80 port 5103
[  3]  0.0-1303.6 sec    350 MBytes  2.25 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 59896 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-765.2 sec   350 MBytes  3.84 Mbits/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 56619 connected with 10.42.103.111 port 5103
[  3]  0.0-780.5 sec    350 MBytes  3.76 Mbits/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 46317 connected with 10.42.103.80 port 5103
[  3]  0.0-1398.2 sec    350 MBytes  2.10 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 46246 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-760.5 sec   350 MBytes  3.86 Mbits/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 37922 connected with 10.42.103.111 port 5103
[  3]  0.0-807.2 sec    350 MBytes  3.64 Mbits/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 59497 connected with 10.42.103.80 port 5103
[  3]  0.0-1429.9 sec    350 MBytes  2.05 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 41334 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-774.9 sec   350 MBytes  3.79 Mbits/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 58486 connected with 10.42.103.111 port 5103
[  3]  0.0-948.0 sec    350 MBytes  3.10 Mbits/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 49260 connected with 10.42.103.80 port 5103
[  3]  0.0-1558.8 sec    350 MBytes  1.88 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

pl02.cs.washington.edu:

------------------------------------------------------------
Client connecting to 10.42.103.55, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.81 port 46167 connected with 10.42.103.55 port 5103
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-457.6 sec   350 MBytes  6.42 Mbits/sec

ganel.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.103.111, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.51 port 55558 connected with 10.42.103.111 port 5103
[  3]  0.0-936.4 sec    350 MBytes  3.14 Mbits/sec

orbitplc2.orbit-lab.org:

------------------------------------------------------------
Client connecting to 10.42.103.80, TCP port 5103
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.103.112 port 44710 connected with 10.42.103.80 port 5103
[  3]  0.0-1108.2 sec    350 MBytes  2.65 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

plastic-104

GigaPerf UDP, using port=5104, size=500, rate=100, and this table of client/server pairs:

client server server address
planetlab4.clemson.edu gardil.gpolab.bbn.com server=10.42.104.52
planetlab5.clemson.edu orbitplc2.orbit-lab.org server=10.42.104.112

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -u -B $server -p 5104 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -u -c $server -p 5104 -n 500M -b 100M

Round 1

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 56957 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.3 sec   480 MBytes  99.7 Mbits/sec   0.048 ms 14467/356658 (4.1%)
[  3]  0.0-40.3 sec  177 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 39103 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.

Analysis

Clemson to BBN got nearly 100 Mbits/sec, and with a fairly good success rate for UDP. Clemson to GT didn't work at all -- there's no "Server Report" section because the client never made contact with the server.

Round 2

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 39958 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.9 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-38.5 sec   461 MBytes   100 Mbits/sec   0.067 ms 27877/356658 (7.8%)
[  3]  0.0-38.5 sec  208 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 37714 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.3 sec   476 MBytes  96.6 Mbits/sec   0.031 ms 17004/356658 (4.8%)
[  3]  0.0-41.3 sec  162 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 47896 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.8 sec   477 MBytes  98.2 Mbits/sec   0.037 ms 16454/356658 (4.6%)
[  3]  0.0-40.8 sec  160 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 43337 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.1 sec   484 MBytes  98.9 Mbits/sec   0.050 ms 11117/356658 (3.1%)
[  3]  0.0-41.1 sec  130 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 55203 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.7 sec   478 MBytes  98.6 Mbits/sec   0.032 ms 15617/356658 (4.4%)
[  3]  0.0-40.7 sec  150 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 53381 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.1 sec   481 MBytes  98.2 Mbits/sec   0.085 ms 13382/356658 (3.8%)
[  3]  0.0-41.1 sec  177 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 34899 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-42.0 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.3 sec   477 MBytes  96.9 Mbits/sec   0.043 ms 16723/356658 (4.7%)
[  3]  0.0-41.3 sec  74 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 55399 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.3 sec   483 MBytes  98.3 Mbits/sec   0.045 ms 11798/356658 (3.3%)
[  3]  0.0-41.3 sec  211 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.52, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.104 port 57268 connected with 10.42.104.52 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.9 sec   478 MBytes  98.1 Mbits/sec   0.041 ms 15389/356658 (4.3%)
[  3]  0.0-40.9 sec  205 datagrams received out-of-order

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.104.112, UDP port 5104
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.104.105 port 37657 connected with 10.42.104.112 port 5104
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   101 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-39.9 sec   477 MBytes   100 Mbits/sec   0.050 ms 16561/356658 (4.6%)
[  3]  0.0-39.9 sec  250 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

plastic-105

GigaPerf TCP, using port=5105, size=250, and this table of client/server pairs:

client server server address
wings-openflow-2.wail.wisc.edu planetlab5.clemson.edu server=10.42.105.105
planetlab4.clemson.edu sardis.gpolab.bbn.com server=10.42.105.53
bain.gpolab.bbn.com plnode2.cip.gatech.edu server=10.42.105.101
plnode1.cip.gatech.edu wings-openflow-3.wail.wisc.edu server=10.42.105.96

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -B $server -p 5105 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -c $server -p 5105 -n 250M

Round 1

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 36006 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-220.5 sec   250 MBytes  9.51 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 35513 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-278.9 sec   250 MBytes  7.52 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 56129 connected with 10.42.105.101 port 5105
[  3]  0.0-702.1 sec    250 MBytes  2.99 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 40317 connected with 10.42.105.96 port 5105
[  3]  0.0-355.5 sec    250 MBytes  5.90 Mbits/sec

Analysis

All results seem consistent with what we'd expect. (Which is itself somewhat unexpected at this point in this round.)

Round 2

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 38263 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-263.6 sec   250 MBytes  7.95 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 37628 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-337.6 sec   250 MBytes  6.21 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 37787 connected with 10.42.105.101 port 5105
[  3]  0.0-637.7 sec    250 MBytes  3.29 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 56549 connected with 10.42.105.96 port 5105
[  3]  0.0-159.6 sec    250 MBytes  13.1 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 57632 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-309.6 sec   250 MBytes  6.77 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 50320 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-319.4 sec   250 MBytes  6.57 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 51847 connected with 10.42.105.101 port 5105
[  3]  0.0-670.7 sec    250 MBytes  3.13 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 45259 connected with 10.42.105.96 port 5105
[  3]  0.0-158.9 sec    250 MBytes  13.2 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 45196 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-281.3 sec   250 MBytes  7.46 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 38246 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-350.2 sec   250 MBytes  5.99 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 48581 connected with 10.42.105.101 port 5105
[  3]  0.0-678.3 sec    250 MBytes  3.09 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 57937 connected with 10.42.105.96 port 5105
[  3]  0.0-159.8 sec    250 MBytes  13.1 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 37270 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-328.4 sec   250 MBytes  6.39 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 58593 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-321.0 sec   250 MBytes  6.53 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 38126 connected with 10.42.105.101 port 5105
[  3]  0.0-634.8 sec    250 MBytes  3.30 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 51984 connected with 10.42.105.96 port 5105
[  3]  0.0-159.1 sec    250 MBytes  13.2 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

wings-openflow-2.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.105.105, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.95 port 36042 connected with 10.42.105.105 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-167.4 sec   250 MBytes  12.5 Mbits/sec

planetlab4.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.105.53, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.104 port 55325 connected with 10.42.105.53 port 5105
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-247.7 sec   250 MBytes  8.47 Mbits/sec

bain.gpolab.bbn.com:

------------------------------------------------------------
Client connecting to 10.42.105.101, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.54 port 50408 connected with 10.42.105.101 port 5105
[  3]  0.0-578.6 sec    250 MBytes  3.62 Mbits/sec

plnode1.cip.gatech.edu:

------------------------------------------------------------
Client connecting to 10.42.105.96, TCP port 5105
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.42.105.100 port 51999 connected with 10.42.105.96 port 5105
[  3]  0.0-159.0 sec    250 MBytes  13.2 Mbits/sec

Analysis

All results seem consistent with what we'd expect.

plastic-106

GigaPerf UDP, using port=5106, size=500, rate=100, and this table of client/server pairs:

client server server address
planetlab5.clemson.edu wings-openflow-2.wail.wisc.edu server=10.42.106.95
wings-openflow-3.wail.wisc.edu plnode1.cip.gatech.edu server=10.42.106.100

One-time prep commands run on each client and server

sudo yum -y install iperf

Commands run on each server

server=<ipaddr>
nice -n 19 iperf -u -B $server -p 5106 -s -i 1

Commands run on each client

server=<ipaddr>
nice -n 19 iperf -u -c $server -p 5106 -n 500M -b 100M

Round 1

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 46561 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] WARNING: did not receive ack of last datagram after 10 tries.

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 43047 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.8 sec   464 MBytes  95.5 Mbits/sec   0.131 ms 25488/356658 (7.1%)
[  3]  0.0-40.8 sec  210 datagrams received out-of-order

plnode2.cip.gatech.edu:

{{{{


Client connecting to 10.42.106.104, UDP port 5106 Sending 1470 byte datagrams UDP buffer size: 122 KByte (default)


[ 3] local 10.42.106.101 port 33743 connected with 10.42.106.104 port 5106 [ 3] 0.0-1482.0 sec 17.2 GBytes 99.8 Mbits/sec [ 3] Sent 12572788 datagrams [ 3] Server Report: [ 3] 0.0-1481.8 sec 16.1 GBytes 93.2 Mbits/sec 0.138 ms 833663/12572787 (6.6%) [ 3] 0.0-1481.8 sec 223 datagrams received out-of-order }}}

Analysis

Clemson to Wisconsin has no Server Report section, but looking at the server-side log (not quoted here), it looks like the expected amount of data was actually transfered. Wisconsin to GT looks good. GT to Clemson is also good, except that it ran for nearly half an hour due to a bug in the version of iperf that comes with Fedora 8, which causes it not to exit when run as a UDP client.

Round 2

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 54239 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.7 sec   459 MBytes  94.6 Mbits/sec   0.048 ms 29066/356658 (8.1%)
[  3]  0.0-40.7 sec  171 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 48745 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   101 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.6 sec   440 MBytes  91.0 Mbits/sec   0.336 ms 42772/356658 (12%)
[  3]  0.0-40.6 sec  123 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect; the loss rates are a little high for UDP, but not surprisingly so.

Round 3

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 51582 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.9 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-41.0 sec   474 MBytes  97.0 Mbits/sec   0.026 ms 18523/356658 (5.2%)
[  3]  0.0-41.0 sec  128 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 36720 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.7 sec   461 MBytes  95.1 Mbits/sec   0.014 ms 27866/356658 (7.8%)
[  3]  0.0-40.7 sec  209 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 49523 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.5 sec   466 MBytes  96.6 Mbits/sec   0.024 ms 24464/356658 (6.9%)
[  3]  0.0-40.5 sec  109 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 43492 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.8 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.1 sec   460 MBytes  96.4 Mbits/sec   0.373 ms 28391/356658 (8%)
[  3]  0.0-40.1 sec  182 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 45595 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.5 sec   469 MBytes  97.2 Mbits/sec   0.025 ms 22260/356658 (6.2%)
[  3]  0.0-40.5 sec  77 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 49192 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.2 sec   462 MBytes  96.4 Mbits/sec   0.031 ms 27400/356658 (7.7%)
[  3]  0.0-40.2 sec  143 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

planetlab5.clemson.edu:

------------------------------------------------------------
Client connecting to 10.42.106.95, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.105 port 46123 connected with 10.42.106.95 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-42.0 sec   500 MBytes  99.8 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.9 sec   468 MBytes  96.0 Mbits/sec   0.021 ms 22476/356658 (6.3%)
[  3]  0.0-40.9 sec  169 datagrams received out-of-order

wings-openflow-3.wail.wisc.edu:

------------------------------------------------------------
Client connecting to 10.42.106.100, UDP port 5106
Sending 1470 byte datagrams
UDP buffer size:  109 KByte (default)
------------------------------------------------------------
[  3] local 10.42.106.96 port 48602 connected with 10.42.106.100 port 5106
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-41.7 sec   500 MBytes   100 Mbits/sec
[  3] Sent 356659 datagrams
[  3] Server Report:
[  3]  0.0-40.7 sec   475 MBytes  97.9 Mbits/sec   0.244 ms 17480/356658 (4.9%)
[  3]  0.0-40.7 sec  184 datagrams received out-of-order

Analysis

All results seem consistent with what we'd expect.

plastic-107

GigaWeb, using count=30, port=4107, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
planetlab5.clemson.edu pl4.myplc.grnoc.iu.edu server=10.42.107.72
pl5.myplc.grnoc.iu.edu plnode2.cip.gatech.edu server=10.42.107.101
plnode1.cip.gatech.edu pl02.cs.washington.edu server=10.42.107.81
pl01.cs.washington.edu planetlab4.clemson.edu server=10.42.107.104

One-time prep commands run on each server

sudo yum -y install pyOpenSSL patch
rm -rf ~/gigaweb
mkdir -p ~/gigaweb/docroot

cd ~/gigaweb
wget http://code.activestate.com/recipes/442473-simple-http-server-supporting-ssl-secure-communica/download/1/ -O httpsd.py
wget http://groups.geni.net/geni/attachment/wiki/PlasticSlices/Experiments/httpsd.py.patch?format=raw -O httpsd.py.patch
patch httpsd.py httpsd.py.patch
rm httpsd.py.patch

cd ~/gigaweb/docroot
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

cd ~/gigaweb
openssl genrsa -passout pass:localhost -des3 -rand /dev/urandom -out localhost.localdomain.key 1024
openssl req -subj /CN=localhost.localdomain -passin pass:localhost -new -key localhost.localdomain.key -out localhost.localdomain.csr
openssl x509 -passin pass:localhost -req -days 3650 -in localhost.localdomain.csr -signkey localhost.localdomain.key -out localhost.localdomain.crt
openssl rsa -passin pass:localhost -in localhost.localdomain.key -out decrypted.localhost.localdomain.key
mv -f decrypted.localhost.localdomain.key localhost.localdomain.key
cat localhost.localdomain.key localhost.localdomain.crt > localhost.localdomain.pem
rm localhost.localdomain.key localhost.localdomain.crt localhost.localdomain.csr

Commands run on each server

server=<ipaddr>
cd ~/gigaweb/docroot
python ../httpsd.py $server 4107

Commands run on each client

server=<ipaddr>
rm -rf ~/gigaweb
mkdir ~/gigaweb
cd ~/gigaweb
for i in {1..30} ; do wget --no-check-certificate https://$server:4107/substrate.doc -O substrate.doc.$i ; done
du -sb .
md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."

Round 1

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 2

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

planetlab5.clemson.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode1.cip.gatech.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

plastic-108

GigaWeb, using count=40, port=4108, file=substrate.doc, md5sum=d4fcf71833327fbfef98be09deef8bfb, and this table of client/server pairs:

client server server address
wings-openflow-3.wail.wisc.edu orbitplc1.orbit-lab.org server=10.42.108.111
orbitplc2.orbit-lab.org pl5.myplc.grnoc.iu.edu server=10.42.108.73
pl4.myplc.grnoc.iu.edu wings-openflow-2.wail.wisc.edu server=10.42.108.95

One-time prep commands run on each server

sudo yum -y install pyOpenSSL patch
rm -rf ~/gigaweb
mkdir -p ~/gigaweb/docroot

cd ~/gigaweb
wget http://code.activestate.com/recipes/442473-simple-http-server-supporting-ssl-secure-communica/download/1/ -O httpsd.py
wget http://groups.geni.net/geni/attachment/wiki/PlasticSlices/Experiments/httpsd.py.patch?format=raw -O httpsd.py.patch
patch httpsd.py httpsd.py.patch
rm httpsd.py.patch

cd ~/gigaweb/docroot
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

cd ~/gigaweb
openssl genrsa -passout pass:localhost -des3 -rand /dev/urandom -out localhost.localdomain.key 1024
openssl req -subj /CN=localhost.localdomain -passin pass:localhost -new -key localhost.localdomain.key -out localhost.localdomain.csr
openssl x509 -passin pass:localhost -req -days 3650 -in localhost.localdomain.csr -signkey localhost.localdomain.key -out localhost.localdomain.crt
openssl rsa -passin pass:localhost -in localhost.localdomain.key -out decrypted.localhost.localdomain.key
mv -f decrypted.localhost.localdomain.key localhost.localdomain.key
cat localhost.localdomain.key localhost.localdomain.crt > localhost.localdomain.pem
rm localhost.localdomain.key localhost.localdomain.crt localhost.localdomain.csr

Commands run on each server

server=<ipaddr>
cd ~/gigaweb/docroot
python ../httpsd.py $server 4108

Commands run on each client

server=<ipaddr>
rm -rf ~/gigaweb
mkdir ~/gigaweb
cd ~/gigaweb
for i in {1..40} ; do wget --no-check-certificate https://$server:4108/substrate.doc -O substrate.doc.$i ; done
du -sb .
md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."

Round 1

Results

wings-openflow-3.wail.wisc.edu:

+$ server=10.42.108.90

+$ for i in {1..30} ; do wget --no-check-certificate https://$server:4108/substrate.doc -O substrate.doc.$i ; done
--2011-05-26 17:25:36--  https://10.42.108.90:4108/substrate.doc
Connecting to 10.42.108.90:4108... connected.
^C

of-planet2.stanford.edu:

+$ server=10.42.108.111

+$ for i in {1..30} ; do wget --no-check-certificate https://$server:4108/substrate.doc -O substrate.doc.$i ; done
--2011-05-26 17:25:28--  https://10.42.108.111:4108/substrate.doc
Connecting to 10.42.108.111:4108... failed: Connection timed out.

orbitplc2.orbit-lab.org:

+$ server=10.42.108.73

+$ for i in {1..30} ; do wget --no-check-certificate https://$server:4108/substrate.doc -O substrate.doc.$i ; done
--2011-05-26 13:22:22--  https://10.42.108.73:4108/substrate.doc
Connecting to 10.42.108.73:4108... failed: Connection timed out.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
254626816       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

Everything failed except Indiana to Wisconsin, but that one worked well.

Round 2

Results

wings-openflow-3.wail.wisc.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc2.orbit-lab.org:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

wings-openflow-3.wail.wisc.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc2.orbit-lab.org:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

wings-openflow-3.wail.wisc.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc2.orbit-lab.org:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 5

Results

wings-openflow-3.wail.wisc.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc2.orbit-lab.org:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

wings-openflow-3.wail.wisc.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc2.orbit-lab.org:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
339501056       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

plastic-109

GigaNetcat, using count=25, port=6109, file=substrate.doc, and this table of client/server pairs:

client server server address
navis.gpolab.bbn.com pl5.myplc.grnoc.iu.edu server=10.42.109.73
pl4.myplc.grnoc.iu.edu pl02.cs.washington.edu server=10.42.109.81
pl01.cs.washington.edu planetlab5.clemson.edu server=10.42.109.105
planetlab4.clemson.edu wings-openflow-3.wail.wisc.edu server=10.42.109.96
wings-openflow-2.wail.wisc.edu ganel.gpolab.bbn.com server=10.42.109.51

One-time prep commands run on each server

sudo yum -y install nc
mkdir -p ~/giganetcat
cd ~/giganetcat
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

One-time prep commands run on each client

sudo yum -y install nc

Commands run on each server

server=<ipaddr>
cd ~/giganetcat
for i in {1..25} ; do nc -l $server 6109 < substrate.doc ; echo "completed transfer #$i" ; md5sum substrate.doc ; done

Commands run on each client

server=<ipaddr>
rm -rf ~/giganetcat
mkdir ~/giganetcat
cd ~/giganetcat
for i in {1..25} ; do nc $server 6109 > substrate.doc ; echo "completed transfer #$i" ; md5sum substrate.doc ; mv substrate.doc substrate.doc.$i ; done
du -sb .
md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."

Round 1

Results

navis.gpolab.bbn.com:

+$ du -sb .
169752576       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
169752576       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
4096    .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.10
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.11
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.12
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.13
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.14
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.15
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.16
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.17
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.18
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.19
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.20
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.8
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.9

planetlab4.clemson.edu:

+$ du -sb .
5544    .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
cd78ddbe122d455a37e47204d21a93d2  substrate.doc

of-planet2.stanford.edu:

+$ du -sb .
8491520 .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc

wings-openflow-2.wail.wisc.edu:

+$ for i in {1..20} ; do nc $server 6109 > substrate.doc ; echo "completed transfer #$i" ; md5sum substrate.doc ; mv substrate.doc substrate.doc.$i ; done
completed transfer #1
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #2
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #3
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #4
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #5
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #6
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #7
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #8
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #9
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #10
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #11
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #12
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #13
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #14
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #15
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #16
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #17
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #18
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #19
d4fcf71833327fbfef98be09deef8bfb  substrate.doc
completed transfer #20
d4fcf71833327fbfef98be09deef8bfb  substrate.doc

Analysis

Washington to Clemson failed because Clemson didn't actually have the file to serve, so it quickly sent twenty zero-length files. Clemson to Stanford just failed. Stanford to Wisconsin died partway through the first transfer. Wisconsin to BBN worked fine, but we didn't capture the du and md5sum output, so we've listed the transfer log here.

Round 2

Results

navis.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

planetlab4.clemson.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

wings-openflow-2.wail.wisc.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

navis.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

planetlab4.clemson.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

wings-openflow-2.wail.wisc.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

navis.gpolab.bbn.com:

+$ du -sb .
84878336        .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.10
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.11
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.12
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.13
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.14
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.15
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.8
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.9

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

planetlab4.clemson.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

wings-openflow-2.wail.wisc.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

On navis.gpolab.bbn.com, we accidentally started the client before starting the server, so it created a bunch of zero-length files before the server started transmitting. All other results seem consistent with what we'd expect.

Round 5

Results

navis.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

planetlab4.clemson.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

wings-openflow-2.wail.wisc.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 6

Results

navis.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl4.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl01.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

planetlab4.clemson.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

wings-openflow-2.wail.wisc.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

plastic-110

GigaNetcat, using count=25, port=6110, file=substrate.doc, and this table of client/server pairs:

client server server address
gardil.gpolab.bbn.com pl01.cs.washington.edu server=10.42.110.80
pl02.cs.washington.edu orbitplc2.orbit-lab.org server=10.42.110.112
orbitplc1.orbit-lab.org pl4.myplc.grnoc.iu.edu server=10.42.110.72
pl5.myplc.grnoc.iu.edu plnode1.cip.gatech.edu server=10.42.110.100
plnode2.cip.gatech.edu sardis.gpolab.bbn.com server=10.42.110.53

One-time prep commands run on each server

sudo yum -y install nc
mkdir -p ~/giganetcat
cd ~/giganetcat
wget http://groups.geni.net/geni/attachment/wiki/DeliverablePage/Spiral1%20substrate%20catalog.doc?format=raw -O substrate.doc

One-time prep commands run on each client

sudo yum -y install nc

Commands run on each server

server=<ipaddr>
cd ~/giganetcat
for i in {1..25} ; do nc -l $server 6110 < substrate.doc ; echo "completed transfer #$i" ; md5sum substrate.doc ; done

Commands run on each client

server=<ipaddr>
rm -rf ~/giganetcat
mkdir ~/giganetcat
cd ~/giganetcat
for i in {1..25} ; do nc $server 6110 > substrate.doc ; echo "completed transfer #$i" ; md5sum substrate.doc ; mv substrate.doc substrate.doc.$i ; done
du -sb .
md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."

Round 1

Results

gardil.gpolab.bbn.com:

+$ du -sb .
169752576       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl02.cs.washington.edu:

+$ du -sb .
8495016 .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
2c43a5dd0efdeb2ce92381d245ec0081  substrate.doc

of-planet2.stanford.edu:

+$ du -sb .
4096    .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.10
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.11
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.8
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.9

orbitplc1.orbit-lab.org:

+$ du -sb .
4096    .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.10
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.11
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.8
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.9

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
169752576       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
169752576       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

BBN to Washington worked fine, but Washington to Stanford died during the second transfer. Stanford to Rutgers didn't work at all.

Round 2

Results

gardil.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl02.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc1.orbit-lab.org:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 3

Results

gardil.gpolab.bbn.com:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl02.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc1.orbit-lab.org:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

All results seem consistent with what we'd expect.

Round 4

Results

gardil.gpolab.bbn.com:

+$ du -sb .
152777728       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7

pl02.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc1.orbit-lab.org:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

On gardil.gpolab.bbn.com, we accidentally started the client before starting the server, so it created several zero-length files before the server started transmitting. All other results seem consistent with what we'd expect.

Round 5

Results

gardil.gpolab.bbn.com:

+$ du -sb .
152777728       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.1
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.2
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.3
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.5
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.6
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.7

pl02.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc1.orbit-lab.org:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

On gardil.gpolab.bbn.com, we accidentally started the client before starting the server, so it created several zero-length files before the server started transmitting. All other results seem consistent with what we'd expect.

Round 6

Results

gardil.gpolab.bbn.com:

+$ du -sb .
203702272       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
d41d8cd98f00b204e9800998ecf8427e  substrate.doc.4

pl02.cs.washington.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

orbitplc1.orbit-lab.org:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

pl5.myplc.grnoc.iu.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

plnode2.cip.gatech.edu:

+$ du -sb .
212189696       .

+$ md5sum * | grep -v d4fcf71833327fbfef98be09deef8bfb || echo "All checksums match."
All checksums match.

Analysis

gardil.gpolab.bbn.com got one zero-length file for some reason; nothing obvious in the server-side log (not quoted here) to explain it. All other results seem consistent with what we'd expect.

Last modified 9 years ago Last modified on 06/07/11 11:27:02