Your message dated Mon, 02 Sep 2013 21:16:43 +
with message-id
and subject line Bug#721540: Removed package(s) from unstable
has caused the Debian Bug report #644353,
regarding Kernel 8.2-1 is not enable with IPSEC
to be marked as done.
This means that you claim that the problem has been
2011/10/5 Petr Salinger :
>> option IPSEC
>> option IPSEC_NAT_T
>> device crypto
>> device enc
>
> Have to be the devices built-in or can they be built as a modules ?
> I would prefer to use modules, iff posible.
AFAIK everything that can be built as module already is.
Mats, if you want t
onsdag den 5 oktober 2011 klockan 08:04 skrev Petr Salinger detta:
>
> In this particular case, which option and devices have to be added.
> The [1] enlist:
>
>>option IPSEC
>>option IPSEC_NAT_T
>>device crypto
>>device enc
All of these are needed for the desired IPSec functionali
Package: kfreebsd-8
I was under the impression that my pushinf for IPSEC support
would have lead to that feature being enable in image 8.2,
at least. Until a few minutes ago I have had a custom
kernel 8.1 in use in order to evaluate ipsec-tools
continuously. Now I have installed
kfreebsd-image
2011/10/4 Mats Erik Andersson :
> and I must to my great disappointment observe that
> IPSec and pfkey is not activated in our prebuilt
> package. How come? I was under the impression that
> we all do agree on this matter.
What's the bug # for this?
--
Robert Millan
--
To UNSUBSCRIBE, email t
Dear all,
I was under the impression that my pushinf for IPSEC support
would have lead to that feature being enable in image 8.2,
at least. Until a few minutes ago I have had a custom
kernel 8.1 in use in order to evaluate ipsec-tools
continuously. Now I have installed
kfreebsd-image-8.2-1-amd6
6 matches
Mail list logo
