[quagga-users 11251] Re: bgp question

Alexis Rosen quagga-users at alexis.users.panix.com
Sat Dec 12 17:07:24 GMT 2009


I'll leave the why to other people, and stick to "how". If you want to  
do it the way you're doing it now, look into using confederations.  
Confederations allow you to not build a full mesh in your iBGP.

/a

On Dec 12, 2009, at 8:42 AM, Stephan von Krawczynski wrote:

> Forgive my ignorance, but why?
> Why should a bgp-router with a static default route and one simple  
> network
> peer with all other routers being part of his AS?
> He neither needs the routes announced nor do the others need to know  
> him, as
> there are no other routes possible besides the one through r2.
> I can imagine why using a network declaration is intended to not  
> inject the
> route to the kernel, it very likely thinks that there already is a  
> static
> route for the network.
> Nevertheless it is obvious that "redistribute connected" does not do  
> what it
> says, or?
> I would really appreciate some comment on that. Is that a bug? If it  
> is not,
> what is the intention behind auto-filtering the network for local  
> routing but
> not for announcement and vice versa? That really sounds brain-dead  
> to me.
>
> -- 
> Regards,
> Stephan
>
>
> Bret Clark <bclark at spectraaccess.com> wrote:
>
>> Well I know enough about BGP to be dangerous, but I was always  
>> under the
>> impression that in an IBGP network, all IBGP routers needed to peer  
>> with
>> all other IBGP routers, so R3 needs to have a peering session with  
>> R1.
>>
>> Stephan von Krawczynski wrote:
>>> Hi all,
>>>
>>> I ran into a problem lately that is possibly caused by too little  
>>> sleep ;-)
>>> Setup:
>>>
>>> <r1> - <some router> - <r2> - <r3> - <the world>
>>>
>>> r1,r2,r3 are all part of AS 1, all quagga, all with bgpd
>>> <some router> is a simple box with static routes (a ebgp-multihop  
>>> setup).
>>>
>>> r1 tries to announce a network 192.168.1.0/24 to r2 which should  
>>> again
>>> announce it to r3 and r3 to <the world>.
>>> The problem arises at r2.
>>> If I add a
>>> 	network 192.168.1.0/24
>>> 	redistribute connected
>>> to r2's config then it announces the net to r3, but it does not  
>>> enter the route
>>> in the kernels' routing table. So routing does not work.
>>> if I add a
>>> 	redistribute connected
>>> to r2's config then it does not announce the net to r3, but enters  
>>> the route
>>> in the kernels' routing table. Routing does work, but <the world>  
>>> does not
>>> know the net.
>>> All setup is quagga 0.99.12 btw.
>>> What did I miss here? I judged this to be a trivial setup, but ... ?
>>>
>>>
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users at lists.quagga.net
>> http://lists.quagga.net/mailman/listinfo/quagga-users
>>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users
>



More information about the Quagga-users mailing list