[Bug 225403] net/openbgpd breaks on 10.3 due to no tcpmd5 module
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jan 23 13:15:46 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225403
Bug ID: 225403
Summary: net/openbgpd breaks on 10.3 due to no tcpmd5 module
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: hrs at FreeBSD.org
Reporter: oliver at watershed.co.uk
Flags: maintainer-feedback?(hrs at FreeBSD.org)
Assignee: hrs at FreeBSD.org
On 10.3-RELEASE-p26 (still a "production" version), bgpd fails to start when
updated to 5.2.20121209_3. No error is logged to the terminal, but
/var/log/messages shows:
bgpd[57713]: fatal in SE: pfkey setup failed: Address family not supported by
protocol family
bgpd[57712]: fatal in RDE: rde_dispatch_imsg_session: pipe closed
bgpd[57711]: dispatch_imsg in main: pipe closed
bgpd[57711]: dispatch_imsg in main: pipe closed
bgpd[57711]: Lost child: session engine exited
This happens even with a bare bgpd.conf file that just has an "AS xxxxx" line
in it.
We believe the issue is that 10.3 is not built with the TCP_SIGNATURE build
option by default and has no 11.1 equivalent of IPSEC_SUPPORT option nor
tcpmd5.ko kernel module available.
If that's the case, could the port be patched to check for a required module's
availability? It could issue a warning that a custom kernel should be built or,
preferably, still just work but without the new functionality.
It may be worth urgently putting something into a package installation message
while the problem is resolved, since it caught us totally off-guard and there
is no quick workaround to fix once it's installed.
Thank you for maintaining the port.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list