[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quagga-users
Subject:    [quagga-users 3021] Re: BGP- redistribute EBGP routes through iBGP
From:       "john smith" <johnsmith0302 () hotmail ! com>
Date:       2004-10-28 9:33:44
Message-ID: BAY17-F37jO8Cwvwrxa00040083 () hotmail ! com
[Download RAW message or body]

or simply put a L2 switch in front of core and connect all 3 on it....(if 
your core router is piddly and cannot handle too many routes...)


>From: Jeff S Wheeler <jsw@jsw.louisville.ky.us>
>To: quagga-users@lists.quagga.net
>Subject: [quagga-users 3018] Re: BGP- redistribute EBGP routes through 
>iBGP	toanother eBGP	connection
>Date: Thu, 28 Oct 2004 03:13:44 -0400
>
>On Wed, 2004-10-27 at 20:51, Brian wrote:
> > Border 1 and Border 2 are NOT meshed
>
>It doesn't matter that border1 and border2 do not have a circuit or
>multi-access network interconnecting them.  They still need an iBGP
>session.  The only way to avoid that is to confederate or make border1
>and border2 route-reflector-clients of core.  There is no reason to do
>that in your topology.
>
>Just configure an iBGP session between border1 and border2, make sure
>the loopback addresses and any advertised next-hop values are reachable
>via IGP on both routers, and watch your problem go away.  :-)
>
>--
>Jeff S Wheeler <jsw@jsw.louisville.ky.us>
>
>
>
>_______________________________________________
>Quagga-users mailing list
>Quagga-users@lists.quagga.net
>http://lists.quagga.net/mailman/listinfo/quagga-users

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-users
[prev in list] [next in list] [prev in thread] [next in thread]