cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
520
Views
0
Helpful
3
Replies

Config R2 to block 30.1.1.1/8 make sure R2 don't install in its table

krahulbgp
Level 1
Level 1

 

Config R2 to block 30.1.1.1/8 make sure R2 do not intsllat in its routing table
why & how "ip prefix-list INK permit 0.0.0.0/0 le32" used here ? why 30.1.1.1/8 prefix is not used ? can any one   explain 

BGP Q1.PNG

 

3 Replies 3

Deepak Kumar
VIP Alumni
VIP Alumni

Hello,

I have doubt that this prefix is blocking any thing. Prefix: 0.0.0.0/0 le 32 matches any prefix with a length between 0 and 32 bits (inclusive). This matches all possible IPv4 prefixes.

 

if you want to block  30.1.1.1/8  than your prefix list would be 

 

ip prefix-list INK deny 30.0.0.0/8

ip prefix-list INK permit 0.0.0.0/0 le 32

 

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

that is correct that should be but  how "ip prefix-list INK permit 0.0.0.0/0 le32" used here , i doubt it too ,let us have some more output on this  

Hello,

 

As @Deepak Kumar mentioned the first statement denies the prefix you want (however looking at your diagram are you sure you didn’t want to deny the 3.1.1.1/8 prefix?).

 

The second statement permits all other prefixes.

As with ACLs, Prefix lists, route-maps they all

havw implicit Denies at the end. So if you didn’t permit anything after your initial statement then you would deny your prefix in the first entry and implicitly deny everything else, so

functionally you would deny everything.

 

Hope that helps

 

-David

Review Cisco Networking for a $25 gift card