[Openswan Users] No ipsec0 interfaces in routeing table

ted leslie tleslie at tcn.net
Wed Jul 5 13:15:05 CEST 2006


unless you put the Klips patch in, the 2.6 kernel version of freeswan/openswan
don't have ipsecX interfaces

thats not to say that this is your problem, if yuor doing a DNAT and SNAT translation
in your setup , then it could be.

-tl



On Tue, 04 Jul 2006 11:06:51 -0400
Jack Lowry <jrlowry376 at adelphia.net> wrote:

> I've been using freeswan 1.99 for years and I've decided
> to upgrade to openswan 2.4.6 on kernel 2.6.17.
> 
> I fairly certain I'm getting connected to my peer
> (a checkpoint 4.1 firewall) as ipsec auto --status gives
> me a message "500 STATE_MAIN_I4 (ISAKMP SA established)"
> among other things (but nothing that sicks out a problem.
> 
> I can't connect to a host on the remote end.
> 
> On thing that I find odd is the routing table does not include
> routes for the network behind the peer that I am trying to connect
> to using ipsec0 as the interface.
> 
> 
> _______________________________________________
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
> Building and Integrating Virtual Private Networks with Openswan: 
> http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
> 


More information about the Users mailing list