Date: Wed, 26 Sep 2012 15:42:19 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@cochard.me> Cc: freebsd-net@freebsd.org, Marcin Cieslak <saper@saper.info> Subject: Re: enc(4) uninitialized in -current? Message-ID: <CAGH67wSTy66UThUGwwMTeQnaNx8oW7UadXOct21ftjf6H3Mpyg@mail.gmail.com> In-Reply-To: <CA%2Bq%2BTcptmDrtAQph_vUZtrrJCqFqC39f4XkeuvDZ1CS5pz3hOw@mail.gmail.com> References: <slrnk66vbe.2uvc.saper@saper.info> <CA%2Bq%2BTcptmDrtAQph_vUZtrrJCqFqC39f4XkeuvDZ1CS5pz3hOw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 26, 2012 at 3:33 PM, Olivier Cochard-Labbé
<olivier@cochard.me> wrote:
> On Thu, Sep 27, 2012 at 12:10 AM, Marcin Cieslak <saper@saper.info> wrote:
>> I have just updated by 9.0-something laptop to 10.0-CURRENT r240948
>> and it very quickly panics after enabling network with IPsec
>> (I am using IPsec w/racoon for IPv4 over 802.11, also using
>> tunelled IPv6).
>
> I don't know if it's related, but one of the first dmesg message
> displayd on my -current (rev 240921) is:
>
> module_register: module enc already exists!
> Module enc failed to register: 17
Not 100% sure, but DEV_ENC might need to be specified in your
$KERNCONF. IPv6 also has IPSEC built in... does this issue occur when
IPv6 is disabled/not built into your kernel?
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wSTy66UThUGwwMTeQnaNx8oW7UadXOct21ftjf6H3Mpyg>