Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Aug 2004 10:21:55 -0600
From:      Nathan Kinkade <nkinkade@ub.edu.bz>
To:        Cristi Tauber <cristi.tauber@sbhost.ro>
Cc:        FreeBSD Question <freebsd-questions@freebsd.org>
Subject:   Re: kernel compile
Message-ID:  <20040825162155.GU3767@gentoo-npk.bmp.ub>
In-Reply-To: <412C2DA7.B08686EF@sbhost.ro>
References:  <412C2DA7.B08686EF@sbhost.ro>

next in thread | previous in thread | raw e-mail | index | archive | help

--5tINJiUS2/Dn5Rhr
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 25, 2004 at 09:11:51AM +0300, Cristi Tauber wrote:
>          hi all,
>     I compile a 5.2.1 release's kernel with IPFIREWALL and IPSEC (?
> IPSEC_ESP). I compiled the kernel w/o errors i rebooted and everything
> works great. I mention that I do not installed any IPSEC software at
> that time. I downloaded qmail ? ucspi and try to install. After ucspi I
> had to reboot the server in order to start svscan. Now is my problem ...
> the server is not booting with the error :
>=20
>  /etc/rc: WARNING : /etc/ipsec.conf not readable; ipsec start aborted
>=20
>   (OK ... i dont want ipsec right now)
>=20
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
> /bin/sh on /etc/rc terminated abnormally, going to single mode
>=20
>            A tried to recompile the kernel without IPSEC and even
> without IPFIREWALL ... i get the same error . What's wrong ???
>=20
>                      thanks in advance
>=20
>             Cristi

I really don't know anything about using IPSEC under FreeBSD, but since
nobody seems to have replied just yet, I'll offer up a few suggestions
that occur to me immediately ( in order of importance ):

1) in /etc/rc.conf set ipsec_enable=3D"NO" - take a look at
/etc/rc.d/ipsec, you'll see that it may be this script that is causing
your boot to fail under the ipsec_prestart() function. so setting this
option in rc.conf may well give you the desired result.

2) try creating an empty /etc/ipsec.conf to appease ipsec

3) check into any sysctl variables that might affect ipsec in the kernel
- set them in either /etc/sysctl.conf, or perhaps /boot/loader.conf.

Nathan
--=20
PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xD8527E49

--5tINJiUS2/Dn5Rhr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBLLyjO0ZIEthSfkkRAi9rAKCkcMAt1X9a7USdaSAT1B7zeY6v7wCdEtyW
M/QxYtMWGYdB9snjSXydRjw=
=/4FO
-----END PGP SIGNATURE-----

--5tINJiUS2/Dn5Rhr--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040825162155.GU3767>