Lab 5.6.1 Reflection

For Lab 5.6.1 by reading the information on the lab i was able to learn that the config isn't the only way of solving IP routing problems. You can also use the Cisco Internetwork Operating system command line interface to solve problems on the local area network(which will be showed in later packet tracer labs). I also learned that the inspecting tool can be used to examine the routing table in packet tracer. I was also able to learn how to configure a route using a GUI(Graphic User Interface). I would have to configure the router with address and subnet mask as 0.0.0.0, and also the next hop as 10.10.6. This configuration  would make any packet that came from the LAN would be directed towards the R1-ISP Router. The most important thing that i learned from this lab which was a on going problem through the other labs was the reason why a added PDU would always fail the first time to the extent where you would have to press the "fire" button to resend it. The problem was that the ARP table were not yet populated.

Reflection questions:
The data that a IP packet can contain is things from the destination IP address, source address, Protocols etc.
What is meant by the phrase the "IP packet has been routed" means that it has traveled through the network and reached the destination. A route is a pathway in which packets travel through. These routes can be configured based on the best possible way to send the packets to the user's wishes. The places where things go wrong could be from the routes to even the devices. If devices or routes aren't configured correctly than packets would either never be sent or on the most likely be lost or dropped.