GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: regexp fun (was RE: Filtering BGP updates using ip as-path access-lists) posted 08/21/2002
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


Abidin,

	But at the same time, you must take into account that it may not
have transited any other AS's :)

1000 100 10

and

1000 1 2 3 100 4 5 6 10


HTH

Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@xxxxxxxxxxxxxxx

CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625


-----Original Message-----
From: Abidin Kahraman [mailto:kahramana@xxxxxxxxxxxxxxx] 
Sent: Wednesday, August 21, 2002 10:37 AM
To: Brian McGahan; Abidin Kahraman; 'elping'; 'Michael Snyder'
Cc: steven.j.nelson@xxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
access-lists)

You are right Brian, 

What about ^1000(_.+_)100(_.+_)10$

Abidin.

-----Original Message-----
From: Brian McGahan [mailto:brian@xxxxxxxxxxxxxxx] 
Sent: Wednesday, August 21, 2002 6:19 PM
To: 'Abidin Kahraman'; 'elping'; 'Michael Snyder'
Cc: steven.j.nelson@xxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
access-lists)

Abidin,

	You have to take into consideration that it may have transited
other AS's in the meantime.  Test it against:

1000 1 2 3 100 4 5 6 10

HTH

Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@xxxxxxxxxxxxxxx

CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625


-----Original Message-----
From: Abidin Kahraman [mailto:kahramana@xxxxxxxxxxxxxxx] 
Sent: Wednesday, August 21, 2002 10:02 AM
To: Brian McGahan; 'elping'; 'Michael Snyder'
Cc: steven.j.nelson@xxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
access-lists)

Is this ok ?

^1000_100(_.+_)10$ 

