Navigating the Physical Layer — Cables, Interfaces, and Firewall Logic

In my second day of networking, I moved from theory to practice using Cisco Packet Tracer. The goal was simple: connect a firewall, routers, and switches. The reality was a bit more complex, involving the “Like Devices” rule and the unique logic of the ASA 5505.

Get Dawid Kowalski’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Key Learning: The “Like Devices” Rule
One of the first hurdles was understanding when to use a Straight-Through vs. a Cross-over cable.

• Straight-Through: Used for connecting “unlike” devices (PC to Switch, Switch to Router).
• Cross-Over (Dashed Line): Used for “like” devices (Switch to Switch). While modern gear uses Auto-MDIX, CCNA fundamentals require knowing the legacy standard for pinouts.

The “Red Arrow” Mystery:
The most frustrating part was the red links. Unlike home routers, enterprise Cisco gear starts with all interfaces in a Shutdown state for security.

I typed these commands into Router1’s CLI:

Router(config-if)# exit
Router(config)# interface GigabitEthernet 0/0/0
Router(config-if)# no shutdown
Router(config-if)# exit
Router(config)# interface GigabitEthernet 0/0/1
Router(config-if)# no shutdown

Learning the no shutdown command was my first step into the Cisco CLI.

The ASA 5505 Challenge:
I discovered that the ASA 5505 isn’t just a firewall; it’s a “Switch-Firewall.” You can’t put an IP address directly on the physical port. I had to create a VLAN, name it (nameif outside), and then assign the physical port to that VLAN.

Conclusion:
By the end of the day, all my links were green. I had successfully used Copper, Fiber, Serial, and Console cables to create a functional (and secure) network path.