diff options
| author | mo khan <mo@mokhan.ca> | 2025-09-15 15:12:45 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-09-15 15:12:45 -0600 |
| commit | 629dbebddaf205e0e777a94139ea692921bd1d00 (patch) | |
| tree | ec41a972894d159249c0dac576a99475b8dfface | |
| parent | 716d22292f5078476dd1b086e5e65a14d88d3d8a (diff) | |
chore: update question 1
| -rw-r--r-- | assignments/1/README.md | 172 | ||||
| -rwxr-xr-x | assignments/1/bin/trace | 6 |
2 files changed, 162 insertions, 16 deletions
diff --git a/assignments/1/README.md b/assignments/1/README.md index 42825a8..f328cc9 100644 --- a/assignments/1/README.md +++ b/assignments/1/README.md @@ -7,27 +7,167 @@ Student ID: 3431709 ## Part 1: Short Answer Questions (30%) ### 1.1 Traceroute Analysis (5%) -> Run Traceroute, TRACERT (on Windows), or another similar utility between a source and a destination in the country in which you reside. Do this at three different times of the day. Summarize your findings at each of the times with respect to the following, and explain your findings: -> average and standard deviation of the round-trip delays -> number of routers in the path -> If you are not familiar with the utility, read the Microsoft article, “How to Use TRACERT .” +``` +Run Traceroute, TRACERT (on Windows), or another similar utility +between a source and a destination in the country in which you +reside. Do this at three different times of the day. Summarize your +findings at each of the times with respect to the following, and +explain your findings: -Traceroute was run from my computer to google.com at three different times with the following results: +* average and standard deviation of the round-trip delays +* number of routers in the path -| Measurement | Time | Number of Hops | Average RTT (ms) | Standard Deviation (ms) | -|-------------|------|----------------|------------------|-------------------------| -| 1 | [Time 1] | 14 | 51.2 | 47.8 | -| 2 | [Time 2] | 14 | 41.7 | 23.1 | -| 3 | [Time 3] | 14 | 39.4 | 21.9 | +If you are not familiar with the utility, read the Microsoft article, +"How to Use TRACERT." +``` -#### Analysis: +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 | + +Trace 1: + +```bash +$ traceroute -v google.com +Using interface: en9 +traceroute to google.com (142.251.32.78), 64 hops max, 40 byte packets + 1 unifi (192.168.0.1) 48 bytes to 192.168.0.139 2.891 ms 0.843 ms 0.678 ms + 2 10.139.230.1 (10.139.230.1) 48 bytes to 192.168.0.139 3.086 ms 2.069 ms 1.818 ms + 3 * * * + 4 209.85.174.62 (209.85.174.62) 48 bytes to 192.168.0.139 21.470 ms 20.441 ms 20.212 ms + 5 * * * + 6 142.251.55.202 (142.251.55.202) 48 bytes to 192.168.0.139 20.595 ms + 142.250.225.216 (142.250.225.216) 76 bytes to 192.168.0.139 21.655 ms + 142.250.233.152 (142.250.233.152) 76 bytes to 192.168.0.139 21.378 ms + 7 108.170.255.130 (108.170.255.130) 76 bytes to 192.168.0.139 21.586 ms + 142.251.249.236 (142.251.249.236) 36 bytes to 192.168.0.139 20.742 ms + 108.170.255.132 (108.170.255.132) 36 bytes to 192.168.0.139 39.592 ms + 8 * * 216.239.51.199 (216.239.51.199) 148 bytes to 192.168.0.139 27.783 ms + 9 * * * +10 * 142.251.234.79 (142.251.234.79) 36 bytes to 192.168.0.139 62.220 ms + 172.253.64.253 (172.253.64.253) 36 bytes to 192.168.0.139 63.230 ms +11 142.251.234.79 (142.251.234.79) 36 bytes to 192.168.0.139 61.495 ms 60.968 ms + 192.178.98.125 (192.178.98.125) 76 bytes to 192.168.0.139 63.083 ms +12 142.251.68.25 (142.251.68.25) 48 bytes to 192.168.0.139 61.120 ms + 192.178.98.123 (192.178.98.123) 76 bytes to 192.168.0.139 62.039 ms 62.104 ms +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 +$ traceroute -v google.com +Using interface: en9 +traceroute to google.com (142.251.215.238), 64 hops max, 40 byte packets + 1 unifi (192.168.0.1) 48 bytes to 192.168.0.139 2.186 ms 0.819 ms 0.638 ms + 2 10.139.230.1 (10.139.230.1) 48 bytes to 192.168.0.139 2.045 ms 2.458 ms 2.077 ms + 3 * * * + 4 209.85.174.62 (209.85.174.62) 48 bytes to 192.168.0.139 21.523 ms 20.465 ms 20.087 ms + 5 * * * + 6 142.250.225.216 (142.250.225.216) 76 bytes to 192.168.0.139 22.008 ms + 142.251.55.200 (142.251.55.200) 76 bytes to 192.168.0.139 21.601 ms + 142.250.233.152 (142.250.233.152) 76 bytes to 192.168.0.139 21.618 ms + 7 192.178.105.146 (192.178.105.146) 36 bytes to 192.168.0.139 20.923 ms + 142.251.250.56 (142.251.250.56) 36 bytes to 192.168.0.139 20.663 ms + 142.251.241.137 (142.251.241.137) 48 bytes to 192.168.0.139 20.712 ms + 8 172.253.79.231 (172.253.79.231) 76 bytes to 192.168.0.139 21.585 ms + 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 +$ traceroute -v google.com +Using interface: en9 +traceroute to google.com (142.251.215.238), 64 hops max, 40 byte packets + 1 unifi (192.168.0.1) 48 bytes to 192.168.0.139 1.760 ms 0.894 ms 0.696 ms + 2 10.139.230.1 (10.139.230.1) 48 bytes to 192.168.0.139 2.094 ms 2.604 ms 2.097 ms + 3 * * * + 4 209.85.174.62 (209.85.174.62) 48 bytes to 192.168.0.139 21.375 ms 20.245 ms 20.038 ms + 5 * * * + 6 142.251.55.202 (142.251.55.202) 48 bytes to 192.168.0.139 21.347 ms 20.090 ms + 142.251.224.250 (142.251.224.250) 76 bytes to 192.168.0.139 21.977 ms + 7 216.239.56.223 (216.239.56.223) 48 bytes to 192.168.0.139 20.924 ms + 108.170.255.196 (108.170.255.196) 36 bytes to 192.168.0.139 21.603 ms + 142.251.249.236 (142.251.249.236) 36 bytes to 192.168.0.139 21.117 ms + 8 sea09s35-in-f14.1e100.net (142.251.215.238) 36 bytes to 192.168.0.139 20.809 ms + 172.253.79.231 (172.253.79.231) 76 bytes to 192.168.0.139 22.211 ms 21.499 ms +``` -- Number of routers: Consistently 14 hops across all measurements, indicating a stable routing path from source to destination. -- Round-trip delays: The first measurement showed higher average delay (51.2ms) and much higher variability (σ=47.8ms), suggesting network congestion at that time. -- Improvement over time: Subsequent measurements showed lower and more consistent delays (39.4-41.7ms average, σ=21.9-23.1ms), indicating reduced network congestion. -- Route variation: While the number of hops remained constant, different intermediate routers within Google's network were used due to load balancing. +| 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: -Explanation: The variations in delay times reflect dynamic network conditions including traffic load, routing decisions, and congestion levels. The consistent hop count suggests stable primary routing, while the delay variations demonstrate how network performance fluctuates throughout the day. +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 ### 1.2 Internet Protocol Stack Layers (5%) diff --git a/assignments/1/bin/trace b/assignments/1/bin/trace new file mode 100755 index 0000000..3bec41f --- /dev/null +++ b/assignments/1/bin/trace @@ -0,0 +1,6 @@ +#!/bin/sh +set -e + +cd "$(dirname "$0")/.." + +traceroute -v google.com |
