Module 1:Tasks

Telnet Task:

Searching for books on the Deakin library, I found 2, my result was

You searched for the AUTHOR: bennahum Deakin/Gordon:All Locations
2 AUTHORS found, with 2 entries; AUTHORS 1-2 are:

1 Bennahum David A 1936 ................................. 1 entry
2 Bennahum Ninotchka .................................... 1 entry

The title was Managed Care: financial, legal and ethical issues

...and although I think Star Wars IV is the best movie ever, the blinkenlights version left me a bit cold, although Mark Hamill's acting seemed better than the original version, the special effects just weren't up to scratch 8)

FTP Task:

Because the files are hosted on a unix platform CAPITALIZATION matters.

Traceroute Task

As ever wikipedia is a great way to start a search for info, especially if its techo related - here I tried http://en.wikipedia.org/wiki/Traceroute

From the Network-tools website, the result was:

TraceRoute to 134.7.179.10 [curtin.edu.au]
Hop (ms) (ms) (ms) IP Address Host name
1 1 0 0 66.98.244.1 gphou-66-98-244-1.ev1servers.net
2 1 1 0 66.98.241.16 gphou-66-98-241-16.ev1servers.net
3 0 0 0 66.98.240.12 gphou-66-98-240-12.ev1servers.net
4 1 1 1 129.250.11.129 ge-1-11.r03.hstntx01.us.bb.gin.ntt.net
5 2 2 2 129.250.2.228 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net
6 37 37 38 129.250.4.112 p64-1-3-0.r21.lsanca03.us.bb.gin.ntt.net
7 37 77 37 129.250.3.159 p16-1-0-0.r02.lsanca03.us.bb.gin.ntt.net
8 196 196 196 198.172.90.102 so-2-1-0.a00.lsanca02.us.ce.verio.net
9 200 200 200 202.158.194.153 so-3-2-0.bb1.b.syd.aarnet.net.au
10 212 212 212 202.158.194.33 so-2-0-0.bb1.a.mel.aarnet.net.au
11 221 221 221 202.158.194.17 so-2-0-0.bb1.a.adl.aarnet.net.au
12 248 248 248 202.158.194.5 so-0-1-0.bb1.a.per.aarnet.net.au
13 248 248 248 202.158.198.178 gigabitethernet0.er1.curtin.cpe.aarnet.net.au
14 248 248 248 202.158.198.186 gw1.er1.curtin.cpe.aarnet.net.au
15 248 248 248 134.7.250.18 -
16 248 248 248 134.7.248.65 te1-1.b309-sr.net.curtin.edu.au
17 249 248 249 134.7.179.10 prodweb1.curtin.edu.au

When I ran a traceroute from my desktop, the result was:

traceroute to curtin.edu.au (134.7.179.10), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.382 ms 4.606 ms 1.502 ms
2 202-154-95-181.people.net.au (202.154.95.181) 13.225 ms 12.906 ms 12.863 ms
3 vic-gw-cty-01-g-0-2-10.people.net.au (218.214.17.251) 12.647 ms 17.014 ms 15.978 ms
4 302-ge0-0-0.gw4.mel1.alter.net (203.166.42.121) 15.916 ms 16.646 ms 20.998 ms
5 324.at-3-0-0.xr2.mel1.alter.net (210.80.33.165) 16.242 ms 17.864 ms 15.531 ms
6 0.so-7-0-0.xt2.syd2.alter.net (210.80.32.229) 26.862 ms 29.448 ms 28.677 ms
7 so-7-0-0.br2.syd2.alter.net (210.80.33.238) 28.401 ms 30.450 ms 30.587 ms
8 gigabitethernet2-0-0.pe1.c.syd.aarnet.net.au (203.103.244.194) 27.305 ms 29.237 ms 28.692 ms
9 ge-1-0-5.bb1.b.syd.aarnet.net.au (202.158.202.22) 30.859 ms 28.385 ms 28.472 ms
10 so-2-0-0.bb1.a.mel.aarnet.net.au (202.158.194.33) 41.293 ms 41.961 ms 40.624 ms
11 so-2-0-0.bb1.a.adl.aarnet.net.au (202.158.194.17) 50.394 ms 52.110 ms 51.292 ms
12 so-0-1-0.bb1.a.per.aarnet.net.au (202.158.194.5) 79.390 ms 80.244 ms 78.246 ms
13 gigabitethernet0.er1.curtin.cpe.aarnet.net.au (202.158.198.178) 78.884 ms 77.571 ms 78.071 ms
14 gw1.er1.curtin.cpe.aarnet.net.au (202.158.198.186) 79.085 ms 76.608 ms 79.458 ms
15 134.7.250.18 (134.7.250.18) 77.598 ms 78.498 ms 74.944 ms
16 te1-1.b309-sr.net.curtin.edu.au (134.7.248.65) 76.425 ms 78.229 ms 76.618 ms

The average hop time over 16 hops was 4.788 ms.

Interesting, because a traceroute run from visualroute.visualware.com servers in the US only used 14 hops, but took 298 ms to get there... go figure.

Ping Task

I had trouble Ping'ing the actual webct site from network tools so decided to Ping the curtin.edu.au site. I got these results:

Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 249 ms
Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 248 ms
Round trip time to 134.7.179.10: 249 ms
Round trip time to 134.7.179.10: 249 ms
Round trip time to 134.7.179.10: 249 ms

Average time over 10 pings: 248.4 ms

And from my computer using Terminal I got:

64 bytes from 134.7.179.10: icmp_seq=0 ttl=244 time=79.398 ms
64 bytes from 134.7.179.10: icmp_seq=1 ttl=244 time=78.154 ms
64 bytes from 134.7.179.10: icmp_seq=2 ttl=244 time=79.432 ms
64 bytes from 134.7.179.10: icmp_seq=3 ttl=244 time=79.159 ms
64 bytes from 134.7.179.10: icmp_seq=4 ttl=244 time=81.086 ms
64 bytes from 134.7.179.10: icmp_seq=5 ttl=244 time=78.634 ms
64 bytes from 134.7.179.10: icmp_seq=6 ttl=244 time=79.073 ms
64 bytes from 134.7.179.10: icmp_seq=7 ttl=244 time=76.830 ms
64 bytes from 134.7.179.10: icmp_seq=8 ttl=244 time=78.869 ms
64 bytes from 134.7.179.10: icmp_seq=9 ttl=244 time=79.146 ms

The average time was significantly faster from my desktop, which I would expect because of the geographical difference between the two servers along with, I guess, the much lower volume of overall traffic the packets would encounter along the way. Interestingly, the difference in speeds correlate quite accurately with the differences in speed in the traceroute task - I guess that the traceroute is actually just Pinging the server anyway but also logging the servers encountered along the way.