for the life of me I cannot determine why the prefix noted above is not
matching the prefix 192.1.1.0/24.
The topology is r3 and r5 as eBGP peers.  R5 originating 128, 191, and 192
routes.  R5 with the prefix permit 128.0.0.0/2 ge17 attached to the R3
neighbor statement.  That prefix statement is not permitting the 192 route.
R3 before the prefix-list
   Network          Next Hop            Metric LocPrf Weight Path
*> 128.1.1.0/24     10.1.35.5                0             0 35 i
*> 191.1.1.0/24     10.1.35.5                0             0 35 i
*> 192.1.1.0        10.1.35.5                0             0 35 i
R3 after the prefix-list
   Network          Next Hop            Metric LocPrf Weight Path
*> 128.1.1.0/24     10.1.35.5                0             0 35 i
*> 191.1.1.0/24     10.1.35.5                0             0 35 i
R5 Loopbacks
Loopback128                128.1.1.5/24
Loopback191                191.1.1.5 /24
Loopback192                192.1.1.5/24
-- r/ LG Blogs and organic groups at http://www.ccie.netReceived on Sun Apr 25 2010 - 08:49:49 ART
This archive was generated by hypermail 2.2.0 : Sat May 01 2010 - 09:49:57 ART