Wednesday, December 14, 2016

Week 12

For week 12, we have learned about RIPv1 and RIPv2. It is said that internet is divided into autonomous system wherein routing is referred to Intradomain routing (inside an autonomous system) and Interdomain routing (between autonomous system). 3 popular routing protocols:

  • Routing Information Protocol (RIP)
  • Open Shortest Path First (OSPF)
  • Border Gateway Protocol (BGP)
To fully understand distance vector routing, you just need to follow the following: initialization, sharing and updating. Common problem about distance vector routing is instability or two-node loop instability. But it has solution to solve the problem which is defining infinity, split horizon and split horizon and poison reverse. There's a lot of things that we have discussed but I can't compressed everything here. But one thing's for sure, we have learned a lot from it.



Week 10

For week 10, we had implementing basic addressing scheme, basic router configuration, routing table and its principles, packet fields and frame fields, path determination. We also had a brief session about Dynamic and Static Routing.  We tried setting passwords for each router, configuring interfaces, configuring a banner, saving changes on the router and verifying basic configuration and router operations.

Sir Justin also made us try doing an example of Static Routing through packet tracer. We also discussed the dynamic routing protocols summary wherein we had that diagram to understand it. Sir Justin discussed the best path and metric for the routers which is hop count and bandwidth. Based on what he said, the best path is bandwidth. Lastly, path determination. Sir Justin taught us on how to get the IP address that is free to use. Then just some meanings and the meeting has finally ended with of course, the exercise. We shouldn't forget that.

Week 5 & 6

For week 5, we have talked about Application Layer Services. We just took the topic for, I guess, 1 meeting. We kept on configuring servers for us to learn. And for us to do it, we had an exercise.

For week 6, we have learned about transport layer and packet sniffing using Wireshark. We encountered Open Systems Interconnection Model wherein we deepen our understanding about the different layer in networking. In transport layer, we have learned the different responsibilities, functions and protocols that are commonly used. For packet sniffing, we had an exercise wherein we capture results using wireshark and 3-way handshake connection. We sniffed the Asia Pacific College (APC) website and TipidPC website. Sniffing encrypted traffic is worst, I guess.

Thursday, November 3, 2016

Research Paper

On week 5, I wasn't able to attend again due to the cancelled flight. I wasn't able to fly back to Manila on Monday. Luckily, my classmates told me that Sir Justin wasn't present. But as week 6 passed by, research paper was the main topic. My groupmates and I was still unsure about the given statements in our research. But as I talked to them, I got the inspiration to push through and help them in making the project a good one. Good thing is we were able to pass it on time and got Sir Justin's approval for the said research. By the way, our topic is about Fault Tolerance Techniques in Cellular Networks.

Packet Tracer

On week 3, we have started learning more about Packet Tracer. We learned on how to input the needed objects. It was actually one of the best things that I have learned so far. Because you'll be dealing with the connection between the computers and the servers. Of course, you have to know what cable to use in the specific connection. You'll also learn how to configure each system and ping if you have done it correctly.  I hope we could do more excise for Packet Tracer.

On week 4, I wasn't able to attend the meeting. I was in Hong Kong by that time. I'm sure that my classmates have learned something new and interesting.

Thursday, September 29, 2016

Networks

In the first meeting with Sir Justine for our subject DNETCOM, we were asked about Networks.


  • What is network?
  • Why do we need networks?
Network has a lot of meaning. Arrangement of intersecting lines, a group or system of interconnected people or things and a lot more. But network does not base only to that. Network can also be for e-learning and work. Why? Because of the following:

for E-learning
  1. Current and accurate
  2. Availability
  3. Consistency
  4. Cost reduction
for Work
  1. Remote Access
  2. Multiple Resources 

Network also introduced some of the popular communication tools such as: Instant Messaging, Blogs, Wikis, Podcasting and Collaboration tools. 

Networking has architecture components wherein you could follow to make a better network for a certain company.

Architecture Components:

  • Fault tolerance
  • Scalability
  • Quality of Service (QoS)
  • Security
Of course, you shouldn't just focus on making a fast network. Also, you have to consider whether whom you should give the highest availability, security etc. and the topology wherein you should arrange the network along with its nodes and connecting lines.

On the second meeting, we discussed about the 2 domains, types of network devices and the different cables to use. The 2 domains are collision and broadcast. Collision Domain refers to the capability of the devices to transmit data simultaneously, while, Broadcast Domain refers to the capability of the devices to transmit data to all other devices in a network segment.

How to differentiate the following network devices? Hub, Switch, and Router

Hub –  has 1 BIG Collision Domain (CD) and 1 BIG Broadcast Domain (BD).
Switch – has 1 CD per interface and 1 BIG BD.
Router – has 1 CD per interface and 1 BD per interface. 

Those 3 also have alternative devices that you can use such as: repeater, bridge and firewall. In which have less ports. And for the last, cables. Straight-through cable is a cable that you can use to connect different devices. Crossover must be used for the same devices while console cable is for Access Command Line Interface (CLI) of the device.

As I listen to the lecture, my understanding in networking is something that is too basic. I didn't know that there's a lot of things you should know before you could actually say you know networking. You might as well want to learn and gain something.