To the best of my knowledge, Juniper does not implement the back-reference in AS-path regular expressions. Therefore there is no direct translation available.
You should discuss the need for this with your account team, as an Enhancement Request. > -----Original Message----- > From: [email protected] [mailto:juniper-nsp- > [email protected]] On Behalf Of KJ > Sent: Thursday, July 29, 2010 5:46 AM > To: Daniel Verlouw > Cc: Juniper-Nsp > Subject: Re: [j-nsp] AS-path regexp clue needed > > Take a look here: > > http://www.juniper.net/techpubs/software/junos/junos74/swconfig74- > policy/html/policy-extend-match-config3.html > <http://www.juniper.net/techpubs/software/junos/junos74/swconfig74- > policy/html/policy-extend-match-config3.html> > > On 29 July 2010 14:18, Daniel Verlouw <[email protected]> wrote: > > > Hi, > > > > can someone give me some clue on how to translate the following Cisco > > regexp to Junos ? > > > > ip as-path access-list 1 permit ^([0-9]+)(_\1)*$ > > > > (this uses pattern recall to match AS paths whose first AS number in > the > > path is repeated zero or more times; basically to make sure certain > > customers prepend their own AS number only). > > > > IOS-to-Junos translator is unable to parse this and JTAC, well, let's > > just say they don't seem to get it -at all-. > > > > Of course, I could write a regexp per customer, but obviously this > > doesn't scale very well. > > > > --Daniel. > > > > _______________________________________________ > > juniper-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > > -- > //kjwilki > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
