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

Wendler, Daniel dwe at boreus.de
Thu Dec 13 12:10:23 CET 2012


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.

Mit freundlichen Grüßen
---------------------------------
Daniel Wendler

Leiter Infrastruktur
Boreus Rechenzentrum GmbH
Zur Schwedenschanze 2
18435 Stralsund

tel.: +49 (0)3831/367 6409
fax.: +49 (0)3831/367 6609
email: dwe at boreus.de

www.boreus.de

Geschäftsführer: André Jahns, Holger Lebrecht
Handelsregister: Amtsgericht Stralsund HRB 5750
Sitz der Gesellschaft: Stralsund

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."




More information about the Bird-users mailing list