Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Sep 2000 19:11:05 -0700 (PDT)
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Sam Wun <swun@eSec.com.au>
Cc:        "'freebsd-security@freebsd.org'" <freebsd-security@FreeBSD.ORG>
Subject:   Re: IPsec block my ssh remote login.
Message-ID:  <Pine.BSF.4.21.0009251910330.89779-100000@freefall.freebsd.org>
In-Reply-To: <39D0060C.230D7658@eSec.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Sep 2000, Sam Wun wrote:

> This makes much more sense now. Thanks
> Another question is, do I need to setup ipsec in rc.conf file like ipfilter just
> for convinently setting the IPSEC up when the machine in the booting stage? If
> so, I will need to modify the rc.network to reflect the change?

rc.conf includes the option:

ipsec_file="/etc/ipsec.conf"    # Name of config file for setkey

which does the obvious thing. You may also like to enable other rc.conf
options.

Kris

--
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009251910330.89779-100000>