From: Rich Collins (nilsi2002@gmail.com)
Date: Thu Apr 24 2008 - 20:02:49 ART
I would suggest a very simple setup.
R1 (AS1) --- R2------R3 (AS2)
source 200.200.1.1 on R1 into BGP
Use some some internal routing protocol to set up the BGP loopback peering
of R1 and R3.
If you traceroute from R3 to 200.200.1.1 it will go to R2 (next-hop) and
then stop. R2 (non-BGP) does not know about 200.200.1.1
-Rich
On 4/24/08, ccie23 ccie23 <ccie2323@gmail.com> wrote:
>
> Hi Rich,
> Could you further explain how tunneling work or could you point me
> to a article that does so. thank you very much!!
>
> On Tue, Apr 22, 2008 at 11:28 PM, Rich Collins <nilsi2002@gmail.com>
> wrote:
>
>> Yes I would say that it is basically a blackhole problem on R5.
>>
>> You have routes known via eBGP on the edge that have to traverse a non-BGP
>> speaker R5. If they are not known there via an internal routing protocol
>> they will be blackholed. The two choices to solve this are redistributing
>> BGP or tunneling between BGP speakers across the domain.
>>
>> -Rich
>>
>>
>> On 4/22/08, ccie23 ccie23 <ccie2323@gmail.com> wrote:
>>
>>> Hi Experts,
>>> I'm still confussed on why it is needed to redistribute BGP to
>>> IGP. Can someone please shed some light thank you.
>>>
>>>
>>>
>>> Pass the CCIE in six weeks, Guaranteed!
>>> http://www.certscience.com/CCIE
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
Pass the CCIE in six weeks, Guaranteed!
http://www.certscience.com/CCIE
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:52 ART