OSPF anycast prefix being filtered

[Ondrej Zajicek]

On Wed, Apr 01, 2015 at 05:01:01PM +0200, Patrik Lundin wrote:
> The reason I was trying to avoid the "direct" protocol is because of this
> description in the docs (http://bird.network.cz/?get_doc&f=bird-6.html#ss6.4):
> ===
> "The question is whether it is a good idea to have such device routes
> in BIRD routing table. OS kernel usually handles device routes for
> directly connected networks by itself so we don't need (and don't want)
> to export these routes to the kernel protocol. OSPF protocol creates
> device routes for its interfaces itself and BGP protocol is usually
> used for exporting aggregate routes."
> ===
> 
> I specifically noticed that OSPF is supposed to create routes for its
> own interfaces.

Yes it is supposed to do that. Although handling of 'lo' is kind of
special case and in some circumstances does not work as expected. In that
case it is often useful to try dummy interface instead of lo interface.

> It turns out the "filtered out" messages were not relevant to my problem.
> The issue was caused by a OSPF network type mismatch. While I was
> using the BIRD default of point-to-point, the upstream router was
> configured for broadcast. After the upstream router was changed to use a
> point-to-point network type everything started to work.
> 
> It would be nice to know what the meaning of the "filtered out" lines are,
> but they do not seem to affect the route announcement.

'filtered out' lines are related to 'import none', e.g. routes were not
imported from OSPF to master routing table.

-- 
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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20150401/2286d36f/attachment.asc>