From owner-freebsd-net@freebsd.org  Tue Dec  5 00:44:36 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 728EAE707F5
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue,  5 Dec 2017 00:44:36 +0000 (UTC)
 (envelope-from yaroslav@shvets.name)
Received: from gw1.artcapital.ua (mail.artcapital.ua [91.216.135.35])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 044991069;
 Tue,  5 Dec 2017 00:44:34 +0000 (UTC)
 (envelope-from yaroslav@shvets.name)
Received: from gw1.artcapital.ua (localhost [127.0.0.1])
 by gw1.artcapital.ua (8.15.2/8.15.2) with ESMTP id vB50iVCT043170;
 Tue, 5 Dec 2017 02:44:31 +0200 (EET)
 (envelope-from yaroslav@shvets.name)
Received: from localhost (yar@localhost)
 by gw1.artcapital.ua (8.15.2/8.15.2/Submit) with ESMTP id vB50iVis043167;
 Tue, 5 Dec 2017 02:44:31 +0200 (EET)
 (envelope-from yaroslav@shvets.name)
X-Authentication-Warning: gw1.artcapital.ua: yar owned process doing -bs
Date: Tue, 5 Dec 2017 02:44:31 +0200 (EET)
From: yar <yaroslav@shvets.name>
To: =?UTF-8?Q?Olivier_Cochard-Labb=C3=A9?= <olivier@freebsd.org>
cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject: Re: Bidirectional Forwarding Detection
In-Reply-To: <CA+q+Tcqx6z0L=zP-nMtSPjc9rwA5YPh6RuciDz4-aTFpjjGk1A@mail.gmail.com>
Message-ID: <alpine.BSF.2.20.1712050242320.14937@tj1.negpncvgny.hn>
References: <alpine.BSF.2.20.1712041448410.82959@tj1.negpncvgny.hn>
 <CA+q+Tcqx6z0L=zP-nMtSPjc9rwA5YPh6RuciDz4-aTFpjjGk1A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
X-Greylist: mail.artcapital.ua: 2017/12/05 02:44:31 whitelisted for localhost
 [127.0.0.1] yaroslav@shvets.name -> (ACL 306)
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 00:44:36 -0000

Hello Olivier.

Thanks for the detailed answer.

I meant something like this:
https://www.bsdcan.org/2016/schedule/events/667.en.html
https://www.bsdcan.org/2016/schedule/attachments/358_bsdcan2016-bfd.pdf

On Mon, 4 Dec 2017, 15:41, you wrote:

> On Mon, Dec 4, 2017 at 1:53 PM, yar <yaroslav@shvets.name> wrote:
>
>> Hello All.
>>
>> Does FreeBSD support BFD (Bidirectional Forwarding Detection)?
>> rfc5880, rfc5881
>
>
> ​Hi,
>
> BFD is supported (ie: not filtered) by FreeBSD: you just need to use a BFD
> daemon software.
>
> If your question was "Does FreeBSD includes a BFD daemon into base?", the
> answer is no.
>
> Main usage of BFD is to detect network failure between routing peers and
> give this information to the routing protocol​.
> As example, once an OSPF process detect new neighbours, it will sent their
> IP addresses to the BFD process:
> Once received, the BFD process will monitor the reachability of these
> neighbours and will communicate back to the OSPF process if they are not
> reachable.
>
> But I'm not aware of a standard way for an "independent" bfd daemon to
> communicate between all the routing softwares (bird, FRR, quagga, etc.):
> This is why they includes their own BFD daemon (like bird).
>
> Regards,
>
> Olivier
>

-- 
yar