Packet Tracer 1.4.2.2 Determining the best using routing tables.

In this lab it had started with already 100% complete. All that it gave were some questions from me to answer. from those question i was given all the answers just by exploring the network that included looking for the routing protocol, best metric, and the best path which would be FastEthernet0/0 since it was the only one configured, henceforth the best path. i feel that i really didn't learn that much from this lab since must of the things i already have done in the previous labs. i probably would have learned more from actually troubleshooting the network problems and finding answers my own way. Since this network was bigger then the others i previously had to work on having to troubleshoot it would have been a lot more worth it then just answering questions.

Packet Tracer 1.3.5.2 Routing Table Principles

in this packet tracer i was able to learn about the routing table and more things about it. i start with a ping from the desktop of PC3 which results in it being in it being unsuccessful. so i troubleshoot this problem further by going into the CLI to configure an address. once i configure i try the ping again only for it to fail because of the request timing out. so i know had to look for another way of fixing the routing issue in R3. so what i did was by viewing the ping from PC1 to PC3 in simulation mode i could see the problem from a different perspective. so i filter the traffic so that only the ICMP packets is shown. i then add a simple PDU and click on PC1. this will recognize PC1 as the source of traffic, and then press PC3 as the destination host. this completely trouble shoots the problem that was associated with the ping and traveling of the packet.

Lab 1.3.4.2 Dynamic Routing

in this lab it focused on static rouing. the difference between Static and Dynamic is that in static routing you would have to entering the addresses manually in the routing table through the CLI. In Dynamic routing is a change that happens automatically in the network topology as if it adapts. in this lab i went to the CLI in order to configure the the router by using a new command router RIP. after i configure RIP in router R2, R3, R4 i would then analyze the routing table on each of the routers. as i press R1 to show ip route i notice that router shows directly connected routes along with static and dynamic routes. from there i would move to ping from R3 to PC1 only for it to be successful. all in all i then configure a static route in R2 since a static route doesn't adapt to changes in the network like a dynamic route. fom ther i ping once again but instead with R3 to PC1 and reach 100% completion.

Packet Tracer 1.3.3 Static Routing

In this packet tracer lab what i was able to learn about static routing. First i was told to enter the CLI  for R3 and configure terminal in order to add the static route. i enabled the router and added the command ip route 192.168.1.0 255.255.255.0 192.168.3.1. with this i was able to see the addresses with the show ip route  command. AFter that i would then have to ping R1 to reach R#. For task 2 i would enter a static route on R1 in order to reach R3. to do this i would move on to configuring R1 with similar commands as R3. Although the only difference would obviously be the command ip route 192.168.3.0 255.255.255.0 FastEthernet 0/1. From there i would similarly repeat a similar process on the remaining router to reach R1's LAN. After doing another ping but for R3 to PC1 the ping is successful. After that i reached 100% completion. i was able to learn about static routes and their importance to the network.

Packet Tracer 1.3.2.2 Directly Connected Networks

In this lab i was able to constantly add more from what i done before and improve my troubleshooting skills. in this lab i had to configure to routers R1 and R2. in this lab it shows the importance of having a routing table. without one packets wouldn't know where to go and as result, the packets will never arrive. i had to configure the ports Fa 0/0 and S0/0/0. since i had all the commands needed to do this task it was practically a breeze in entering it in the CLI. From there i was able to get green lights for all of the devices and resulting in completing this lab. After that all i did was use ping to see if the connectivity was functioning properly.

Packet Tracer 1.2.2 Configuring and Verifying R1

From this lab i had to out into action previous commands in order for me to complete the lab. To start if off i had to configure R1 using the CLI instead of the config tab. This was a bit more difficult since everything had to be done manually instead of just entering IP addresses and everything else is done automatically. i started of  with having to enter passwords in order to start configuration on the Serial0/0/0 and Fa0/0 ports. After successfully entering the corresponding addresses with the routing table given to me i was able to get the green light for the switch and router. However for the other side i had to to config the serial port in order for a complete connection to be done. The command that i had to use for the enabling for the secret passwords i used the vty command for this set up. After that i had a complete lab with new skills and tactics for more difficult configurations.

Packet Tracer 1.2.1.2 Connecting and Identifying Devices

In this packet tracer lab some of the things required where to configure the devices in the logical workspace  that included two PCs, 2 Routers and one switch. The first thing that i had to do was connect the corresponding ports of all the devices in the workspace. After that i gave all the devices new names which required little effort. the trickier part was using the "place note" feature to assign the network numbers for the devices. After that all that was left to do was put in the correct addresses for all the devices according to the routing table given. As a result, i was able to apply skills that i learned from previous labs and make everything run much more quickly and successfully.