<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Packet-Tracer on Andy Als</title><link>https://andyals.com/tags/packet-tracer/</link><description>Recent content in Packet-Tracer on Andy Als</description><generator>Hugo</generator><language>en-us</language><copyright>Andy Als</copyright><lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://andyals.com/tags/packet-tracer/index.xml" rel="self" type="application/rss+xml"/><item><title>Lab — Static Routing and EIGRP</title><link>https://andyals.com/posts/2026/06/lab-static-routing-and-eigrp/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://andyals.com/posts/2026/06/lab-static-routing-and-eigrp/</guid><description>&lt;p&gt;In this lab, the goal was to practice some basic routing configurations. Going through the NetworkChuck Summer of CCNA course, this is the section we are currently up to.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="a-little-bit-on-routing"&gt;A Little Bit on Routing&lt;/h2&gt;
&lt;p&gt;Routers will not route to networks they do not know about. They are clever devices in some ways, but not that clever. So there are a few different ways to get routers to know about networks. Firstly, any network directly connected to the router (i.e plugged into an interface) will be available. Providing of course the ip address has been set and the interface is up/up.&lt;/p&gt;</description></item></channel></rss>