Carl T. Miller schrieb:
> This explains what I'm seeing now. Both sides of the tunnel
> show that the tunnel is up. A route is added for each remote
> lan using the default gateway. If I try to ping a host on
> the remote lan (it's an unrouteable address) I get an error
> from the gateway saying
Rene Mayrhofer said:
> Freeswan does not support 2.6 kernels, only openswan >= 2.3.0 properly
> supports them.
Thanks.
> It will work, but without the virtual ipsec* interfaces. The native
> IPSec stack is just a different means of integration.
This explains what I'm seeing now. Both sides of t
Carl T. Miller schrieb:
> Can you tell me what I need to do to support the ipsec* interfaces?
The ipsec* interfaces are only provided by the KLIPS IPSec stack.
Freeswan does not support 2.6 kernels, only openswan >= 2.3.0 properly
supports them.
> Also, can the package description and documentatio
Rene Mayrhofer said:
> Carl T. Miller schrieb:
> The native IPSec stack in kernel 2.6 does not have the virtual ipsec*
> interfaces, the support is different.
Can you tell me what I need to do to support the ipsec* interfaces?
Also, can the package description and documentation be updated? It
sa
Carl T. Miller schrieb:
> I'm running the standard kernel that installs with Sarge on
> the i386. I've installed ipsec-tools. Am I just missing
> something?
The native IPSec stack in kernel 2.6 does not have the virtual ipsec*
interfaces, the support is different.
with best regards,
Rene
--
T
Package: freeswan
Version: 2.04-11.3
Distro: Sarge
Kernel: kernel-image-2.6.8-1-386 2.6.8-10
When I configure and start an ipsec connection, no ipsec
interface is being created. I see that the connection is
running on both sides, and both sides get a new route for
the remote lan, however, the gat
6 matches
Mail list logo
