[Openswan Users] Openswan and OpenL2TP

[Paul Wouters]

On Tue, 25 Dec 2007, coffee wrote:

You should not need to setup any manual security policies if you are using
L2TP. Just the "new connection" wizard, together with properly importing the
PKCS#12 files is all that is needed on the windows side.

Paul

> Step 1:
> In linux:
> 1. config Openswan(host to host mode)
> In MS Windows:
> 2. write a Security Policy in "IP Security Policies on Local Computer" snap-in.
> Then, ping Windows from Linux, but it's not able to get reply. Otherwise, from Windows, it'll get reply after one or two secs. Here Linux can ping Windows also. I don't know what's wrong?
> Now, we've get IPsec SA.
>
> Step 2:
> In MS Windows:
> 1. configure "Route and remote access". Here the VPN Server is up.
> In linux:
> 1. turn on the OpenL2TP without ipsec.so plugin.
> 2. restore config file that can create a tunnel and a session with peer addr.
> Now, in linux, we could get ppp0 interface. The server can detect it as a client. From this result we consider OpenL2TP is working well.
> So these two tools are separate working.
>
> If we use Windows client, we'll need setup a connection and input name/passwd/PSK .etc. Then dialup. The L2TP/IPSec connection will establish. So I'm not sure in linux, we do
> IPSec(we need manually creat SP in server at first, but to win client don't) and L2TP completely separate is a right method?
>
> Thanks&Regards
>
> --
> coffee
>
>
> _______________________________________________
> 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
>

-- 
Building and integrating Virtual Private Networks with Openswan:
http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155