The following are the outputs of two old runs of the
traceroute command, one looking from Bendigo towards the
rest of the lnternet via La Trobe, Bundoora, and the other from
outside La Trobe looking towards Bendigo.
Note that the traceroute output given in the lecture shows an up-to-date
representation of the structure of the Internet in the region of
La Trobe University.
12 ltu.gw.au ( 139.130.8.2) 252 ms 273 ms 123 ms
13 149.144.1.2 (149.144.1.2) 398 ms 149 ms 273 ms
14 r-itsbgo.bendigo.latrobe.edu.au (149.144.2.254) 531 ms * 408 ms
15 busfddi0.bendigo.latrobe.edu.au (149.144.10.1) 244 ms * 273 ms
16 ironbark (149.144.20.60) 316 ms 279 ms 480 ms
1 149.144.20.254(149.144.20.254) 3ms 3ms 3ms
2 itsfddi0.bendigo.latrobe.edu.au (149.144.10.254) 3 ms 4 ms 5 ms
3 r-bgowan.bendigo.latrobe.edu.au (149.144.2.1) 6 ms 4 ms 10 ms
4 Itu.gw.au 149.144.1.1 (149.144.1.1) 36 ms 32 ms 32 ms
5 national.gw.au(139.130.8.1) 269ms 304ms 297ms
- Can you see where the large delays occur in datagram delivery?
- Use this information to draw a diagram of the topology of the
Internet in our region at the time these traceroutes were run. You
should show IP addresses of the various interfaces involved, and
possibly network and subnet numbers (although these may only be a
guess, since we don't know the subnet masks which are in use).
- How has the structure of the 'net changed since this traceroute
was run?