Bug 281935 - net/frr9 bgpd rpki module libssh conflict
Summary: net/frr9 bgpd rpki module libssh conflict
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Olivier Cochard
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-07 23:09 UTC by Jason Tubnor
Modified: 2024-10-15 23:04 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (olivier)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Tubnor 2024-10-07 23:09:28 UTC
The bgpd_rpki.so module is being built against a different version of security/libssh that is in ports.

This is an issue with frr9 and frr10 in either the quarterly or latest builds.

security/libssh in quarterly 4_9_6 where bgpd_rpki.so (librtr.so.0) expects 4_5_0 . Below is the relevant debugs:

# service frr restart bgpd
Checking intergrated config...
Checking vtysh.conf
OK
Starting bgpd.
frr_init: loader error: dlopen(/usr/local/lib/frr/modules/bgpd_rpki.so): /usr/local/lib/libssh.so.4: version LIBSSH_4_5_0 required by /usr/local/lib/librtr.so.0 not defined
frr_init: loader error: dlopen(/usr/local/lib/frr/modules/rpki.so): Cannot open "/usr/local/lib/frr/modules/rpki.so"
frr_init: loader error: dlopen(rpki): Shared object "rpki" not found, required by "bgpd"
/usr/local/etc/rc.d/frr: WARNING: failed to start bgpd

# ls -lsa /usr/local/lib/libssh*
469 -rw-r--r--  1 root  wheel  989304 Sep 21 13:22 /usr/local/lib/libssh.a
  1 lrwxr-xr-x  1 root  wheel      11 Sep 21 13:22 /usr/local/lib/libssh.so -> libssh.so.4
  1 lrwxr-xr-x  1 root  wheel      15 Sep 21 13:22 /usr/local/lib/libssh.so.4 -> libssh.so.4.9.6
313 -rwxr-xr-x  1 root  wheel  496752 Sep 21 13:22 /usr/local/lib/libssh.so.4.9.6
Comment 1 Jason Tubnor 2024-10-07 23:22:36 UTC
$ uname -a
FreeBSD myhostname 13.4-RELEASE-p1 FreeBSD 13.4-RELEASE-p1 GENERIC amd64
Comment 2 Olivier Cochard freebsd_committer freebsd_triage 2024-10-08 10:08:44 UTC
This is lue to security/libssh update that is using the same SOVERSION but it is not compatible with previous version.
I will bump their PORTREVISION to force a package rebuild (on all frr versions).
Thanks for the report.
Comment 3 commit-hook freebsd_committer freebsd_triage 2024-10-08 11:08:57 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=7f3171d71b13d1ac1709db8510163eababc8271d

commit 7f3171d71b13d1ac1709db8510163eababc8271d
Author:     Olivier Cochard <olivier@FreeBSD.org>
AuthorDate: 2024-10-08 10:11:55 +0000
Commit:     Olivier Cochard <olivier@FreeBSD.org>
CommitDate: 2024-10-08 11:07:51 +0000

    net/frr*: Bump PORTREVISION after libssh update

    PR:             281935
    Reported by:    Jason Tubnor <jason@tubnor.net>

 net/frr10/Makefile | 1 +
 net/frr8/Makefile  | 1 +
 net/frr9/Makefile  | 1 +
 3 files changed, 3 insertions(+)
Comment 4 commit-hook freebsd_committer freebsd_triage 2024-10-08 15:25:27 UTC
A commit in branch 2024Q4 references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=346c9ffbc65e33c76f6fb785ffc542a67d3b669c

commit 346c9ffbc65e33c76f6fb785ffc542a67d3b669c
Author:     Olivier Cochard <olivier@FreeBSD.org>
AuthorDate: 2024-10-08 10:11:55 +0000
Commit:     Olivier Cochard <olivier@FreeBSD.org>
CommitDate: 2024-10-08 15:23:58 +0000

    net/frr*: Bump PORTREVISION after libssh update

    PR:             281935
    Reported by:    Jason Tubnor <jason@tubnor.net>

    (cherry picked from commit 7f3171d71b13d1ac1709db8510163eababc8271d)

 net/frr10/Makefile | 1 +
 net/frr8/Makefile  | 1 +
 net/frr9/Makefile  | 1 +
 3 files changed, 3 insertions(+)
Comment 5 Jason Tubnor 2024-10-15 23:03:48 UTC
I can confirm on an affected host that this has now been corrected. For those with a similar issue, the following needed to be executed as root:

pkg update
pkg upgrade -f

As this is purely a route reflector for us, a force re-installation of packages was fine but for more complex setups, you'll need to assess your workflow.

This bug can now be closed. Thanks for your help!