Just a thought: maybe use OSPF stub networking to detect the fail-overed
address?
Cheers,
Kees
On 02-06-2022 19:35, Thomas Steen Rasmussen wrote:
On 6/2/22 7:04 PM, Marek Zarychta wrote:
W dniu 2.06.2022 o 16:16, Thomas Steen Rasmussen pisze:
Hello :)
I am using BIRD on FreeBSD and it is
W dniu 2.06.2022 o 16:16, Thomas Steen Rasmussen pisze:
Hello :)
I am using BIRD on FreeBSD and it is working okay, apart from missing
CARP awareness. I am wondering if anyone knows if work has been done in
this area already?
As you may know, CARP is a patent-free VRRP alternative originally
On Tue, May 31, 2022 at 02:38:07PM +0300, Eugene Bogomazov wrote:
> Hello,
>
> RFC 9234 provides a new mechanism for route leak detection and prevention.
>
> In the attachment you can find a patch which introduces this functionality
> for BIRD 2.0.9.
Hello
Thanks for the patch, i will check it
On Thu, 02 Jun 2022, Thomas Steen Rasmussen wrote:
> As you may know, CARP is a patent-free VRRP alternative originally from
> OpenBSD.
>
Correct. And to elaborate on history:
https://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol#History
Besides from OpenBSD to FreeBSD it is also port
Hello :)
I am using BIRD on FreeBSD and it is working okay, apart from missing
CARP awareness. I am wondering if anyone knows if work has been done in
this area already?
As you may know, CARP is a patent-free VRRP alternative originally from
OpenBSD. A network interface can have one or more
Ahoj Maria!
For our production RS'es we do not use Ansible, yet we do for Restena
route collector machine which runs on a Centos custom build and what we
have done with Ansible is :
. Building the bird config
. Install bird2
. Ensure bird2 config folder exists . Remove old configs
. Configure
