diff options
| author | mo khan <mo@mokhan.ca> | 2025-09-27 22:23:51 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-09-27 22:23:51 -0600 |
| commit | e861dc559881ce7c4eb09f1d6360e69790c742cb (patch) | |
| tree | c8b5aabfa0b80f5422f7a0f9a2a1ec4f7720c5fe /assignments/1 | |
| parent | d189e5e3c61b9d4aa9715b1f2017131034a77466 (diff) | |
update numbers
Diffstat (limited to 'assignments/1')
| -rw-r--r-- | assignments/1/README.md | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/assignments/1/README.md b/assignments/1/README.md index 266cfb6..34bb1c7 100644 --- a/assignments/1/README.md +++ b/assignments/1/README.md @@ -35,6 +35,7 @@ Summary (using hop 7 as last responding hop): - Average RTT across runs: (18.50 + 18.92 + 18.88) / 3 = 18.77 ms - Standard deviation (sample): ~0.23 ms +- Number of routers observed in the path: at least 7 (later hops did not reply due to filtering) - Note: These RTTs are for the last responding hop (Telus backbone node). The destination and later hops likely rate-limit or drop probes; this is common. Full traceroute outputs @@ -265,11 +266,15 @@ a) Number of packets b) Links (via traceroute) - Answer: In all three traces to www.athabascau.ca, the last responding hop was 7 (Telus backbone). Later hops filtered probes, so the total hop count to the destination could not be observed with ICMP/UDP traceroute. +- Responding hops seen (from Run 1): + 1) 192.168.0.1 (home router) + 2) 10.139.230.1 (ISP gateway) + 7) 154.11.15.105/154.11.15.107 (Telus backbone) c) Speed for each identified link - Answer (best estimate): - Home Wi-Fi/access uplink: measured average upload ~430 Mb/s (local bottleneck when sending) - - ISP/regional/backbone: typically >= 1–10 Gb/s + - ISP/regional/backbone: typically >= 1-10 Gb/s - Reason: Per-link bandwidth cannot be inferred from traceroute RTT; we use measured access speeds and typical provider capacities. d) Time when the last packet enters the first link @@ -278,8 +283,8 @@ d) Time when the last packet enters the first link - Answer: t0 + 0.188 s (approx) e) Time when the last packet arrives at the server -- Add ~50–60 ms for propagation/processing: 0.188 s + 0.050–0.060 s ~ 0.238–0.248 s -- Answer: about t0 + 0.24–0.25 s +- Add ~10-20 ms for propagation/processing (consistent with ~18.8 ms RTT to the last responding hop): 0.188 s + 0.010-0.020 s ~ 0.198-0.208 s +- Answer: about t0 + 0.20-0.21 s ## 2.2 Propagation Delay and Bandwidth-Delay Product (20%) |