Disable BFD on specific interfaces

[Pavlos Parissis]

On 23/01/2015 01:49 μμ, Ondrej Zajicek wrote:
> 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').


OK great, thanks for the clarification.

Cheers,
Pavlos


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20150127/eef0f02c/attachment.asc>