[j-nsp] AS path access list (regexp)

Scott Morris swm at emanon.com
Fri Apr 20 09:13:52 EDT 2007


For prepend stuff, what about something like:

regexp ^1000(_[1-9]+)(\1)*(_[1-9]+)(\2)*$

Assuming 1000 is your peering AS, then the other (up to) two AS's could have
the same number repeat itself.

Just a thought.

Scott


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Daniel Lete
Sent: Friday, April 20, 2007 8:03 AM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] AS path access list (regexp)

Hello Kanagaraj,

^.{1,3}$
will allow an AS_PATH which depth is between 1 and 3 AS

it will not cater though for either the first, second or third AS doing
AS_PATH prepending.

Daniel


Kanagaraj Krishna wrote:
> Hi,
>      I have this AS path access list to one of my BGP peerings (inbound
route map) which is based on Cisco to set different local pref to:
> 
> - direct peering AS
> - direct peering AS + 1st AS hop
> - direct peering AS + 1st AS hop + 2nd AS hop
> 
> Based on Cisco
> -----------------------
>   ip as-path access-list 77 permit ^(ABCD_)+$
>   ip as-path access-list 77 permit ^(ABCD_)+[0-9]+$
>   ip as-path access-list 77 permit ^(ABCD_)+[0-9]+_[0-9]+$
> 
> 
> How do i mirror the same requirement on a Juniper? Thanks.
> 
> Regards,
> Kana
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 

--
Daniel Lete Murugarren
HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5
George's Dock, IFSC, Dublin 1 Registered in Ireland, no 275301  tel:
+353-1-660 9040  fax: +353-1-660 3666
web: http://www.heanet.ie/
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



More information about the juniper-nsp mailing list