Disable BFD on specific interfaces

[Ondrej Zajicek]

On Wed, Jan 14, 2015 at 01:15:10PM +0100, Pavlos Parissis wrote:
> On 14/01/2015 12:47 μμ, Jeronimo de A. Barros wrote:
> but my logic was wrongly applied to the conf, it should haven been:
> protocol bfd {
>     debug { states, routes, filters, interfaces, events };
>     interface "bond0" {
>         min rx interval 400 ms;
>         min tx interval 400 ms;
>         idle tx interval 1000 ms;
>         multiplier 3;
>     };
>     interface "eth*" {
>         disabled yes;
>     }
> }
> 
> but I get config error at the line ' disabled yes;'

Hi

There is no 'disabled' option, there is 'passive' option, which does something
slightly different.

But you don't really need such option, because BFD is active only on interfaces
where internal BFD clients (OSPF, BGP) requested a session. So you could
configure in OPSF/BGF whether given OSPF interface / BGP session should
use BFD (option 'bfd').


-- 
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/20150123/b3192833/attachment.asc>