Bug#307578: freeswan doesn't create ipsec0
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 documentation be updated? It says that it works with the standard kernels. Or, better yet, can the kernel maintainers include support for them in the 2.6 series? It will work, but without the virtual ipsec* interfaces. The native IPSec stack is just a different means of integration. with best regards, Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307578: freeswan doesn't create ipsec0
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 that the host cannot be reached. Strange - you might want to look at auth.log for any error messages. However, I can recommend to use openswan instead - freeswan is unmaintained. with best regards, Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307578: freeswan doesn't create ipsec0
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307578: freeswan doesn't create ipsec0
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 says that it works with the standard kernels. Or, better yet, can the kernel maintainers include support for them in the 2.6 series? c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307578: freeswan doesn't create ipsec0
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 gateway for the remote lan is the public IP address of the local host. Obviously I can't pass traffic to the remote lan. `ipsec look` shows this: cat: /proc/net/ipsec_spigrp: No such file or directory cat: /proc/net/ipsec_eroute: No such file or directory grep: /proc/net/ipsec_tncfg: No such file or directory sort: open failed: /proc/net/ipsec_spi: No such file or directory The description of the package says: Please note that you will need kernel support for using this package. The standard Debian kernel already includes support for IPSec. I'm running the standard kernel that installs with Sarge on the i386. I've installed ipsec-tools. Am I just missing something? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
