diff options
| author | mo khan <mo@mokhan.ca> | 2025-09-15 18:42:58 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-09-15 18:42:58 -0600 |
| commit | cfda5547b98bd026e3d47b25c490c883a6098603 (patch) | |
| tree | 30641f947967f6e7d6ead26ff462613f42df8ef4 | |
| parent | 0d8fb420061fdf64c7dee2bd0d916b3074511f03 (diff) | |
simplify 1.1
| -rw-r--r-- | assignments/1/README.md | 87 |
1 files changed, 15 insertions, 72 deletions
diff --git a/assignments/1/README.md b/assignments/1/README.md index 8ea75bc..abd5d5a 100644 --- a/assignments/1/README.md +++ b/assignments/1/README.md @@ -29,11 +29,16 @@ If you are not familiar with the utility, read the Microsoft article, Traceroute was run from my computer to google.com at three different times with the following results: -| Measurement | Time | # of Hops | Average RTT (ms) | Standard Deviation (ms) | -| ----------- | ---- | --------- | ---------------- | ------------------ | -| 1 | 14:34 | 13 | 34.34 | 25.61 | -| 2 | 14:39 | 8 | 15.87 | 9.13 | -| 3 | 15:08 | 8 | 15.36 | 9.12 | +| Measurement | Time | # of Hops | End-to-End RTT (ms) | +| ----------- | ---- | --------- | ------------------ | +| 1 | 14:34 | 13 | 61.43 | +| 2 | 14:39 | 8 | 20.85 | +| 3 | 15:08 | 8 | 21.51 | + +RTT Statistics: + +- Average RTT: 34.60 ms +- Standard Deviation: 23.24 ms ### Trace 1 @@ -63,24 +68,6 @@ traceroute to google.com (142.251.32.78), 64 hops max, 40 byte packets 13 yyz12s07-in-f14.1e100.net (142.251.32.78) 36 bytes to 192.168.0.139 61.941 ms 61.323 ms 61.030 ms ``` -| Hop | RTT | RTT | RTT | Total | -| --- | --- | --- | --- | ----- | -| 1 | 2.891 | 0.843 | 0.68 | 4.412 | -| 2 | 3.086 | 2.069 | 1.8181 | 6.972999999999999 | -| 3 | - | - | - | - | -| 4 | 21.470 | 20.441 | 20.212 | 62.123000000000005 | -| 5 | - | - | - | - | -| 6 | 20.595 | 21.655 | 21.378 | 63.628 | -| 7 | 21.586 | 20.42 | 39.592 | 81.598 | -| 8 | - | - | 27.783 | 27.783 | -| 9 | - | - | - | - | -| 10 | 62.220 | 63.230 | - | 125.44999999999999 | -| 11 | 61.495 | 60.968 | 63.083 | 175.546 | -| 12 | 61.120 | 62.039 | 62.104 | 185.26299999999998 | -| 13 | 61.941 | 61.323 | 61.030 | 184.294 | -| --- | --- | --- | --- | ----- | -| | | | | 927.0721000000001 | - ### Trace 2 ```bash @@ -102,19 +89,6 @@ traceroute to google.com (142.251.215.238), 64 hops max, 40 byte packets sea09s35-in-f14.1e100.net (142.251.215.238) 36 bytes to 192.168.0.139 21.078 ms 20.483 ms ``` -| Hop | RTT | RTT | RTT | Total | -| --- | --- | --- | --- | ----- | -| 1 | 2.186 | 0.819 | 0.638 | 3.643 | -| 2 | 2.045 | 2.458 | 2.077 | 6.580 | -| 3 | - | - | - | - | -| 4 | 21.523 | 20.465 | 20.087 | 62.075 | -| 5 | - | - | - | - | -| 6 | 22.008 | 21.601 | 21.618 | 65.227 | -| 7 | 20.923 | 20.663 | 20.712 | 62.298 | -| 8 | 21.585 | 21.078 | 20.483 | 63.146 | -| --- | --- | --- | --- | ----- | -| | | | | 262.969| - ### Trace 3 ```bash @@ -135,44 +109,13 @@ traceroute to google.com (142.251.215.238), 64 hops max, 40 byte packets 172.253.79.231 (172.253.79.231) 76 bytes to 192.168.0.139 22.211 ms 21.499 ms ``` -| Hop | RTT | RTT | RTT | Total | -| --- | --- | --- | --- | ----- | -| 1 | 1.760 | 0.894 | 0.696 | 3.350 | -| 2 | 2.094 | 2.604 | 2.097 | 6.795 | -| 3 | - | - | - | - | -| 4 | 21.375 | 20.245 | 20.038 | 61.658 | -| 5 | - | - | - | - | -| 6 | 21.347 | 20.090 | 21.977 | 63.414 | -| 7 | 20.924 | 21.603 | 21.117 | 63.644 | -| 8 | 20.809 | 22.211 | 21.499 | 64.519 | -| --- | --- | --- | --- | ----- | -| | | | | 263.380| - ### Analysis -The traceroute measurements reveal several important network characteristics: - -* Round-Trip Time Analysis - - Measurement 1 (14:34): Highest average RTT (34.34 ms) with largest standard deviation (25.61 ms), indicating significant network variability - - Measurements 2 & 3 (14:39, 15:08): Similar performance with averages around 15.4 ms and standard deviations around 9.1 ms, showing more stable conditions -* Router Path Analysis - - Measurement 1: 13 hops - took a longer path through Google's network infrastructure - - Measurements 2 & 3: 8 hops - more direct routing to the same destination IP (142.251.215.238) - - The hop count reduction suggests load balancing and route optimization occurred between measurements -* Network Behavior Patterns - - Initial measurement showed higher latency and variability, possibly due to: - - Cold cache effects - - Different routing through Google's CDN - - Network congestion at that time - - Subsequent measurements benefited from optimized routing and reduced congestion - - The consistent performance in measurements 2 and 3 indicates stable network conditions during that timeframe - -Key Findings: - -1. Route Optimization: Google's network dynamically selected shorter paths for better performance -2. Time of Day Effects: Network performance improved over the 30-minute measurement window -3. Latency Consistency: Later measurements showed lower variability, indicating more predictable performance -4. Load Balancing: Different destination IPs (142.251.32.78 vs 142.251.215.238) demonstrate Google's distributed infrastructure +The traceroute runs show different destination IPs due to Google's +load balancing. Trace 1 took longer (61ms, 13 hops) while Traces +2-3 were faster (21ms, 8 hops), indicating route optimization. The +`* * *` entries show routers filtering ICMP traffic, which is normal +behavior. ## 1.2 Internet Protocol Stack Layers (5%) |
