[Openswan Users] L2TP problem with OpenSWAN 2.6.x after changing default route

[Paul Wouters]

On Tue, 12 Jul 2011, Nels Lindquist wrote:

> interfaces, and OpenSWAN is configured to use one of them.  For
> operational reasons we sometimes switch the default route from the
> primary interface (used for IPSEC) to the secondary interface.  When
> using OpenSWAN 2.4.x, there are no issues; all tunnels continue to
> operate normally and any new connections, L2TP or otherwise, are
> initiated and function normally.
>
> I tried upgrading to 2.6.x (most recently tried 2.6.33 and 2.6.34),
> which generally works the same way *except* that any new L2TP
> connections attempted while the default route is not the interface used
> for IPSEC, the L2TP tunnel fails.  (The IPSEC transport mode connection
> is still created properly).  L2TP connections work perfectly well as
> long as the default route is the same as "left".

I dont understand who 2.4 and 2.6 with netkey are different ?

> I'm still using xl2tpd version 1.1.2 as the gateway in question is
> CentOS 4 and the kernel isn't new enough to build the xl2tpd 1.2.x series.

There is no kernel issue if you are not trying to get the CONFIG_OL2TP stuff
in the kernel (which we currently don't support anyway)

Paul