[Bug 256371] net/exabgp4

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 02 Jun 2021 08:32:22 UTC

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256371

            Bug ID: 256371
           Summary: net/exabgp4
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: zi@FreeBSD.org
          Reporter: borjam@sarenet.es
          Assignee: zi@FreeBSD.org
             Flags: maintainer-feedback?(zi@FreeBSD.org)

There is a serious bug in ExaBGP including the latest version (4.2.20, while
the port is still on 4.2.11).

Depending on network conditions and the number of configured neighbors, ExaBGP
may stay in a loop in which it will never connect to them. This bug can be
triggered after a power blackout, for example, when it can take some time for
connectivity to be restored.

The bug is fixed on Github:
https://github.com/Exa-Networks/exabgp/issues/1035

but it hasn't made it to a numbered release. It will for 4.2.21 I imagine.

Meanwhile, as the fix only requires adding two obvious code lines to a file I
think it would be wise to add the patch to the port until 4.2.21 is released.

https://github.com/borjam/exabgp/commit/6c2bf6ff8fd2fbcaa2a0abf621134ec0afa81849

-- 
You are receiving this mail because:
You are the assignee for the bug.