BIRD 1.3.11 (ports) on FreeBSD 9.1-p7

[Alexander V. Chernikov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09.10.2013 11:36, Markus Grundmann wrote:
> Hi Alexander!
> 
> Here some additional information do you requested. On a other
> server (same OS) I running a BIRD 1.3.11 with OSPFv2, OSPFv3 and a
> BGP Peering with Full-Prefix-Table. That works fine.
> 
> --- BIRD configuration ---
> 
> #log syslog { debug, trace, info, remote, warning, error, auth,
> fatal, bug }; router id 8X.2X.32.210;
> 
> #protocol direct {                        // Commented out for
> testing purposes #        interface "vlan*"; #}
It is significant. Did you have this uncommented initially?
> 
> protocol kernel { learn; persist; scan time 20; import all; export
> all; }
> 
> protocol device { scan time 10; }
> 
> protocol ospf activezone { rfc1583compat yes;
Do you really need this?

> area 0.0.0.0 { interface "vlan3" { cost 10; type broadcast; };
> 
> interface "vlan2" { cost 10; type broadcast; passwords { password
> "totaly secret ;-)" { id 1; }; };
> 
> authentication cryptographic; };
> 
> };
> 
> export all; import all; }
> 
> 
> Am 09.10.2013 09:25, schrieb Alexander V. Chernikov:
>> Did this happen with quagga?
> 
> No! Quagga works fine but I think BIRD is more powerful
> (Filtering).
> 
>> 
>>> Virtual servers are no longer reachable. What's the problem?
>>> The same messages are generated by OSPFv3 processes.
>> Em, "arpresolve" messages are generated by kernel. Are you
>> talking about "LSA disappeared" ones?
> 
> Yes! The "arpresolv" messages are an result of starting BIRD
> daemon.
> 
>> 
>> Can you provide bird config (at least direct/ospf protocol parts)
>> and describe network topology?
> 
> See above.
> 
>> E.g. how the server can reach "8X.2X.32.211" or other addresses
>> in dmesg. What does output of "route get 8X.2X.32.211" show (when
>> working "normal" and when problem starts) ?
>> 
> route get 8X.2X.32.211 route to: <hostname> destination:
> 8X.2X.32.192
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Should it be directly reachable or?


> mask: 255.255.255.224 interface: vlan2 flags: <UP,DONE> recvpipe
> sendpipe  ssthresh  rtt,msec    mtu        weight    expire 0
> 0         0         0      1500         1         0

There are 2 FreeBSD cases which probably can play here:

1) Due to absence of Direct routes (or Direct protocol route
reannounce) bird can change direct interface route to OSPF-one (this
is probably what we see here). This is fixed (for IPv4 case) in 9.2 -
there are special RTM_PINNED flag for non-interface routes. I hope to
fix the rest (IPv6 and tunnels stuff) soon.

2) Given that you have several addresses on interface Direct route
reannounce can happen on primary (first) address change.

So, probably the best way is to update to 9.2 (or at least r248895).
If your interface addresses are stable, adding "Direct" protocol back
should mitigate the problem



> 
> Thanks + Regards, Markus
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJVC58ACgkQwcJ4iSZ1q2kDMgCeK4QqOsQMrCRLDBSCoHJ4dsf6
JH0AoJ+1qeOl1q4fJ2e872VJ21fQ3bOx
=ZlaC
-----END PGP SIGNATURE-----