From: pablo.smiraglia@verizon.com
Date: Mon Sep 18 2006 - 11:47:42 ART
Assuming that natting and other basic issues were taking care of (ie let
"any" inside traffic flow to "outside" as it is the default behavior).
Your configuration should be good enough for R1 to successfully start a
BGP session with R2, but not the other way around. This may be good or
desired in many cases.
My guess: just be patient and wait a couple of minutes to be sure that R1
"tries" to start the BGP session...
HTH,
pablo.
PS: if natting is involved, you will need to deal with BGP next-hop
issues, that are unrelated to your problem at the time.
"2nd CCIE" <doubleccie@yahoo.com>
Sent by: nobody@groupstudy.com
09/18/2006 07:53 AM
Please respond to
"2nd CCIE" <doubleccie@yahoo.com>
To
ccielab@groupstudy.com, security@groupstudy.com
cc
Subject
BGP through pix
Guys
I have a confusion here
R1-----------pix>>--------R2
if i configure R1 to peer with R2 and R2 to peer with R1 using the
update-source loopback and the ebgp-multihop options ...do i still need to
allow BGP on the External ACL of the PIX ?? ...why not R1 to peer with R2
( not the other way around ) without enabling anything on the PIX .
my configuration works only when i allow the bgp to pass through the PIX
via ACL from outside to inside .
is there a way to force the peering direction ?
thx
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great
rates starting at 1"/min.
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART