EIGRP FILTERING WITH STUB ROUTING

Task 1
Add two more loopbacks on R4 with the respective addresses:
Loopback 2: 10.0.4.4/24
Loopback 3: 10.0.44.4/24
Advertise them as External prefixes.
Task 2
Configure R4 so that it can advertise only connected and summary routes in EIGRP. It should not
be queried by R1 and/or R2 if they lose any EIGRP prefix.

Lab Solution
Task 1
Add two more loopbacks on R4 with the respective addresses:
Loopback 2: 10.0.4.4/24
Loopback 3: 10.0.44.4/24
Advertise them as External prefixes.
R4 Configuration:
!
interface Loopback2
ip address 10.0.4.4 255.255.255.0
!

interface Loopback3
ip address 10.0.44.4 255.255.255.0
!
route-map CONNECTED permit 10
match interface Loopback2 Loopback3
!
router eigrp 1
redistribute connected route-map CONNECTED
network 10.1.124.4 0.0.0.0
network 172.16.104.4 0.0.0.0
network 172.16.144.4 0.0.0.0
!
Verification:
Pic. 2 - R3 Receives External Prefixes.

Task 2
Configure R4 so that it can advertise only connected and summary routes in EIGRP. It should not
be queried by R1 and/or R2 if they lose any EIGRP prefix.
R4 Configuration:
!
router eigrp 1
redistribute connected route-map CONNECTED
network 10.1.124.4 0.0.0.0
network 172.16.104.4 0.0.0.0
network 172.16.144.4 0.0.0.0
eigrp stub connected summary
!
Pic. 3 - EIGRP Stub Options (the defaults in yellow).

Verification:
Pic. 4 - R1 Sees R4 as the Stub Router.

R4 can now only advertise directly connected networks/subnets (these enabled in EIGRP) as well
as summary route (the defaults in 'stub' command). Also R1 and R2 are not going to send EIGRP
Query packets upon losing their EIGRP prefixes.
Note!
Even though R4 is a 'stub' router allowing connected and summary routes, it does advertise EIGRP
prefixes that have been redistributed. They are still connected enabled (redistributed) in EIGRP.
Pic. 5 - R3's External Prefixes.

EIGRP WITH STUB ROUTING AND LEAK MAPS

Task 1
Using the lab 52 config, remove eigrp stub command on R4.
Task 2
Configure R1 and R2 as EIGRP stub routers. Use default options (connected and summary).
Task 3
Keeping R1 and R2 EIGRP stub routers allow R1 to advertise 10.0.44.0/24.
Task 4
Keeping R1 and R2 EIGRP stub routers allow R2 to advertise 10.0.4.0/24.

Lab Solution
Task 1
Using the lab 52 config, remove eigrp stub command on R4.
R4 Configuration:
!
R4(config-router)#no eigrp stub
R4(config-router)#
!

Task 2
Configure R1 and R2 as EIGRP stub routers. Use default options (connected and summary).
R1 Configuration:
!
router eigrp 1
network 10.1.13.1 0.0.0.0
network 10.1.123.1 0.0.0.0
network 10.1.124.1 0.0.0.0
network 172.16.101.1 0.0.0.0
no auto-summary
eigrp stub connected summary
!
R2 Configuration:
!
router eigrp 1
network 10.1.123.2 0.0.0.0
network 10.1.124.2 0.0.0.0
network 172.16.102.2 0.0.0.0
no auto-summary
eigrp stub connected summary
!
Verification:
Pic. 2 - R3 Routing Table.

Notice!
R3 does not receive R4's prefixes because R1 and R2 filters them out (only connected and
summary routes can be advertised by R1 and R2).
Task 3
Keeping R1 and R2 EIGRP stub routers allow R1 to advertise 10.0.44.0/24.
R1 Configuration:
!
ip prefix-list R4_L3 seq 5 permit 10.0.44.0/24
!
route-map LEAK permit 10
match ip address prefix-list R4_L3
!
router eigrp 1
network 10.1.13.1 0.0.0.0
network 10.1.123.1 0.0.0.0
network 10.1.124.1 0.0.0.0
network 172.16.101.1 0.0.0.0

no auto-summary
eigrp stub connected summary leak-map LEAK
!
Verification:
Pic. 3 - R3's Routing Table.

Notice!
R1 unsuppressed 10.0.44.0/24. It takes a moment longer to advertise the same prefix over S0/0 as
it is a slow link. Also, while using 'leak-map' the defaults (connected and summary) are not added
unless manually typed in.
Task 4
Keeping R1 and R2 EIGRP stub routers allow R2 to advertise 10.0.4.0/24.
R2 Configuration:
!
ip prefix-list R4_L2 seq 5 permit 10.0.4.0/24
!
route-map LEAK permit 10
match ip address prefix-list R4_L2
!
router eigrp 1
network 10.1.123.2 0.0.0.0
network 10.1.124.2 0.0.0.0
network 172.16.102.2 0.0.0.0
no auto-summary
eigrp stub connected summary leak-map LEAK
!
Verification:
Pic. 4 - R3's Routing Table.