9‐2 Build a Network Challenge 2 - Snowboundport37/champlain GitHub Wiki

<title>NET-330 • Lab 9-2 • Build a Network Challenge 2 • BGP</title> <style> :root { --bg:#0d1117; --panel:#161b22; --ink:#c9d1d9; --link:#58a6ff; --mono:#a5d6ff; } html,body{background:var(--bg); color:var(--ink); font-family:ui-sans-serif,system-ui,Segoe UI,Roboto,Ubuntu,"Helvetica Neue",Arial;} h1,h2,h3{color:var(--link); margin:1.2rem 0 .4rem} p,li{line-height:1.55} .grid{display:grid; gap:14px} .two{grid-template-columns:repeat(auto-fit,minmax(320px,1fr))} .card{background:var(--panel); border:1px solid #30363d; border-radius:10px; padding:14px} code,kbd,pre{font-family:ui-monospace, SFMono-Regular, Menlo, Consolas, "Liberation Mono", monospace} pre{background:#0f1420; border:1px solid #283142; border-radius:10px; padding:12px; overflow:auto; color:var(--mono)} .todo{background:#12221a; border-color:#1f6f42} .ok{color:#56d364} a{color:var(--link); text-decoration:none} .small{font-size:.95rem} .muted{color:#8b949e} .k{color:#ffd580} </style>

Lab 9-2 • Build a Network Challenge 2 • BGP

Course: NET-330 • Points: 100 • Deliverable: single lab report with configs and proof

Objective

Extend Foster 202 Company connectivity to a Partner network and a Customer network using BGP, while keeping OSPF inside Foster 202. All laptops must reach each other. No static routes except the single default on BTV Router.

Topology summary

  • Foster 202 AS 3033 runs OSPF inside the company.
  • Vermont ISP AS 1010 peers with Pacific ISP and with BTV Router.
  • Pacific ISP AS 2054 peers with Vermont ISP, Partner, Customer.
  • Partner Company AS 34908 advertises 10.15.6.0/24.
  • Customer Company AS 5132 advertises 10.200.24.0/24.

Key links and addresses

  • Vermont ISP ↔ Pacific ISP: 192.168.1.1/30 ↔ 192.168.1.2/30
  • Vermont ISP ↔ BTV Router: 192.168.2.1/30 ↔ 192.168.2.2/30
  • Pacific ISP ↔ Partner: 192.168.3.1/30 ↔ 192.168.3.2/30
  • Pacific ISP ↔ Customer: 192.168.4.1/30 ↔ 192.168.4.2/30
  • Partner LAN: 10.15.6.0/24 gateway 10.15.6.1
  • Customer LAN: 10.200.24.0/24 gateway 10.200.24.1

Foster 202 internal subnets

  • BTV ↔ MTL link: 172.16.0.0/30
  • BTV Core: 172.16.10.0/24
  • User VLAN: 172.16.5.0/24
  • Data Center VLAN: 172.16.6.0/24
  • Montreal LAN: 172.16.20.0/24

What I built

  1. Left OSPF running inside Foster 202. Added a single default on BTV Router that points to Vermont ISP.
  2. Turned on EBGP sessions across all ISP edges and to Partner and Customer.
  3. Redistributed OSPF from BTV Router into BGP for AS 3033 so the ISPs learn all Foster 202 routes.
  4. Verified reachability by pinging between Partner PC, Customer PC, and Foster 202 hosts. All pings succeed.

Device configurations

BTV Router • Foster 202 • AS 3033

enable
configure terminal
! Interfaces are already addressed (Fa0/0 172.16.10.1, S0/1/0 172.16.0.1, Fa0/1 192.168.2.2)
ip route 0.0.0.0 0.0.0.0 192.168.2.1

router ospf 1
network 172.16.0.0 0.0.0.3 area 0
network 172.16.10.0 0.0.0.255 area 0
default-information originate


! EBGP with Vermont ISP so we can export our OSPF routes outward
router bgp 3033
bgp log-neighbor-changes
neighbor 192.168.2.1 remote-as 1010
redistribute ospf 1

BTV 3550 Multilayer Switch • Foster 202

enable
configure terminal
ip routing
interface vlan5
 ip address 172.16.5.1 255.255.255.0
 no shutdown
interface vlan6
 ip address 172.16.6.1 255.255.255.0
 no shutdown
interface vlan10
 ip address 172.16.10.2 255.255.255.0
 no shutdown
router ospf 1
 network 172.16.5.0 0.0.0.255 area 0
 network 172.16.6.0 0.0.0.255 area 0
 network 172.16.10.0 0.0.0.255 area 0

MTL Router • Foster 202 • AS 3033 (OSPF only)

enable
configure terminal
! Interfaces: S0/1/0 172.16.0.2, Fa0/0 172.16.20.1
router ospf 1
 network 172.16.0.0 0.0.0.3 area 0
 network 172.16.20.0 0.0.0.255 area 0

Vermont ISP • AS 1010

enable
configure terminal
! Interfaces: Fa0/0 192.168.1.1 255.255.255.252, Fa0/1 192.168.2.1 255.255.255.252
router bgp 1010
 bgp log-neighbor-changes
 neighbor 192.168.1.2 remote-as 2054
 neighbor 192.168.2.2 remote-as 3033
 ! Advertise point to point nets if needed
 network 192.168.1.0 mask 255.255.255.252
 network 192.168.2.0 mask 255.255.255.252

Pacific ISP • AS 2054

enable
configure terminal
! Interfaces: Fa0/0 192.168.3.1, S0/1/0 192.168.1.2, Fa0/1 192.168.4.1
router bgp 2054
 bgp log-neighbor-changes
 neighbor 192.168.1.1 remote-as 1010
 neighbor 192.168.3.2 remote-as 34908
 neighbor 192.168.4.2 remote-as 5132
 network 192.168.1.0 mask 255.255.255.252
 network 192.168.3.0 mask 255.255.255.252
 network 192.168.4.0 mask 255.255.255.252

Partner Company • AS 34908

enable
configure terminal
! Interfaces: Fa0/0 192.168.3.2, Fa0/1 10.15.6.1
router bgp 34908
 bgp log-neighbor-changes
 neighbor 192.168.3.1 remote-as 2054
 network 10.15.6.0 mask 255.255.255.0

Customer Company • AS 5132

enable
configure terminal
! Interfaces: S0/1/0 192.168.4.2, Fa0/0 10.200.24.1
router bgp 5132
 bgp log-neighbor-changes
 neighbor 192.168.4.1 remote-as 2054
 network 10.200.24.0 mask 255.255.255.0

End device IPs

  • User-Laptop: 172.16.5.2/24 gw 172.16.5.1
  • DataCenter-Station: 172.16.6.2/24 gw 172.16.6.1
  • Montreal-Laptop: 172.16.20.2/24 gw 172.16.20.1
  • Partner-PC: 10.15.6.2/24 gw 10.15.6.1
  • Customer-PC: 10.200.24.2/24 gw 10.200.24.1

Verification

Core checks I ran.

! Pacific ISP
show ip route
show ip bgp summary

! Vermont ISP
show ip route
show ip bgp summary


! BTV Router
show ip route


! Customer PC
ping 172.16.6.2


! Partner PC
ping 10.200.24.2
ping 172.16.5.2

Results: all pings succeed. BGP neighborships show Established on all four peering points. Foster routes appear on the ISPs via redistribution from BTV Router.

Screenshots to include

  • Pacific ISP output of show ip route
  • Vermont ISP output of show ip route
  • BTV Router output of show ip route
  • Customer PC terminal showing success ping to DataCenter-Station 172.16.6.2
  • (optional but nice) show ip bgp summary on all BGP speakers

Notes and gotchas

  • Use copy running-config startup-config to save on every device.
  • Packet Tracer sometimes tries to resolve unknown words. If you accidentally type a bare word like wr or end while not in the right mode, it may try DNS. Disable name lookup if needed: no ip domain-lookup.
  • Make sure the point to point links have the correct port pairings. Example: Vermont Fa0/1 to BTV Fa0/1, Pacific Fa0/0 to Partner Fa0/0, and Pacific Fa0/1 to Customer S0/1/0 per the diagram.

Reflection • Tech journal

I kept OSPF inside the enterprise to keep reconvergence fast and to avoid leaking external paths into the interior. I added one default on BTV toward Vermont so hosts can exit the AS. I built EBGP on the edges and used a single redistribution point on BTV to announce all Foster 202 routes into BGP. This keeps policy simple and limits redistribution to one place. I validated with route tables and end to end pings from every campus to Partner and Customer. This pattern is reusable in future labs by keeping IGP inside, EBGP outside, and using a single redistribution boundary.

Place your topology image here: Build-a-Ne-Challenge2-BGP.jpg
Report authored by Andrei Gorlitsky

Champlain College - Andrei Gorlitsky's Academic Wiki

Welcome to my GitHub Wiki! This is where I document my entire Champlain College experience, including assignments, notes, and everything I've learned across all courses until I graduate.

This wiki serves as a central hub for my academic journey, showcasing my growth and knowledge in cybersecurity and beyond.

For more information about Champlain College, visit:
Champlain College

© Andrei Gorlitsky 2025 - Champlain College

⚠️ **GitHub.com Fallback** ⚠️