I`ve tried on my router and it seems ok, what is your ideas?

Abidin.
-----Original Message-----
From: Brian McGahan [mailto:brian@xxxxxxxxxxxxxxx] 
Sent: Wednesday, August 21, 2002 5:21 PM
To: 'Brian McGahan'; 'elping'; 'Michael Snyder'
Cc: steven.j.nelson@xxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: regexp fun (was RE: Filtering BGP updates using ip as-path
access-lists)

	Did we give up already?

<snip>

	Try this one: All routes originated in AS 10, passed through AS
100, and learned from AS 1000.  (In one line)

HTH

Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@xxxxxxxxxxxxxxx

CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625


-----Original Message-----
From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf Of
elping
Sent: Sunday, August 18, 2002 9:46 AM
To: Michael Snyder
Cc: steven.j.nelson@xxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: Re: Filtering BGP updates using ip as-path access-lists

steve :
consider that
^4 [0-9]* will be an exact 4 and some other number
so any routes coming from 4 will not show up...

i put your theory to the test on an actual Bgp routing table observ.
I am using 7788 and all it's connected routes..

in summary the underscore will allow 7788 routes and it's
connected...without the underscore
you are saying a exact 7788 and it's connected.....see for yourself...

if i mistyped or got you thoughts wrong feel free to correct..



using your string i obtain nothing
route-server.east>sh ip bgp reg ^7788 [0-9]* [0-9]*$
route-server.east>

observ the string sh ip bgp reg ^7788_[1-9]*$  ---that is with the
underscore
route-server.east>sh ip bgp reg ^7788 [0-9]* [0-9]*$

route-server.east>sh ip bgp reg ^7788_[1-9]*$
BGP table version is 97446699, local router ID is 216.191.65.118
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*>i64.26.128.0/18   216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
*>i192.203.106.0    216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i192.222.1.0      216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i192.222.2.0/23   216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i192.222.4.0/22   216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i192.222.8.0      216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i198.96.127.0     216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i198.96.199.0     216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i199.71.68.0      216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i204.138.103.0    216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i204.187.103.0    216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i204.225.145.0    216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i205.207.175.0    216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i205.233.68.0     216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i206.51.251.0     216.191.224.1                 100      0 7788 i
* i                 216.191.224.1                 100      0 7788 i
*>i206.191.0.0/18   216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
*>i209.217.64.0/18  216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
route-server.east>

observe without the underscore sh ip bgp reg ^7788 [1-9]*$

route-server.east>sh ip bgp reg ^7788 [1-9]*$
BGP table version is 97446794, local router ID is 216.191.65.118
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*>i64.26.128.0/18   216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
*>i206.191.0.0/18   216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
*>i209.217.64.0/18  216.191.224.1                 100      0 7788 7788 i
* i                 216.191.224.1                 100      0 7788 7788 i
route-server.east>sh ip bgp reg ^7788_[1-9]*$




Michael Snyder wrote:

> _ (Matches a comma (,), left brace ({), right brace (}), the beginning
> of the input string, the end of the input string, or a space.
>
> Steve I just wanted to match a space. Thats why I didn't use _ ,
Cisco
> shows examples of not using _ to match spaces.  In other words, a
space
> char will match a space character.
>
> I stand by my expression of ^4 [0-9]* [0-9]*$
>
> I think another legal expression would be ^4 12 16 3$ notice that _
> isn't needed.
>
> -----Original Message-----
> From: steven.j.nelson@xxxxxx [mailto:steven.j.nelson@xxxxxx]
> Sent: Thursday, August 15, 2002 10:14 AM
> To: msnyder@xxxxxxx
> Subject: RE: Filtering BGP updates using ip as-path access-lists
>
> Michael
>
> You have missed out the _
>
> ^4_[0-9]*_[0-9]*$
>
> Steve
>
> -----Original Message-----
> From: Michael Snyder [mailto:msnyder@xxxxxxx]
> Sent: 15 August 2002 15:53
> To: 'Chaim Gev'
> Cc: ccielab
> Subject: RE: Filtering BGP updates using ip as-path access-lists
>
> ^4 [0-9]* [0-9]*$
>
> Would match any AS that was directly connected to an AS that was
> directly connected to AS 4.  Is this correct?
>
> Also I think the expression you cited ^_4_[0-9]*$ is different than
> ^4_[0-9]*$. If they are the same, why not use the shorter one?
>
> Please Advise
>
> -----Original Message-----
> From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf
Of
> Chaim Gev
> Sent: Thursday, August 15, 2002 8:13 AM
> To: msnyder@xxxxxxx; raj.bahad@xxxxxxxxxxxxxx
> Cc: ccielab@xxxxxxxxxxxxxx
> Subject: RE: Filtering BGP updates using ip as-path access-lists
>
> The "*" means "match 0 or more sequences of the pattern" which is null
> in
> your suggestion.
> ^_4_[0-9]*$ is more accurate if you are asked to filter exactly AS4
(and
> not
> AS14).
>
> >From: "Michael Snyder" <msnyder@xxxxxxx>
> >Reply-To: "Michael Snyder" <msnyder@xxxxxxx>
> >To: "'Raj'" <raj.bahad@xxxxxxxxxxxxxx>
> >CC: <ccielab@xxxxxxxxxxxxxx>
> >Subject: RE: Filtering BGP updates using ip as-path access-lists
> >Date: Thu, 15 Aug 2002 07:52:31 -0500
> >
> >I'm no expert on as-path access-lists.
> >
> >But, I believe the $ is the main difference.
> >
> >^4_  anything beginning with as path 4.
> >
> >^4_[0-9]*$ anything beginning with as path 4 and ENDS with one
> >additional AS.
> >
> >Which brings up a question of mine,
> >
> >Why wouldn't ^4_*$ do the same thing?
> >
> >
> >
> >-----Original Message-----
> >From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf
Of
> >Raj
> >Sent: Thursday, August 15, 2002 7:02 AM
> >To: ccielab@xxxxxxxxxxxxxx
> >Subject: Filtering BGP updates using ip as-path access-lists
> >
> >Hi all,
> >
> >I've come across a scenario for which I require some clarification.
> >
> >I want to permit only networks originated from AS4, and AS's directly
> >attached to AS4. I use the following config to meet the requirements,
> >however I have come across documentation that has achieved the same
> >results
> >using a slightly different version. I've listed both of them below:
> >
> >ip as-path access-list 1 permit ^4_
> >
> >and the other being:
> >
> >ip as-path access-list 1 permit ^4_[0-9]*$
> >
> >Could someone please help clarify why one method would be preferred
> over
> >the
> >other?
> >
> >Thanks,
> >
> >Raj.
> >_________________________________________________________________
> >Commercial lab list: http://www.groupstudy.com/list/commercial.html
> >Please discuss commercial lab solutions on this list.
> >_________________________________________________________________
> >Commercial lab list: http://www.groupstudy.com/list/commercial.html
> >Please discuss commercial lab solutions on this list.
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
> _________________________________________________________________
> Commercial lab list: http://www.groupstudy.com/list/commercial.html
> Please discuss commercial lab solutions on this list.
> _________________________________________________________________
> Commercial lab list: http://www.groupstudy.com/list/commercial.html
> Please discuss commercial lab solutions on this list.
> _________________________________________________________________
> Commercial lab list: http://www.groupstudy.com/list/commercial.html
> Please discuss commercial lab solutions on this list.
_________________________________________________________________
Commercial lab list: http://www.groupstudy.com/list/commercial.html
Please discuss commercial lab solutions on this list.
_________________________________________________________________
Commercial lab list: http://www.groupstudy.com/list/commercial.html
Please discuss commercial lab solutions on this list.
_________________________________________________________________
Commercial lab list: http://www.groupstudy.com/list/commercial.html
Please discuss commercial lab solutions on this list.
************************************************************************
***
Bu e-posta mesaji ve ekleri sadece gonderildigi kisi veya kuruma
ozeldir.
Eger dogru kisiye ulasmadigini dusunuyorsaniz, bu mesajin gizlenmesi,
yonlendirilmesi, kopyalanmasi veya herhangi bir sekilde kullanilmasi
yasaktir.
Mesaj iceriginde bulunan fikir ve yorumlar, Superonline'a degil sadece
gondericiye aittir.
Bu mesaj bilinen tum viruslere karsi test edilmistir.
 
************************************************************************
***
This e-mail and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you are not the intended recipient you are hereby notified that any
dissemination, forwarding, copying or use of any of the information is
prohibited.
The opinions expressed in this message belong to sender alone. There is
no
implied endorsement by SUPERONLINE.
This e-mail has been scanned for all known computer viruses.
************************************************************************
***





************************************************************************
***
Bu e-posta mesaji ve ekleri sadece gonderildigi kisi veya kuruma
ozeldir.
Eger dogru kisiye ulasmadigini dusunuyorsaniz, bu mesajin gizlenmesi,
yonlendirilmesi, kopyalanmasi veya herhangi bir sekilde kullanilmasi
yasaktir.
Mesaj iceriginde bulunan fikir ve yorumlar, Superonline'a degil sadece
gondericiye aittir.
Bu mesaj bilinen tum viruslere karsi test edilmistir.
 
************************************************************************
***
This e-mail and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you are not the intended recipient you are hereby notified that any
dissemination, forwarding, copying or use of any of the information is
prohibited.
The opinions expressed in this message belong to sender alone. There is
no
implied endorsement by SUPERONLINE.
This e-mail has been scanned for all known computer viruses.
************************************************************************
***
_________________________________________________________________
Commercial lab list: http://www.groupstudy.com/list/commercial.html
Please discuss commercial lab solutions on this list.
__________________________________________________________________
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab