Movie + Food = LOVE

This week is our last discussion week. After 13 weeks, the term is about to end. Our final lesson was RIP. RIP in routing means Routing Information Protocol. It uses a metric called hop count. In our last lesson it took me a while to fully understand  what the next hop of a route was. You could imagine my reaction when I heard the term hop count. When our prof showed us how to implement RIP in Packet Tracer. I thought it looked easy enough. It looked easier than manually routing in a static route. So our group was eager to do the last exercise. After 2 meetings, we were still unable to finish it. Whenever we pinged a device, it would return as a failure. It was very frustrating. When we were about to give up, sir helped us out. However, he discovered that there was a problem with the case. We just had to laugh it out. We had let the exercise frustrate us when we should've asked for help right away instead. We would've saved ourselves the trouble.

As you may have known from my previous posts, our class had been studying about WireShark. But, as they say "Walang Forever". It was time for us to part ways. Our class had to move on from using Wireshark. I felt that the lessons were rather short. We just learned a new tool and then we had to drop it a couple of weeks later. Then again, this might be the product of combining 2 subjects into one (DNETCOM).  However, don't be sad, for we were reunited with Cisco Packet Tracer. We were still able to apply the lessons in configuration during midterms. We still practiced naming routers, setting passwords, configuring interfaces and the likes. Also, the level of difficulty went up a notch. We started routing the devices. Sir Justin taught us how to route step-by-step. Honestly though, our group had a hard time routing during the exercise. We were aware of the step by step procedure and what commands to use. Our problem was routing the path or figuring out the next h