nanog mailing list archives
Re: As path for Junos
From: Pedro Cavaca <pmsac.nanog () gmail com>
Date: Fri, 7 Mar 2014 19:44:10 +0000
On 7 March 2014 19:26, Michael Loftis <mloftis () wgops com> wrote:
http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html There's no backref support in the regex subset that juniper has chosen to implement, see http://juniper.cluepon.net/index.php/ER_Detect_AS-PATH_prepends - and I don't think Juniper has gone anywhere with that engineering request.
Why wouldn't ".{3}" work, for this case?
On Fri, Mar 7, 2014 at 3:31 AM, Marco Paesani <marco () paesani it> wrote:Hi Everyone, I need a help to transform this Cisco IOS command: ip as-path access-list 50 permit _([0-9]+)_\1_\1_ in Juniper JUNOS policy-options. Best regards, Marco M. +39 348 6019349-- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler
Current thread:
- As path for Junos Marco Paesani (Mar 07)
- Re: As path for Junos Michael Loftis (Mar 07)
- Re: As path for Junos Pedro Cavaca (Mar 07)
- Re: As path for Junos Pedro Cavaca (Mar 07)
- Re: As path for Junos Marco Paesani (Mar 07)
- Re: As path for Junos Saku Ytti (Mar 08)
- Re: As path for Junos Pedro Cavaca (Mar 08)
- Re: As path for Junos Pedro Cavaca (Mar 07)
- Re: As path for Junos Michael Loftis (Mar 07)
- Re: open source with flowspec ? ML (Mar 13)
- Re: open source with flowspec ? joel jaeggli (Mar 13)
- Re: open source with flowspec ? Tom Hill (Mar 20)