cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
679
Views
5
Helpful
6
Replies

EIGRP and route filtering with route map & access-list

iores
Level 3
Level 3

Hi,

I have a question regarding EIGRP route filtering with route map and extended access list (ACL).

 

This is the reference routing table BEFORE route filtering:

10.0.0.0/8 is variably subnetted, 9 subnets, 7 masks
D        10.0.0.1/32 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.0.0.2/32 [90/130816] via 172.16.0.9, 00:02:37, GigabitEthernet0/3
C        10.0.0.3/32 is directly connected, Loopback0
D        10.1.0.0/16 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.2.0.0/17 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.3.0.0/18 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.4.0.0/19 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.5.0.0/20 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1
D        10.5.20.0/22 [90/130816] via 172.16.0.5, 00:02:37, GigabitEthernet0/1

I want to filter out the prefixes in bold. Everything works fine when I create the extended ACL:

 

10 permit ip 10.5.0.0 0.0.255.255 255.255.240.0 0.0.15.0

and apply it to the route map:

route-map FIL, deny, sequence 10
  Match clauses:
    ip address (access-lists): ACL1 
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map FIL, permit, sequence 20
  Match clauses:
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes

QUESTION:

 

However, if I add the second line to the ACL:

20 permit ip any any

every 10.x.x.x gets filtered out, except the 10.0.0.3/32 (local)

 

Can somebody, please, explain why is this happening?

 

Thank you!

 

 

1 Accepted Solution

Accepted Solutions

 

Might have been worth mentioning that in your original post. 

 

Can you post the full configuration of the router. 

 

Jon

View solution in original post

6 Replies 6

....

Jon Marshall
Hall of Fame
Hall of Fame

 

Because you have used "permit ip any any" which matches every EIGRP route and therefore they are all filtered. 

 

The reason 10.0.0.3/32 is still there is because it is not an EIGRP route. 

 

Jon

 

 

But there are also 172.x.x.x prefixes in the routing table (not shown above) and they remain there. Only 10.x.x.x prefixes are filtered out.

 

Might have been worth mentioning that in your original post. 

 

Can you post the full configuration of the router. 

 

Jon

Hi Jon,

 

I think I found the answer just as I was going to copy the full configuration and routing table.

 

Only prefixes that remain in the routing table are those for Connected/Local interfaces, including 172.x.x.x prefixes, and there are none EIGRP routes after adding

permit ip any any

to the access list. I was confused because I didn't not look carefully at the routing table at first.

 

Thank you for your time, nonetheless.

...