can't export prefix /19 to ospf but /22 is ok

[Wendler, Daniel]

Hi,

another thing on this.
I checkout the git repo and compiled bird myself.
In this version the static routes are exported per OSPF.
So i look for something different between
bird_1.3.8-1~bpo60+1_amd64.deb and the GIT Version.
I found commit e4404cef0be10e639566986a2f8c1906c9f37de1.
The was an change in proto/ospf/config.Y with comment Backbone is non-stub.
Because of this I changed my 1.8.1 config and add following line:

        area 0.0.0.0 { stub no; };

(I don't have an explicit Backbone Area config before, because we don't need one)
Now it works, static routes are accepted by OSPF and distributed.

Maybe it helps also with your problem?!

Daniel

Am 13.12.2012 um 12:10 schrieb "Wendler, Daniel" <dwe at boreus.de>:

> Hi,
> 
> maybe this is an different Problem.
> I realized, that the /19 is from the static protocol while /22 is from direct.
> I have an similar issue where i can not export routes from the static
> protocoll to ospf. 
> I enable ospf debug and there i see "ospf < rejected by protocol".
> I can do what i want (and setup what i want) but routes are rejected.
> 
> Maybe thats the problem here.
> 
> Daniel 
> 
> Am 10.12.2012 um 22:11 schrieb Ondrej Zajicek <santiago at crfreenet.org>:
> 
>> On Tue, Dec 04, 2012 at 10:18:33AM +0100, Piotr wrote:
>>> Hi,
>>> 
>>> 
>>> In bird i have in routing table:
>>> 
>>> 10.10.96.0/22     dev vlan13 [direct1 Nov19] * (240)
>>> 10.10.96.0/19     dev vlan14 [static1 09:12] * (200)
>>> 
>>> and i try to export  prefix 10.10.96.0/19 to ospf
>>> and on others ospf routers i see only:
>>> Extern   10.10.96.0       mask 255.255.252.0
>>> 
>>> There is some limit in bird or ospf or bird takes just more precise  
>>> route ? I'm not sure, but for a while, when i started testing this, i  
>>> saw /19 but it was a night and i was very tired..
>> 
>> Hello
>> 
>> Don't you have enabled option rfc1583compat ? That would cause such behavior.
>> 
>> Do you have messages 'LSAID collision for ...' in bird log?
>> 
>> If the rfc1583compat option is not the cause, you could post 'show ospf state'
>> and 'show ospf lsadb' to see whether there are LSAs for both external routes.
>> 
>> -- 
>> Elen sila lumenn' omentielvo
>> 
>> Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
>> OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
>> "To err is human -- to blame it on a computer is even more so."
>