The test consists of sending a stream of 100 packets, either back to back,
or, if one should not return, waiting 10ms and *then* sending the next
one. Packets follow the same trend as traceroute -- UDP to an unreachable
port. Thanks go to Eric for whipping out the Unix code to do this.
Insofar as impact on the original study, this does not appear to affect
the latency numbers, as the rate limiting does not delay packets, it
simply refuses to send them.
#failures - 10
128.196.128.4 responses: 3
169.226.4.58 responses: 2
18.72.0.47 responses: 3
200.15.3.10 responses: 2
204.59.152.196 responses: 2
205.158.5.58 responses: 2
205.227.188.102 responses: 2
206.142.248.46 responses: 2
206.190.139.1 responses: 2
206.58.0.45 responses: 2
#successes - 35
128.2.72.150 responses: 63
128.32.206.66 responses: 68
128.95.4.144 responses: 79
134.79.18.11 responses: 65
140.142.50.5 responses: 95
144.92.219.49 responses: 55
18.72.0.176 responses: 61
192.188.149.14 responses: 71
192.41.25.46 responses: 71
198.202.75.101 responses: 59
199.1.13.15 responses: 57
204.119.27.10 responses: 81
204.194.12.75 responses: 75
204.245.228.1 responses: 77
204.251.174.179 responses: 23
205.138.138.2 responses: 61
205.142.28.7 responses: 59
205.159.88.19 responses: 57
205.177.25.9 responses: 52
205.197.248.25 responses: 63
205.240.28.15 responses: 77
205.246.67.208 responses: 64
206.161.109.15 responses: 52
206.170.175.1 responses: 64
206.205.230.81 responses: 58
206.240.130.2 responses: 54
206.66.160.2 responses: 37
207.106.34.200 responses: 61
207.126.97.22 responses: 69
207.34.3.1 responses: 56
207.43.170.13 responses: 68
207.67.247.6 responses: 75
208.206.176.12 responses: 64
209.130.129.196 responses: 57
209.98.98.20 responses: 64
#weirdo. works fine with traceroute,
#but inconsistent with hping
192.75.213.193 responses: 6
192.75.213.193 responses: 48
#invalid -- IP not responding
207.254.1.13 responses: 0
192.41.37.39 responses: 0