[quagga-users 7089] Re: bgpd can't assume route.

Paul Jakma paul at clubi.ie
Wed Jun 14 16:57:28 IST 2006


On Wed, 14 Jun 2006, Dmitriy Gorbenko wrote:

>             r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
> ...
> *> 172.16.8.59/32   192.168.5.254           20         32768 ?
> *> 192.168.1.0      0.0.0.0                  0         32768 i
> *> 192.168.3.0      192.168.5.252            2         32768 ?
> ...
>
> Networks 192.168.1.0 and 192.168.3.0 are connected directly to router.

Ah. Hmmm, maybe you wanted 'redistribute connected'? I don't know. 
What exactly were you /expecting/ to happen?

> I can't understand, why bgpd thinks that network 192.168.1.0 is 
> IGP, while I use this network to communicate between BGP routers 
> (network 192.168.3.0 is used to communicate between OSPF routers).
>
> And I want to ask, why bgpd thinks that route to network 192.168.3.0 is 
> "incomplete" ?

Ah, that's because we set IGP origin on 'network ....' originated 
routes, and incomplete origin on redistributed routes (other than 
default).

And no, makes 0 sense to me either. I gather it's cause some other 
major vendor does so, so we do. Hasso Tepper has explained/expanded 
on reasoning why in the past on this list I think.

> P.S. as I said, on the same router works ospfd and bgpd, and ospfd looks 
> fine.

I still don't quite understand what the problem is ;).

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
I think Smithers picked me because of my motivational skills.

 		-- Homer Simpson
 		   Homer the Smithers


More information about the Quagga-users mailing list