OSPF "hack translation" sought
Gentlepeople - I was wondering what the "translation" of the usual hack on Quagga/JunOS/etc. for OSPF into a proper BIRD config was to allow OSPF to propagate routes to directly connected networks, which are not really part of an OSPF area. In those other systems I would make those interfaces just "passive" members, but BIRD doesn't know "passive interfaces". Making them stubs has obvious other side effects, which is why I just want the "passive" hack to work under BIRD. So what's the equivalent to do this in BIRD? Thanks, Clemens Schrimpe
On Thu, Sep 22, 2016 at 02:46:55PM +0200, Clemens Schrimpe wrote:
Gentlepeople -
I was wondering what the "translation" of the usual hack on Quagga/JunOS/etc. for OSPF into a proper BIRD config was to allow OSPF to propagate routes to directly connected networks, which are not really part of an OSPF area. In those other systems I would make those interfaces just "passive" members, but BIRD doesn't know "passive interfaces". Making them stubs has obvious other side effects, which is why I just want the "passive" hack to work under BIRD.
Hi I do not really understand what you want. AFAIK, BIRD OSPF 'stub' interfaces are more-or-less equal to 'passive' interfaces. What you mean by 'side effects' of stub ifaces? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@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."
participants (2)
-
Clemens Schrimpe -
Ondrej Zajicek