Date: Tue, 22 Mar 2022 14:37:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262718] [patch] ipsec.conf failing at boot time Message-ID: <bug-262718-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262718 Bug ID: 262718 Summary: [patch] ipsec.conf failing at boot time Product: Base System Version: 13.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: dinoex@FreeBSD.org Created attachment 232630 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232630&action=edit Suggested patch Setup: I run BGP with md5 passwords, using setkey and ipsec.conf. With FreeBSD-13 this configuration fail to work. from logfile: kernel: Feeding entropy: . kernel: Installing ipsec manual keys/policies. kernel: The result of line 1: Invalid argument. kernel: The result of line 2: Invalid argument. kernel: The result of line 3: Invalid argument. kernel: The result of line 4: Invalid argument. kernel: Loading kernel modules: /etc/ipsec.conf: add 185.XXX.XXX.15 185.XXX.XXX.130 tcp 0x1000 -A tcp-md5 "password"; add 185.XXX.XXX.130 185.XXX.XXX.15 tcp 0x1000 -A tcp-md5 "password"; add 185.XXX.XXX.15 185.XXX.XXX.129 tcp 0x1000 -A tcp-md5 "password"; add 185.XXX.XXX.129 185.XXX.XXX.15 tcp 0x1000 -A tcp-md5 "password"; /etc/rc.conf: ipsec_file="/etc/ipsec.conf" ipsec_enable="YES" kld_list="netgraph tcpmd5 ng_ether ng_pppoe ng_socket ng_mppc ng_ppp ng_tee ng_tcpmss" # service -l | egrep 'ipsec|kld' ipsec kld kldxref Workaround after reboot I run: # /etc/rc.d/ipsec start Suggested fix: Change the Starting order. Patching /etc/rc.d/ipsec solves the problem: # rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | egrep 'ipsec|kld' /etc/rc.d/kldxref /etc/rc.d/kld /etc/rc.d/ipsec start ipsec after -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262718-227>