LAB: EIGRP Stub routing with leak Map

requirements:
- Configure the EIGRP stub feature in such a way that R5 does not receive EIGRP query messages.
- R5 should continue to advertise all learned routes with the exception of SW2’s Loopback0 network.

config set:

R5:
ip prefix-list SW2_LOOPBACK seq 5 permit 150.1.8.0/24
!
route-map STUB_LEAK_MAP deny 10
match ip address prefix-list SW2_LOOPBACK
!
route-map STUB_LEAK_MAP permit 20
!
router eigrp 100
eigrp stub connected leak-map STUB_LEAK_MAP

The leak-map feature of EIGRP stub, like the leak-map for EIGRP summarization, allows the advertisement of routes that would normally be suppressed. When R5 is configured with only the eigrp stub command, it cannot be used as transit. This can be seen from the routing table views of SW2 and R3.

show commands:

before stub connected is applied:
Rack1R3#show ip route | inc via 155.1.0.5
D EX 204.12.1.0/24 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D 155.1.8.0 [90/514816] via 155.1.0.5, 00:01:26, Serial1/0.1
D 155.1.5.0 [90/514560] via 155.1.0.5, 00:01:26, Serial1/0.1
D 155.1.58.0 [90/514560] via 155.1.0.5, 00:01:26, Serial1/0.1
D 155.1.45.0 [90/1024000] via 155.1.0.5, 00:01:26, Serial1/0.1
D 155.1.108.0 [90/517120] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 31.3.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 31.2.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 31.1.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 31.0.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D 150.1.5.0 [90/640000] via 155.1.0.5, 00:01:26, Serial1/0.1
D 150.1.4.0 [90/1152000] via 155.1.0.5, 00:01:26, Serial1/0.1
D 150.1.8.0 [90/642560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 30.2.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 30.3.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 30.0.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D EX 30.1.0.0 [170/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1
D* 0.0.0.0/0 [90/1026560] via 155.1.0.5, 00:01:26, Serial1/0.1


R3 "when stub connected" with leak map used @ R5

Rack1R3#show ip route | inc via 155.1.0.5,
D EX 204.12.1.0/24 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D 155.1.8.0 [90/514816] via 155.1.0.5, 00:17:53, Serial1/0.1
D 155.1.5.0 [90/514560] via 155.1.0.5, 00:17:53, Serial1/0.1
D 155.1.58.0 [90/514560] via 155.1.0.5, 00:17:53, Serial1/0.1
D 155.1.45.0 [90/1024000] via 155.1.0.5, 00:17:53, Serial1/0.1
D 155.1.108.0 [90/517120] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 31.3.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 31.2.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 31.1.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 31.0.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D 150.1.5.0 [90/640000] via 155.1.0.5, 00:17:53, Serial1/0.1
D 150.1.4.0 [90/1152000] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 30.2.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 30.3.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 30.0.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D EX 30.1.0.0 [170/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1
D* 0.0.0.0/0 [90/1026560] via 155.1.0.5, 00:17:53, Serial1/0.1


Rack1R3#show ip route | include via 155.1.0.5
D 155.1.8.0 [90/514816] via 155.1.0.5, 00:00:00, Serial1/0.1
D 155.1.5.0 [90/514560] via 155.1.0.5, 00:00:02, Serial1/0.1
D 155.1.58.0 [90/514560] via 155.1.0.5, 00:00:02, Serial1/0.1
D 155.1.45.0 [90/1024000] via 155.1.0.5, 00:00:02, Serial1/0.1
D 155.1.108.0 [90/517120] via 155.1.0.5, 00:00:00, Serial1/0.1
D 150.1.5.0 [90/640000] via 155.1.0.5, 00:00:02, Serial1/0.1

Rack1R3#show ip route 150.1.8.8
% Subnet not in table