ip route policy LAB - what am I doing wrong?

[anestis.iliadis]

Hi all,

I'm doing a route-policy LAB and it's driving me crazy! I must be doing something wrong but have no idea what... so please help me out.

ok so we have

LAN A 192.168.4.0     /25

LAN B 192.168.4.128 /25  <-- want to PBR

the objective is to set a different next hop address depending on whether the source ip is from LAN A or LAN B... easy enough.

The problem is that in the route-map that does the policy routing, if I match the addresses using an ACL it works fine. Then I thought, I'd try a prefix list but it doesn't work at all... here's what I mean

a) ACL

ip access-list 11 permit 192.168.4.128 0.0.0.127

route-map TEST1 permit 10

match ip addr 11

set ip next hop <some IP>

          -works fine

b) Prefix-list

ip prefix-list PREF seq 5 permit 192.168.4.128/25

route-map TEST2 permit 10

match ip addr prefix-list PREF

set ip next hop <some IP>

          -doesn't work

now the reason that is driving me crazy is that with b) EVERYTHING is matched and forwarded by PBR.

I did debug ip policy and for some reason even 172.16.x.x addresses are matched and forwarded by PBR.

I thought to myself, ok maybe the prefix list is wrong... fair enough, then nothing should be matched, or maybe a combination of LANA,LANB but not everything even different class IPs, right?!!

Any idea what is going on?

thank you,

[cadet alain]

Hi,

you can't use prefix-lists for PBR, they can't match the source IP of a packet because they are used to match routes.

Regards

Alain

Don't forget to rate helpful posts.

[anestis.iliadis]

Hi Alain,

do you mind elaborating a little bit please? Any reason why everything is matched?

[cadet alain · Accepted solution]

Hi,

for the router it is like there was no match statement so it is match everything.

Regards

Alain

Don't forget to rate helpful posts.

[anestis.iliadis]

Thank you for the answer it's very clear why now! I can't believe I missed that!