Showing posts with label module 1. Show all posts
Showing posts with label module 1. Show all posts

Sunday, December 14, 2008

Module 1 - Internet Tools Task

As this tasks concept points out the keystone foundation to the internet is the system of identifying a location and routing data between two fixed end points. With out the ability to do this the internet as we now know it would simply not exist.

Previously I have used Traceroute and other internet tools when building websites and determining which hosting company to go with. I suppose this makes me relatively familiar with the tool and the information that it provides. Never less, I thought a little background research to broaden my understanding of the underlying concept would not hurt.

To complete this particular task I had to complete a Traceroute inquiry via either network-tools.com or centralops.net: I choose to do both to see what, if any, differences would present between the two tools. And besides, it's not like it takes hours to complete a Traceroute inquiry.

The Results
Results from Network-Tools took around 260ms with the last three hops timing out once the packets hit the Curtin network.

Results from Centralops came it at 253ms with the last three hops again timing out once they hit the Curtin network.

Neither of the actual results surprised me as both tools are located offshore. What did surprise me was that both times the last three hops timed out. I hav read that this could be due to packet loss or the network protecting itself as a Traceroute is similar to port sniffing.

Incidentally, the IP address for curtin.edu.au is 134.7.179.53

Ping
For those mildly interested, like nearly every other word within the world of IT, Ping is actually an acronym for Packet Internet Groper (sounds dodgy eh). Ping is used to see if an address on the internet is active an accepting data and it's latency, when pinging curtin.edu.au from the online tools the following was yielded.

The Results
Results from both online sources were approximately the same as the Traceroute results coming in at 260.2ms and 253ms respectivly. This was to be expected as data is still being sent via the same route as in the Traceroute. The major difference here is that a Ping is not recording all hops or resolving domain names. This would explain why Ping results will appear on the page quicker.

From My Local Machine
In further exploration for this task I have done as suggested and utilised the software WhatRoute, directly downloaded to my local machine. I also have used OS X's bundled application, Network Utility, to complete this final piece.

The Results
Results were as expected with response times nearly half that of the online tools, 104ms with traceroute (although both my attempts seem to have completely died when reaching the Curtin network) and 110ms when pinging.

The key takeout to me from this is that location is everything when it comes to speed on the internet. Obviously the closer you are to your destination the quicker it will be to get there. Though the one caveat that I throw in is; you have no actual control on just how your data will be routed. Take my last image for example. My ISP Exetel routes all data through Sydney before shooting me off to Perth and Curtin's network. Is this something that has an effect?

I'm not entirely sure but logic says that going to Perth via Sydney isn't the shortest route and it allows more opportunity for error.

Friday, December 12, 2008

Module 1 - File Transfer Protocol (FTP) Task

So to get the obvious out of the way first, CAPITALIZATION MATTERS! Right, now we have done that, let us continue.

To complete this task I was required to login to the Curtin FTP server using the anonymous login. After successfully doing this I was to then check the directory structure and find the readme.txt. From this file I would find the statement in my posts first sentence, this would fill in the blank from the sentence:

"according to the readme file, '_______ MATTERS'".

I thought the word was going to be SIZE, who would of thunk it eh? ;)

FTP or File Transfer Protocol is my main method of transferring data to and from my websites. I use FTP at least once a week with my personal websites uploading files or downloading backups to my local drive. I also use FTP for renaming files and directories and changing permissions if needed. To do this on a Mac I use the absolutely fantastic Yummy FTP from Yummy Software, it's so simple!

I also currently utilise FTP as a distribution method to obtain files from various different websites and business. As a working DJ I have been in the lucky situation to receive promo records from music labels, over the years I have seen this change to the point now where most labels no longer send records or even CD's; they simply point you to their FTP server and you download all the digital files. Much quicker and cost effective. Who said the record labels weren't utilising new distribution methods.

Of course now their are even more advanced methods of transferring electronic media, but that is a subject for another time.

Thursday, December 11, 2008

Module 1 - Telnet Task B

So as the Star Wars fan that I am, I was quite excited to telnet into towel.blinkenlighs.nl. Of course after after reading my fellow students blogs I was ready for what was in store, and let me say, once in I wasn't disappointed.

For the uninitiated; telnetting into towel.blinkenlights.nl gives you an ASCII art animation of Star Wars Episode 4 A New Hope. Thats right baby, welcome to geekville!

ASCII art is is made from ASCII and is one of those terribly geek things to do. Originally created in the
late 60's it took off in the 70's and 80's allowing people to create images and share them when bandwidth was limited and printers couldn't create the photo realistic prints we can today.

While bandwidth today is cheap and expansive and printers can run of high quality photos, I don't think something such as ASCII art will ever completely leave us, apparently it's been around in one form or another since the birth of the typewriter. For me ASCII art is an important part of computing and the internets history, and while no longer part of the mainstream (was it ever) we still use common forms of ASCII art day in, day out.

In fact one form which you may well be familiar with is the simple emoticon :-) This simple form of ASCII art was first created in 1982 and is still helping us communicate feelings and moods.

I suggest having a further look at ASCII art and if you get inspired then have a go at creating some of your own either by hand or if you wish, you can auto generate it.

Tuesday, December 9, 2008

Module 1 - Telnet Task A

This task required me to utilise Telnet to access the Deakin University library and complete a search.

Before jumping in head first, the first thing I did was to Google a little more information on Telnet and Telnet applications on the Mac. I came across a couple of good sites in particular I found this excellent and simple guide on wikiHow.com. The site also contained some further How To's on checking email with Telnet and the like, but I digress.

After my research, I decided in the end to go down the route of using Mac OS X's built in Telnet client; the Terminal application. Terminal is an application which I am familiar and comfortable with so using it for this task was rather simple.

Logging in to the Deakin library and completing the search was very straight forward. I found that the information presented through Telnet was sparse yet effective, giving me all the details to find the books in the actual library. On further exploration I found that there were a number of features which further helped enhance the search.

While this particular search method was effective and extremely quick, it was frustrating to not have a visual reference or even advanced search options that we take for granted with graphical interfaces. Telnet also lacked any feature for me to check out or borrow a book as many modern web based library interfaces now do. It is from this perspective I found the experience seriously lacking, as I was unable to self serve as I have grown used to on the internet.

This task has given me further understanding of some of the underlying technologies of the internet and their evolution. It was interesting to find that the Telnet protocol was developed in 1969 and while in limited use today, it still has some practical uses as a troubleshooting tool for remote servers and as another resource to search for information.