From: Michael Snyder (msnyder@xxxxxxx)
Date: Thu Aug 22 2002 - 14:52:22 GMT-3
^1000_?.*_?100_?.*_?10$
Ok, lets end the thread, does the above met the criteria?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Edward Monk
Sent: Thursday, August 22, 2002 12:01 PM
To: 'Jake Nesbitt'; ccielab@groupstudy.com
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
ac cess-lists)
Jake,
Jake,
This regexp doesn't meet Brian's criteria.
What will output will be returned when you have nothing in between 1000
and 100? What about when you have nothing in between 100 and 10?
1000 1 100 10 <---- Does this work?
1000 100 1 10 <---- Does this work?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jake Nesbitt
Sent: Thursday, August 22, 2002 6:34 AM
To: ccielab@groupstudy.com
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
ac cess-lists)
Your right. I believe this should do it then:
^_1000_.*_100_.*_10_$
route-server.east>sh ip bgp regexp ^_701_.*_7431_.*_65_$
route-server.east>sh ip bgp regexp ^_70_.*_7431_.*_6571_$
route-server.east>sh ip bgp regexp ^_701_.*_7431_.*_6571_$
BGP table version is 98117058, 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
* i12.34.172.0/23 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i206.221.224.0/21 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i206.221.232.0/23 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i206.221.234.0 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i206.221.236.0/22 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i209.44.24.0/21 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
*>i209.176.214.0/23 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i209.176.216.0/21 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
* i 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
* i216.90.86.0 216.191.64.10 60 0 701 6347
7431
7431 7431 6571 i
*>i 216.191.64.4 60 0 701 6347
7431
7431 7431 6571 i
-----Original Message-----
From: Mingzhou Nie [mailto:mnie@yahoo.com]
Sent: Wednesday, August 21, 2002 11:27 PM
To: Jake Nesbitt; ccielab@groupstudy.com
Subject: RE: regexp fun (was RE: Filtering BGP updates using ip as-path
ac cess-lists)
Sure. But it will also match
- origin 810, pass thru 7100, 732, 3232, etc,
- origin 10010, pass thru 7382, 2329, 3281(just throw some numbers
here)
- origin 10010, no pass thru, learned from 1000
- and more
you have too broad matching here.
--- Jake Nesbitt <jake.nesbitt@verizon.net> wrote:
> How about:
>
> ^1000_.*100_.*10$
>
> should match any as-paths that originate in AS 10, pass through AS
> 100, and
> are learned from AS 1000.
>
> Couple of examples from route-server:
>
> route-server.east>sh ip bgp regexp ^701_.*1239_
> BGP table version is 97958412, 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
> * i12.4.96.0/24 216.191.64.10 60 0 701 1239
> 14452
> i
> * i 216.191.64.4 60 0 701 1239
> 14452
> i
> * i12.4.96.0/23 216.191.64.10 60 0 701 1239
> 14452
> i
> * i 216.191.64.4 60 0 701 1239
> 14452
> i
> * i12.4.97.0/24 216.191.64.10 60 0 701 1239
> 14452
> i
> * i 216.191.64.4 60 0 701 1239
> 14452
> i
> * i12.4.125.0/24 216.191.64.10 60 0 701 1239
> i
> * i 216.191.64.4 60 0 701 1239
> i
> * i12.5.164.0/24 216.191.64.4 60 0 701 1239
> 18618
> 11134 i
> * i12.6.206.0/24 216.191.64.10 60 0 701 1239
> 20357
> i
> *>i 216.191.64.4 60 0 701 1239
> 20357
> i
> *>i12.13.78.0/24 216.191.64.4 60 0 701 1239
> 13578
> i
> * i 216.191.64.10 60 0 701 1239
> 13578
> i
> * i12.13.116.0/22 216.191.64.10 60 0 701 1239
> 6580 i
> *>i 216.191.64.4 60 0 701 1239
> 6580 i
> * i12.20.66.0/23 216.191.64.10 60 0 701 1239
> 11589
> i
> *>i 216.191.64.4 60 0 701 1239
> 11589
> i
> * i12.20.137.0/24 216.191.64.10 60 0 701 1239
> 14452
> i
> * i 216.191.64.4 60 0 701 1239
> 14452
> i
> * i12.20.158.0/23 216.191.64.10 60 0 701 1239
> 14452
> i
> * i 216.191.64.4 60 0 701 1239
> 14452
> i
> * i12.21.144.0/24 216.191.64.10 60 0 701 1239
> 14564
> i
> *>i 216.191.64.4 60 0 701 1239
> 14564
> i
> * i12.23.69.0/24 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
>
> --removed--
>
> route-server.east>sh ip bgp regexp ^701_.*12156$
> BGP table version is 97958478, 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
> * i12.23.69.0/24 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
> * i12.23.74.0/24 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
> * i12.23.120.0/21 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
> * i63.161.204.0/22 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
> * i208.32.226.0 216.191.64.10 60 0 701 1239
> 12156
> i
> * i 216.191.64.4 60 0 701 1239
> 12156
> i
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
> Of
> Abidin Kahraman
> Sent: Wednesday, August 21, 2002 12:05 PM
> To: Brian McGahan
> Cc: ccielab@groupstudy.com
> Subject: RE: regexp fun (was RE: Filtering BGP updates using ip
> as-path
> ac cess-lists)
>
>
> Oh i see, i am sorry misunderstanding :-)
>
> Do you want to all of them in one line?
>
> Are these numbers AS# or path length? (i mean 1 2 3 and 4 5 6)
>
>
> Abidin.
> -----Original Message-----
> From: Brian McGahan [mailto:brian@cyscoexpert.com]
> Sent: Wednesday, August 21, 2002 6:52 PM
> To: 'Abidin Kahraman'
> Cc: ccielab@groupstudy.com
> Subject: RE: regexp fun (was RE: Filtering BGP updates using ip
> as-path
> access-lists)
>
> 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@cyscoexpert.com
>
> CyscoExpert Corporation
> Internetwork Consulting & Training
> http://www.cyscoexpert.com
> Voice: 847.674.3392
> Fax: 847.674.2625
>
>
> -----Original Message-----
> From: Abidin Kahraman [mailto:kahramana@superonline.net]
> Sent: Wednesday, August 21, 2002 10:37 AM
> To: Brian McGahan; Abidin Kahraman; 'elping'; 'Michael Snyder'
> Cc: steven.j.nelson@bt.com; ccielab@groupstudy.com
> 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@cyscoexpert.com]
> Sent: Wednesday, August 21, 2002 6:19 PM
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:33 GMT-3