[169653] in North American Network Operators' Group
Re: As path for Junos
daemon@ATHENA.MIT.EDU (Pedro Cavaca)
Fri Mar 7 14:44:55 2014
In-Reply-To: <CAHDg04uteLxO0eFKks3m2GtvXhDoiZf8bVTNXo-3KWgfUk2UpQ@mail.gmail.com>
From: Pedro Cavaca <pmsac.nanog@gmail.com>
Date: Fri, 7 Mar 2014 19:44:10 +0000
To: Michael Loftis <mloftis@wgops.com>
Cc: nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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
>
>
