Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: nsp: juniper

bgp regexp

 

 

nsp juniper RSS feed   Index | Next | Previous | View Threaded


mihaigabriel at gmail

Aug 29, 2012, 2:05 AM

Post #1 of 2 (253 views)
Permalink
bgp regexp

Hello,

I am reading the bgp regexp examples on Juniper site (
http://www.juniper.net/techpubs/en_US/junos10.2/topics/usage-guidelines/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html)
and I cannot understand this sentence:


Path whose second AS number might be 56 or 78: dot (56 | 78)?
The matching is: 1234 78 39 or 794 78 2

How could this regexp match 1234 78 39 when there is not at least a dot at
the end of expression?

Regards,
_______________________________________________
juniper-nsp mailing list juniper-nsp [at] puck
https://puck.nether.net/mailman/listinfo/juniper-nsp


saku at ytti

Aug 29, 2012, 3:24 AM

Post #2 of 2 (234 views)
Permalink
Re: bgp regexp [In reply to]

On (2012-08-29 12:05 +0300), Mihai Gabriel wrote:

> Path whose second AS number might be 56 or 78: dot (56 | 78)?
> The matching is: 1234 78 39 or 794 78 2
>
> How could this regexp match 1234 78 39 when there is not at least a dot at
> the end of expression?

It should not, JNPR has regexp wrapped around implicit ^$. So I think you
just found bug in documentation.

--
++ytti
_______________________________________________
juniper-nsp mailing list juniper-nsp [at] puck
https://puck.nether.net/mailman/listinfo/juniper-nsp

nsp juniper RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.