Date: Thu, 27 Sep 2012 13:23:42 +0000 (UTC) From: Marcin Cieslak <saper@saper.info> To: freebsd-net@freebsd.org Subject: Re: enc(4) uninitialized in -current? Message-ID: <slrnk68kqv.2uvc.saper@saper.info> References: <slrnk66vbe.2uvc.saper@saper.info> <CA%2Bq%2BTcptmDrtAQph_vUZtrrJCqFqC39f4XkeuvDZ1CS5pz3hOw@mail.gmail.com> <CAGH67wSTy66UThUGwwMTeQnaNx8oW7UadXOct21ftjf6H3Mpyg@mail.gmail.com> <201209270853.31318.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> John Baldwin <jhb@freebsd.org> wrote: > OTOH, have you created an enc0 device? I can't find anything that > automatically creates it. Now I'm wondering if it got initialized in FreeBSD 9.x, too. I used to have net.inet.ip.fw.default_to_accept=0 before (now it's net.inet.ip.fw.default_to_accept=1) so maybe no traffic was sent via the interfaces until everything was fully up? On the other hand the panic occurs quite late - it happened during startup of sixxs-aiccu IPv6 tunnel (which goes over IPv4+mandatory IPsec in my setup). With different configuration it panicked during startup of slpd, also very late in the userland booting process. //Marcin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrnk68kqv.2uvc.saper>