Learning Log 6 (Weeks 11 & 12)

It's been a while since we have started the first term as strangers to this new place we call 'Networking'. Days, weeks, even months have passed and so are the things we used to do. We started from the very bottom, and now, we are at the verge of concluding this subject with only one lecture remaining on hand. After thirteen weeks, we have learn several networking concepts from topologies, network architecture components, domains, network devices, protocols etc. For the final round, here comes RIP (Routing Information Protocol) to close in the regulation. Basically, it is a protocol that exchanges information between network devices within a network. It uses hop count as a routing metric. This refers to the number of devices that the information will travel through before it reaches its final destination. Generally, higher hop count results to slower performance. Also, RIP uses different timers namely: Update, Hold-down, Flush and Timeout. By default, update timers lasts for 30 seconds. Invalid or timeout timers indicates how long the information can be retained in the routing table without being updated. It is set to 180 seconds or 3 minutes by default. The flush timer on the other hand specifies the time between when the information is marked as invalidated or unreachable and when it will be subjected to removal. It is set to 240 seconds or 4 minutes which is 1 minute longer than the invalid timers. Lastly, for Hold-down timers, it blocks any updating in order to give way towards stabilizing the router. Normally, it is set to 180 seconds or 3 minutes.

Learning Log 5 (Weeks 9 & 10)

Everything that was recently discussed has been all about routing, its basic concepts, principles and its classifications. As far as we have learned and understand from the lecture, there are mainly two type of routing: the static routing and the dynamic routing. If you were to know the meaning of static and dynamic, then the concpet should be much easier to grasp because it is actually self-explanatory. Static means some sort of stationary, still, constant or to be simple; not changing. Static routing is highly implemented and recommended if a network uses only one ISP (Internet Service Provider) to be able to connect to the internet. On the other hand, dynamic means not still, inconsistent, changing.
Dynamic routing lives up to its name by discovering networks, updating (can also be referred to as changing) and maintaining routing tables.  See how it is easy to comprehend, am I right with that? I really hope that each and every one of these would be easy as the word itself. However, the latter parts would prove as one of the greatest calamities of the second age. Stay tuned and stay alive for the next chapters of ROUTING.

Learning Log 4 (Weeks 7 & 8)

As weeks pass by, another term will soon come to and end. It has been a tough and bloody-as-hell half of a term we had so far and hopefully it would not be something like it for the next one. After the release of the midterm grades, relief suddenly went through my my mind as I looked upon the marks that were nothing less than satisfactory and above average. Nevertheless, there is still a few more weeks up ahead of us which means there will be new things for us to learn on our DNETCOM class. To make things short and concise, I would simply emphasize on one topic we have learned so far. Sir Justin introduced us to CISCO Packet Tracer second degree cousin, Mr. Wireshark. This nasty bastard is infamous for sniffing packets passively right under your noses. Enough with the overly-exaggerated intro and let's get into the chase. Wireshark enables packet sniffing, or sometimes referred to as capturing, which has something to do with sending and receiving information on either both ends of the 'handshake'. The TCP (Transmission Control Protocol) uses a three-way handshake that includes different flags with different indications. The goal is pretty simple and precise: find the three-way handshake made by the user and the website. I just hope that the next exercises won't get any more difficult tan this. HOPEFULLY.

Week 5

Within a couple of weeks, the midterms will finally set foot; yet many students are agitated due to a handful of the requirements that needs to be complied during the said period. As for our DNETCOM subject, we are to propose, present and defend a research paper. I definitely hope it would be as easy as it sounds. Unfortunately, it isn't. The past exercises proved themselves a worthy challenge since the previous one took us a few days to finish. The following week, we are informed that the next half would focus on a different application called 'Wireshark'. It has been seven weeks and I can say to myself that I almost had no idea what will happen each and every time. Yet hopefully, the odds may be in our favor for the entire term.

Week 4

This week's topic is still the same but it becomes as complicated as it can be. Last time, the tasks only require setting IP addresses and subnet masks. However, this time, more types of servers are present in the scene such as DNS, DHCP, E-mail and a lot more. Also, each one of them has corresponding ports that needs to be memorized. The exercises was a great challenge since the requirements cannot be easily met unless you fully understand the lesson.

Week 3

The further we proceed, the more difficult it gets. This time around, we created several simple local area networks or LAN. The word "simple" is just a relative term. Aside from that, the configuration must be done MANUALLY. At first, it was hard. But as we go through the process, I therefore conclude that it is still hard as it was. The task focuses more on the configuration part which is confusing to be honest. Although, I kind of grasped the concept of typing the appropriate command such as setting a password, assigning an IP address, and pinging the router. Nevertheless, there's still much to learn about Cisco Packet Tracer, the command-based configuration and everything else that falls within the topic.

Week 2

After we tackle about network architecture components and different topology types, we proceeded to a new topic. This time, it focuses on network devices and their domains. In order to properly implement a suitable network, there are more things that needs considering such as what devices must be used and how will they be connected to each other. It is almost the exact same thing, but more specific. After insuring the information that will be stored in the network, the next thing to decide on is how the information goes though it. To accomplish this, appropriate devices and domains must be used to attain the ideal network to implement.