Today was a huge breakthrough in learning routing concepts. When I started with a small Cisco network I kind of cheated the routing a little and on the branch office routers by setting default gateways set to the main office. This is not a good way of achieving routing between locations so I wanted to get everything working on static routing without specifying any default gateways. My instructor has a brilliant method to help with determining routing. The gateway to a network will always be the furthest IP address that is pingable. After building the static routing tables in this manner, I found I could do the static routing properly. It is a lot of information to keep track of and makes me grateful for the advent of dynamic routing protocols.
I decided to make things more complicated and add an additional office location and plumb the routing for that. It’s appreciably a lot to keep track of so before I did the plumbing, I annotated the additional network with all of the numbers. This made for a much easier experience in getting routing working. I found that both traceroute (tracert) and ping to be extremely useful tools. The nerd in me absolutely loves routing. It’s fascinating to see how data packets make it from one end of the network to the other.
This additional instructor challenge completed, it’s time to hit the books for the next chapters. I think I will ask my fearless leader how I can get domain name resolution working in the routers. I figured out how to add and define a DNS server in Packet Tracer and I took a guess at Cisco IOS config statements to try and get the device names to show in the trace instead of just the IP addresses but it is not working. I may also try Google but it might make an interesting topic for discussion by posing the question. We shall see what happens.