Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
> Missing some net-pf-15 (=> af_key) and probably others...
> What are the right aliases for esp4 and ah4?
xfrm-type-xx-yy
xx is the family and yy is the protocol.
So for esp4 that would be
xfrm-type-2-50
--
Debian GNU/Linux 3.0 is out! ( htt
Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
> Missing some net-pf-15 (=> af_key) and probably others...
> What are the right aliases for esp4 and ah4?
xfrm-type-xx-yy
xx is the family and yy is the protocol.
So for esp4 that would be
xfrm-type-2-50
--
Debian GNU/Linux 3.0 is out! ( htt
Hi Herbert,
Herbert Xu écrivait :
> Actually make that esp4.o.
That's ok for SAD with esp4. Now I get the same problem as Martin for SPD,
so I will try rebuilding ipsec-tools with my actual kernel headers.
I'm using the "standard" Sid kernel: kernel-image-2.4.22-1-686.
> Yes they should
Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
>> Make sure that esp.o is loaded.
>
> It was not loaded. I did load it, tryied again, but result was the same.
> BTW, shouldn't theses modules be loaded automagically by modprobe?!
Actually make that esp4.o.
Yes they should be loaded automatica
Hi Herbert,
Herbert Xu écrivait :
> Actually make that esp4.o.
That's ok for SAD with esp4. Now I get the same problem as Martin for SPD,
so I will try rebuilding ipsec-tools with my actual kernel headers.
I'm using the "standard" Sid kernel: kernel-image-2.4.22-1-686.
> Yes they should
Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
>> Make sure that esp.o is loaded.
>
> It was not loaded. I did load it, tryied again, but result was the same.
> BTW, shouldn't theses modules be loaded automagically by modprobe?!
Actually make that esp4.o.
Yes they should be loaded automatica
On Thursday, 02 October 2003, at 17:37:17 +1000,
Mark Devin wrote:
> --
> And here is the errors setkey produces:
> --
> # setkey -f /etc/ipsec.conf
> The result of line 6: Invalid argument.
> The result of line 9: Invalid argument.
> ---
On Thursday, 02 October 2003, at 17:37:17 +1000,
Mark Devin wrote:
> --
> And here is the errors setkey produces:
> --
> # setkey -f /etc/ipsec.conf
> The result of line 6: Invalid argument.
> The result of line 9: Invalid argument.
> ---
Herbert Xu écrivait :
> Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
> > Here is my problem:
> > # echo "add 10.0.0.254 10.0.0.100 esp 200102 -E des-cbc 0x
> > ;" | setkey -c
> > The result of line 1: No buffer space available.
> Make sure that esp.o is loaded.
It was not lo
Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
> Here is my problem:
> # echo "add 10.0.0.254 10.0.0.100 esp 200102 -E des-cbc 0x
> ;" | setkey -c
> The result of line 1: No buffer space available.
Make sure that esp.o is loaded.
--
Debian GNU/Linux 3.0 is out! ( http://ww
Herbert Xu écrivait :
> Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
> > Here is my problem:
> > # echo "add 10.0.0.254 10.0.0.100 esp 200102 -E des-cbc 0x ;" |
> > setkey -c
> > The result of line 1: No buffer space available.
> Make sure that esp.o is loaded.
It was not lo
Jean Christophe ANDR? <[EMAIL PROTECTED]> wrote:
>
> Here is my problem:
> # echo "add 10.0.0.254 10.0.0.100 esp 200102 -E des-cbc 0x ;" |
> setkey -c
> The result of line 1: No buffer space available.
Make sure that esp.o is loaded.
--
Debian GNU/Linux 3.0 is out! ( http://ww
Hi Mark and others,
Mark Devin écrivait :
> Just replying to myself again for the benefit of any list readers having
> similar problems.
And I did follow it with interest... ;-)
> Also make sure that ipsec-tools package is compiled against the 2.4.22
> kernel headers. This can be done
Mark Devin wrote:
Mark Devin wrote:
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which
debian has backported into the 2
Hi Mark and others,
Mark Devin écrivait :
> Just replying to myself again for the benefit of any list readers having
> similar problems.
And I did follow it with interest... ;-)
> Also make sure that ipsec-tools package is compiled against the 2.4.22
> kernel headers. This can be done
Mark Devin wrote:
Mark Devin wrote:
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which
debian has backported into the 2.4.
Mark Devin wrote:
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which
debian has backported into the 2.4.21 kernel sources
Mark Devin wrote:
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which
debian has backported into the 2.4.21 kernel sources.
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which debian
has backported into the 2.4.21 kernel sources.
I just recompile
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which debian
has backported into the 2.4.21 kernel sources.
I just recompiled my kernel today w
Mark Devin wrote:
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which debian
has backported into the 2.4.21 kernel sources.
I just recompiled
I have been running a custom compiled 2.4.21 kernel using the kernel
source package from Adrian Bunk's site on Woody. I had an ipsec link
setup and it was working well using the Kame implementation which debian
has backported into the 2.4.21 kernel sources.
I just recompiled my kernel today wi
22 matches
Mail list logo
