<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Caleb Adewuyi on Medium]]></title>
        <description><![CDATA[Stories by Caleb Adewuyi on Medium]]></description>
        <link>https://medium.com/@dammyadewuyi1?source=rss-153e3fbcc9c9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*N5NtBjn3oq7UjEWO</url>
            <title>Stories by Caleb Adewuyi on Medium</title>
            <link>https://medium.com/@dammyadewuyi1?source=rss-153e3fbcc9c9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:35:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dammyadewuyi1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Enterprise-Grade Network Infrastructure: From Design to Deployment]]></title>
            <link>https://medium.com/@dammyadewuyi1/building-enterprise-grade-network-infrastructure-from-design-to-deployment-8ac2fe3b3f64?source=rss-153e3fbcc9c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ac2fe3b3f64</guid>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[ccna-certification]]></category>
            <category><![CDATA[dynamic-routing]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[computer-networking]]></category>
            <dc:creator><![CDATA[Caleb Adewuyi]]></dc:creator>
            <pubDate>Mon, 17 Nov 2025 17:42:02 GMT</pubDate>
            <atom:updated>2025-11-17T17:42:02.956Z</atom:updated>
            <content:encoded><![CDATA[<h3>When Theory Meets Reality: My Journey Through Enterprise Network Design</h3><p><em>What happens when you take everything you’ve learned about networking and apply it to solve real-world business challenges? This is the story of designing and implementing a complete enterprise network infrastructure that doesn’t just work — it works securely, efficiently, and reliably.</em></p><h3>The Challenge: Connecting a Multi-Site Enterprise</h3><p>Imagine this scenario: A growing organization with a headquarters in one city and two branch offices in different locations. Each location has distinct departments — Finance, Engineering, Sales, IT, and Voice services — all needing secure, isolated network segments. The headquarters houses critical servers (DNS, Web, NTP), and everything must communicate seamlessly while maintaining strict security boundaries.</p><p>This isn’t just about connecting computers. It’s about building a network that:</p><ul><li><strong>Scales</strong> as the business grows</li><li><strong>Secures</strong> sensitive departmental data</li><li><strong>Automates</strong> IP address management</li><li><strong>Synchronizes</strong> time across all devices</li><li><strong>Prevents</strong> unauthorized access at every layer</li><li><strong>Connects</strong> remote sites reliably</li></ul><p>This is exactly what I set out to build, and this is how I did it.</p><h3>Architecture Overview: Building Blocks of Enterprise Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQcH2t6DEnEt9kCIWD51nw.png" /></figure><p>The network follows industry-standard hierarchical design principles:</p><p><strong>Headquarters (3-Tier Architecture):</strong></p><ul><li><strong>Core Layer</strong>: High-speed backbone connecting all distribution switches</li><li><strong>Distribution Layer</strong>: Aggregation point with routing and policy enforcement</li><li><strong>Access Layer</strong>: End-user connectivity with VLAN segmentation</li></ul><p><strong>Branch Offices (2-Tier Architecture):</strong></p><ul><li><strong>Distribution Layer</strong>: Combines routing and core functions</li><li><strong>Access Layer</strong>: Local user connectivity</li></ul><p><strong>Interconnection:</strong></p><ul><li><strong>GRE Tunnels</strong>: Secure site-to-site connectivity over the internet</li><li><strong>OSPF Routing</strong>: Dynamic route propagation across all sites</li></ul><h3>Network Segmentation Strategy</h3><p>Each location implements VLAN-based segmentation:</p><ul><li><strong>VLAN 10</strong>: Sales (CRM Access)</li><li><strong>VLAN 20</strong>: Finance (Restricted Access)</li><li><strong>VLAN 30</strong>: Engineering (Development Resources)</li><li><strong>VLAN 40</strong>: Voice (QoS Priority)</li><li><strong>VLAN 100</strong>: BlackHole (Unused Ports for Security Purpose)</li><li><strong>VLAN 150</strong>: IT Management (Management Purpose)</li><li>VLAN 1000: Native VLAN (Untagged Traffic)</li></ul><p>This segmentation isn’t arbitrary — it maps directly to business requirements and security policies.</p><h3>Phase 1: Foundation — DHCP Infrastructure</h3><h3>Why DHCP Matters in Enterprise Networks</h3><p>Manual IP address assignment in an organization with 100+ devices? That’s a recipe for IP conflicts, misconfigurations, and hours of troubleshooting. DHCP automation is essential, but it must be done right.</p><h3>Implementation Strategy</h3><p><strong>Centralized DHCP Server:</strong></p><ul><li>Deployed on a dedicated router in each of the branches</li><li>Configured multiple DHCP pools for each VLAN across all sites</li><li>Included DHCP options for DNS servers and default gateways</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*fBJxgtx8EvVAHA-nSOoJxQ.png" /></figure><p><strong>Key Configuration Elements:</strong></p><pre>ip dhcp excluded-address 192.168.1.1 192.168.1.10</pre><p>This reserves the first 10 IPs in each subnet for static assignments (routers, servers, printers).</p><p><strong>VLAN-Specific Pools:</strong></p><pre>ip dhcp pool VLAN-10<br> network 192.168.1.0 255.255.255.192<br> default-router 192.168.1.1<br> option 43 ip 192.168.0.35</pre><pre>ip dhcp pool VLAN-20<br> network 192.168.1.64 255.255.255.224<br> default-router 192.168.1.65</pre><p>Notice the /26 and /27 subnet masks? This implements <strong>Variable Length Subnet Masking (VLSM)</strong> to efficiently allocate IP space based on actual needs. Sales VLAN gets a larger subnet, while smaller departments receive appropriately sized blocks.</p><h3>DHCP Relay Configuration</h3><p>Here’s where it gets interesting. Each VLAN don’t run their own DHCP servers — they relay requests to dedicated DHCP server which is the WAN router on the branches. This centralizes management while maintaining local functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*0ZlW_oN5bwHdOTxPOXCIoA.png" /></figure><p>On distribution switches:</p><pre>interface Vlan10<br> ip address 192.168.1.2 255.255.255.192<br> ip helper-address 192.168.1.133<br> standby 1 ip 192.168.1.1<br> standby 1 preempt</pre><p>The ip helper-address command forwards DHCP broadcasts to the central server. The standby configuration? That&#39;s HSRP (Hot Standby Router Protocol) providing gateway redundancy. If one distribution switch fails, the other takes over instantly.</p><p><strong>Result:</strong> Users plug in their devices, get IP addresses automatically, and never know there’s a complex infrastructure working behind the scenes.</p><h3>Phase 2: Security Layer 1 — DHCP Snooping</h3><h3>The Rogue DHCP Server Threat</h3><p>Here’s a real-world attack scenario: Someone brings a home router to the office and plugs it in. That router starts handing out IP addresses with itself as the gateway. Now, all traffic from nearby users flows through the attacker’s device. Credentials, emails, sensitive data — all compromised.</p><p>DHCP Snooping prevents this attack vector.</p><h3>How DHCP Snooping Works</h3><p>Think of DHCP Snooping as a bouncer at a club. It maintains a list of trusted DHCP servers and blocks all others. It also builds a database mapping MAC addresses to IP addresses, switch ports, and VLANs — a critical foundation for other security features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*5szzeE5Kpw5ZjQd72O7ZAA.png" /></figure><p><strong>Configuration on Access Switches:</strong></p><pre>ip dhcp snooping vlan 10,20,30<br>ip dhcp snooping</pre><p>This enables snooping on target VLANs. But here’s the critical part — by default, <strong>ALL ports are untrusted</strong>. You must explicitly trust uplink ports:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*HujEms0GBZhmNlOCRrplLA.png" /></figure><pre>interface FastEthernet0/1<br> switchport access vlan 10<br> ip dhcp snooping limit rate 15<br> switchport mode access<br> switchport port-security mac-address sticky</pre><p>On access ports, we limit DHCP requests to 15 per second (preventing denial-of-service attacks). On uplink ports connecting to our DHCP relay-enabled switches, we configure:</p><pre>interface GigabitEthernet1/0/1<br> description ## Uplink to DSW1 ##<br> ip dhcp snooping trust</pre><p><strong>The Result:</strong> Rogue DHCP servers are blocked. The network tracks every device’s MAC-to-IP binding. This database becomes the foundation for Dynamic ARP Inspection and IP Source Guard — additional security layers.</p><h3>Phase 3: Access Control Lists (ACLs) — Enforcing Security Policy</h3><h3>From Business Requirements to Technical Controls</h3><p>“Finance shouldn’t access Engineering resources.”<br>“Sales can access the internet but not the server farm.”<br>“Only IT can manage network devices.”</p><p>These business rules must translate into technical enforcement. That’s where ACLs come in.</p><h3>Standard vs. Extended ACLs</h3><p>I implemented standard ACL based on use case:</p><p><strong>Standard ACLs</strong> — Simple source-based filtering<br><strong>Extended ACLs</strong> — Granular control (source, destination, protocol, port)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*5tP5yarL31DUtHIGVQY8tA.png" /></figure><p><strong>Finance Department Isolation:</strong></p><pre>ip access-list standard DENY-FINANCE-ENGINEERING<br> remark deny both Finance and Engineering<br> deny   192.168.1.64 0.0.0.31<br> deny   192.168.1.96 0.0.0.15<br> permit any</pre><p>This ACL uses wildcard masks (the inverse of subnet masks) to identify the Finance and Engineering subnets, then denies inter-department traffic.</p><p><strong>Departmental Traffic Control:</strong></p><pre>ip access-list standard DENY-SALES-ENGINEERING<br> remark Deny both Sales and Engineering<br> deny   192.168.1.0 0.0.0.63<br> deny   192.168.1.96 0.0.0.15<br> permit any</pre><pre>ip access-list standard DENY-SALES-FINANCE<br> remark Deny both Sales and Finance<br> deny   192.168.1.0 0.0.0.63<br> deny   192.168.1.64 0.0.0.31<br> permit any</pre><h3>Strategic ACL Placement</h3><p>ACLs are applied at distribution layer VLAN interfaces — the traffic aggregation point. This provides:</p><ul><li><strong>Efficiency</strong>: Filter once instead of on every access port</li><li><strong>Manageability</strong>: Central policy enforcement</li><li><strong>Performance</strong>: Minimal latency impact</li></ul><p><strong>The Implicit Deny:</strong><br>Every ACL ends with an invisible deny any. This follows the security principle of &quot;deny by default, permit explicitly.&quot;</p><h3>Phase 4: Port Security — Endpoint Protection</h3><h3>The Last Line of Defense</h3><p>You’ve secured DHCP, implemented ACLs, but what if someone unplugs a legitimate device and connects an unauthorized laptop? Port security addresses endpoint-level threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*PzcEgw0G4VX_BlppXGSirg.png" /></figure><h3>Three-Tiered Port Security Strategy</h3><p><strong>1. MAC Address Limiting:</strong></p><pre>switchport port-security maximum 1</pre><p>Limits each port to 1 MAC addresses (primary device).</p><p><strong>2. MAC Address Learning:</strong></p><pre>switchport port-security mac-address sticky</pre><p>The switch dynamically learns and saves authorized MAC addresses. This eliminates manual MAC address configuration while maintaining security.</p><p><strong>3. Violation Response:</strong></p><pre>switchport port-security violation restrict</pre><p>When a violation occurs:</p><ul><li><strong>Restrict mode</strong>: Drops unauthorized traffic, increments counter, keeps port up</li><li><strong>Alternative modes</strong>: shutdown (disables port), protect (drops silently)</li></ul><h3>Voice VLAN Integration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*N9UCP9RXnCM-gr9RJGeZVg.png" /></figure><pre>switchport access vlan 10<br>switchport mode access<br>switchport voice vlan 40</pre><p>This configuration:</p><ul><li>Places data traffic in VLAN 10</li><li>Directs voice traffic to VLAN 40</li><li>Prioritizes voice for QoS</li><li>Allows both a PC and IP phone on one port</li></ul><p><strong>Complete Access Port Configuration:</strong></p><pre>interface FastEthernet0/3<br> switchport access vlan 10<br> ip dhcp snooping limit rate 15<br> switchport mode access<br> switchport voice vlan 40<br> switchport port-security mac-address sticky<br> switchport port-security violation restrict</pre><p><strong>Result:</strong> Each port becomes a security checkpoint, preventing unauthorized device connections while supporting legitimate business needs.</p><h3>Phase 5: Network Time Protocol (NTP) — Synchronization &amp; Forensics</h3><h3>Why Time Matters in Network Security</h3><p>When a security incident occurs, investigators need to correlate events across multiple devices. If each device has a different time, this becomes impossible. NTP solves this by synchronizing all network devices to a single authoritative time source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3loqfUbIN4OV3euGBdcJ1w.png" /></figure><h3>NTP Hierarchy Implementation</h3><p><strong>Stratum 1 (Authoritative Source):</strong></p><ul><li>NTP server at headquarters (192.168.0.2)</li><li>Connected to external time source or configured as master</li></ul><p><strong>Stratum 2 (Distribution):</strong></p><ul><li>All network devices synchronize to the central NTP server</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*FpAo9NIIPq3TiJqHpdHzGA.png" /></figure><p><strong>Router NTP Configuration:</strong></p><pre>ntp server 192.168.0.2</pre><p><strong>Verification Commands:</strong></p><pre>DSW1#show run | section ntp<br>ntp server 192.168.0.2</pre><pre>DSW1#show ntp associations</pre><p>The output shows:</p><ul><li>Server address: 192.168.0.2</li><li>Stratum level: 1</li><li>Synchronization status: Selected and active (*)</li></ul><h3>Beyond Time: The Security Benefits</h3><p>Synchronized time enables:</p><ul><li><strong>Accurate logging</strong>: Precise correlation of events</li><li><strong>Compliance</strong>: Many regulations require time synchronization</li><li><strong>Troubleshooting</strong>: Clear sequence of network events</li><li><strong>Certificate validation</strong>: PKI requires accurate time</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3loqfUbIN4OV3euGBdcJ1w.png" /></figure><p>Notice the sys.peer designation with the * symbol? This indicates successful synchronization and active time source selection.</p><h3>Phase 6: WAN Connectivity — GRE Tunnels &amp; OSPF Routing</h3><h3>Connecting Distributed Sites</h3><p>Branch offices need secure, reliable connectivity to headquarters. While VPN solutions exist, I implemented <strong>GRE (Generic Routing Encapsulation) tunnels</strong> combined with <strong>OSPF dynamic routing</strong>.</p><h3>Why GRE Tunnels?</h3><p>GRE provides:</p><ul><li><strong>Protocol flexibility</strong>: Carries any Layer 3 protocol</li><li><strong>Routing protocol support</strong>: OSPF can run over tunnels</li><li><strong>Simplicity</strong>: Easier to configure than full IPsec</li><li><strong>Scalability</strong>: Easy to add new sites</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*nTVAsGx2GmH47FSq2hnHFQ.png" /></figure><p><strong>GRE Tunnel Configuration (WANR — Headquarters):</strong></p><pre>interface Tunnel1<br> ip address 10.1.0.2 255.255.255.252<br> mtu 1476<br> tunnel source Serial0/1/0<br> tunnel destination 203.0.113.2</pre><pre>interface Tunnel2<br> ip address 10.1.0.10 255.255.255.252<br> mtu 1476<br> tunnel source Serial0/1/0<br> tunnel destination 203.0.113.6</pre><p>Key elements:</p><ul><li><strong>MTU 1476</strong>: Accounts for GRE overhead (24 bytes)</li><li><strong>Point-to-point addressing</strong>: /30 subnets for efficient IP usage</li><li><strong>Source/Destination</strong>: Physical interface and remote public IP</li></ul><h3>OSPF Configuration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*-72HMrgxFWTMnDVAlCwJfA.png" /></figure><pre>router ospf 1<br> log-adjacency-changes<br> network 192.168.1.0 0.0.0.63 area 0<br> network 192.168.1.64 0.0.0.31 area 0<br> network 192.168.1.96 0.0.0.15 area 0<br> network 192.168.1.112 0.0.0.15 area 0</pre><p>OSPF provides:</p><ul><li><strong>Dynamic routing</strong>: Automatic route updates</li><li><strong>Fast convergence</strong>: Quick failover if links fail</li><li><strong>Load balancing</strong>: Equal-cost multipath routing</li><li><strong>Scalability</strong>: Hierarchical design with areas</li></ul><h3>Redundancy with HSRP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*0ZlW_oN5bwHdOTxPOXCIoA.png" /></figure><pre>interface Vlan10<br> ip address 192.168.1.2 255.255.255.192<br> standby 1 ip 192.168.1.1<br> standby 1 priority 110<br> standby 1 preempt</pre><p>HSRP configuration across distribution switches ensures:</p><ul><li><strong>No single point of failure</strong>: Automatic gateway failover</li><li><strong>Transparent to users</strong>: Virtual gateway IP remains constant</li><li><strong>Priority-based election</strong>: Designated primary and backup</li><li><strong>Preemption</strong>: Primary reclaims role after recovery</li></ul><h3>Phase 7: Additional Services &amp; Final Integration</h3><h3>DNS &amp; Web Services</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*PN_K2SpwVKWalw1aHPQYkw.png" /></figure><p>The DNS/WEB server provides:</p><ul><li><strong>DNS resolution</strong>: Internal name resolution for enterprise.com domain</li><li><strong>Web hosting</strong>: Company intranet and IT services portal</li><li><strong>DHCP services</strong>: Central IP address management</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*xrEJXlIVKDqca1LXQuhVzw.png" /></figure><p>The successful web access demonstrates:</p><ul><li>End-to-end connectivity</li><li>DNS resolution functioning</li><li>ACL policies permitting appropriate traffic</li></ul><h3>Spanning Tree Protocol</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*DhMrQOUWCit8rLrjuQ86Cw.png" /></figure><pre>spanning-tree mode pvst<br>spanning-tree extend system-id<br>spanning-tree vlan 10 priority 24576</pre><p>STP prevents Layer 2 loops by:</p><ul><li><strong>Blocking redundant paths</strong>: Prevents broadcast storms</li><li><strong>Enabling redundancy</strong>: Activates backup paths on failure</li><li><strong>Per-VLAN optimization</strong>: Different root bridges per VLAN</li></ul><h3>SSH &amp; Device Management</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*akN1GtFJ2k4Ay0NP4y72qA.png" /></figure><pre>ip ssh version 2<br>ip domain-name Enterprise.com</pre><p>Secure device management through:</p><ul><li><strong>SSH v2</strong>: Encrypted administrative access</li><li><strong>Local authentication</strong>: Username/password protection</li><li><strong>AAA potential</strong>: Foundation for RADIUS/TACACS+ integration</li></ul><h3>Verification &amp; Testing: Proving It Works</h3><h3>End-to-End Connectivity Tests</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*vwExf3OZo8xCE80v4PMP1A.png" /></figure><p>Client receives:</p><ul><li><strong>IP Address</strong>: 192.168.2.22 (DHCP assigned)</li><li><strong>Subnet Mask</strong>: 255.255.255.192</li><li><strong>Default Gateway</strong>: 192.168.2.1</li><li><strong>DNS Server</strong>: 192.168.0.10</li></ul><p>This proves:</p><ul><li>DHCP relay functioning across sites</li><li>VLAN segmentation working</li><li>Gateway redundancy operational</li></ul><h3>Security Verification</h3><p><strong>Port Security Status:</strong></p><ul><li>MAC addresses learned and secured</li><li>Violation counters at zero (no security breaches)</li><li>Sticky MAC addresses persisted to configuration</li></ul><p><strong>DHCP Snooping Database:</strong></p><ul><li>All clients have binding entries</li><li>MAC-to-IP-to-port mappings recorded</li><li>Foundation for DAI/IPSG ready</li></ul><p><strong>ACL Hit Counters:</strong></p><pre>deny   192.168.1.64 0.0.0.31 (15 matches)<br>deny   192.168.1.96 0.0.0.15 (8 matches)<br>permit any (2847 matches)</pre><p>This proves ACLs are actively filtering traffic as designed.</p><h3>Time Synchronization Validation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3loqfUbIN4OV3euGBdcJ1w.png" /></figure><p>All devices synchronized to NTP server:</p><ul><li>Consistent timestamps across infrastructure</li><li>Security event correlation enabled</li><li>Compliance requirements met</li></ul><h3>Lessons Learned: What This Project Taught Me</h3><h3>Technical Insights</h3><p><strong>1. Design Before Implementation</strong><br> The hierarchical architecture wasn’t arbitrary. Planning VLAN schemes, IP addressing, and security zones upfront saved hours of reconfiguration.</p><p><strong>2. Security in Layers</strong><br> No single security feature is sufficient. DHCP Snooping + Port Security + ACLs create defense in depth. Each layer catches threats the others might miss.</p><p><strong>3. Redundancy is Non-Negotiable</strong><br> HSRP, redundant distribution switches, and OSPF dynamic routing ensure the network stays operational even when components fail.</p><p><strong>4. Documentation is Critical</strong><br> Throughout implementation, documenting IP schemes, VLAN assignments, and security policies made troubleshooting exponentially easier.</p><h3>Challenges Overcome</h3><p><strong>Challenge 1: ACL Placement &amp; Direction<br></strong>My ACLs didn’t behave as expected because I applied them in the wrong direction on the wrong interface.<br><strong>Lesson:</strong> ACL effectiveness depends heavily on placement (inbound/outbound) and interface selection.</p><p><strong>Challenge 2: Packet Tracer Limitations</strong><br>Some advanced features like DHCP Snooping, IP SLA, and certain ARP inspection behaviors didn’t work reliably.<br><strong>Lesson:</strong> Packet Tracer is excellent for learning, but not all IOS features behave exactly like real hardware.</p><h3>Professional Growth</h3><p>This project transformed theoretical knowledge into practical expertise:</p><ul><li><strong>Problem-solving</strong>: Debugging complex multi-layer issues</li><li><strong>Security mindset</strong>: Thinking like an attacker to defend better</li><li><strong>Business alignment</strong>: Translating requirements into technical solutions</li></ul><h3>Conclusion: Building Networks That Matter</h3><p>This enterprise network implementation represents more than just connected devices — it’s a secure, scalable infrastructure that enables business operations while protecting against modern threats.</p><h3>Key Achievements</h3><p>✅ <strong>Automated IP Management</strong>: DHCP across multi-site environment<br>✅ <strong>Layered Security</strong>: DHCP Snooping, Port Security, ACLs<br>✅ <strong>Department Isolation</strong>: VLAN-based segmentation with policy enforcement<br>✅ <strong>High Availability</strong>: HSRP gateway redundancy, redundant switches<br>✅ <strong>Site Interconnection</strong>: GRE tunnels with dynamic OSPF routing<br>✅ <strong>Time Synchronization</strong>: NTP for security and compliance<br>✅ <strong>Secure Management</strong>: SSH access with strong authentication</p><h3>Real-World Application</h3><p>The skills demonstrated here directly apply to:</p><ul><li><strong>Enterprise IT roles</strong>: Network administrators, engineers, architects</li><li><strong>Security positions</strong>: Understanding defense-in-depth strategies</li><li><strong>Consulting opportunities</strong>: Designing networks for clients</li><li><strong>Career advancement</strong>: Demonstrating practical implementation ability</li></ul><h3>What’s Next?</h3><p>This network provides a foundation for advanced features:</p><ul><li><strong>QoS implementation</strong>: Prioritizing critical applications</li><li><strong>IPv6 dual-stack</strong>: Future-proofing the infrastructure</li><li><strong>Wireless integration</strong>: Secure Wi-Fi with 802.1X authentication</li><li><strong>Network monitoring</strong>: SNMP, NetFlow, syslog integration</li><li><strong>Automation</strong>: Python scripts for configuration management</li></ul><h3>Final Thoughts</h3><p>Building an enterprise network taught me that networking isn’t just about protocols and configurations — it’s about creating infrastructure that people depend on daily. Every security feature protects someone’s data. Every redundancy mechanism prevents business disruption. Every design decision impacts user experience.</p><p>If you’re on your own networking journey, remember: The best way to learn is to build. Start with fundamentals, layer on complexity, break things, fix them, and document everything. The skills you develop through hands-on implementation are what transform you from someone who knows networking to someone who <em>builds</em> networks.</p><p><strong>Want to discuss enterprise network design, security implementations, or have questions about specific configurations? Connect with me — I’m always eager to share knowledge and learn from the networking community.</strong></p><p><em>This project was built using Cisco Packet Tracer, demonstrating that world-class network design doesn’t require a physical lab. With determination, structured learning, and hands-on practice, anyone can master enterprise networking.</em></p><p><strong>#CCNA #NetworkEngineering #CyberSecurity #EnterpriseNetworking #ITInfrastructure</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac2fe3b3f64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Started out in Tech]]></title>
            <link>https://medium.com/@dammyadewuyi1/how-i-started-out-in-tech-b6bddccdd621?source=rss-153e3fbcc9c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6bddccdd621</guid>
            <dc:creator><![CDATA[Caleb Adewuyi]]></dc:creator>
            <pubDate>Fri, 30 Sep 2022 11:18:21 GMT</pubDate>
            <atom:updated>2022-09-30T11:38:22.350Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wCAd05IbXyw8uZ3n.jpg" /><figcaption>Image Source: Google</figcaption></figure><p>I’m sure you will love to read through it. After the end of this article, I will love to see you dive deep into your passion.</p><p>In retrospect, my childhood was full of fun, dismantling electronic gadgets just to rearrange them, as in the former. It started with a toy phone I got; I always wanted to know what exactly was inside that made it produce sound. I’m constantly losing screws and repairing shattered lamps that appear dilapidated. I also went on to lose our working electric standing fan.</p><p>I learned this earlier — that your passion will always find you. My passion discovered me; I never stopped at losing electrical appliances but went on to dismantle a whole engine of a generator trying to fix it. You’d say what kind of personality this is, LOL, it’s in-built, and it worked out in one way: I did all the electrical repair work in our home with little knowledge gained in high school.</p><p>All this, coupled with my interest in solving knot technical problems — I don’t give up solving them halfway; my parents knew me for this — and also the fact that I find it very easy to store digits and play around with them, as well as ease in operating phones, to cut it short, With my interest in building creative things, I unknowingly got into graphics during the COVID-19 lockdown, and I ventured into it to some extent before my passion finally found me out in my current sophomore year, some months ago. I always wanted to code, but I never knew what it was. I remembered asking a tech-savvy what tech really is, and he gave me an answer that actually drove me to know about it and dive into it.</p><p>My journey officially began a few months ago when I attended a tech webinar titled “Finding Your Purpose in Tech,” hosted by @Temidayo Salako. I wasn’t able to attend live, but I listened to the recorded sections, which included an amazing tech-savvy lady, @Grace Omole, whose knowledge in the tech space is admirable.</p><p>The host also spoke about some areas in tech, made mention of data science, and mentioned many of the gifts I have, relating them to data science, which actually made me navigate into the data field and, with God’s will and advice from loved ones, went into data engineering, which I’m currently fully exploring and enjoying every bit of, and my dream is to be a technical problem solver to my world and to use technology for the betterment of the world.</p><p>In conclusion, my purpose for writing this is to make some individuals like me dive deep for their passion with God’s help in making it through it, and I hope it did.</p><p>Thank you for reading!</p><p>Watch out for some of my articles on the step-by-step completion of a real, live, end-to-end EDA project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6bddccdd621" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>