Indeed L2TP is just a transport protocol. L2TP just handles links between peers on each side of the tunnel. It's very true to its name, "Layer 2 transport protocol"... That's what it does, and all that it does. Much like GRE it's common practice in many scenarios to run it over IPSec to take care of privacy.
One of the big gotchas I experienced when setting L2lTP over IPSec on an ASA was authentication. Passwords had to be NTLM hashed to work with CHAP. It took a while for me to figure out why auth kept failing. I see CHAP works fine with PFSense, I only mention it as a matter of trivia. On Fri, Sep 9, 2011 at 3:38 PM, Jim Pingle <[email protected]> wrote: > On 9/9/2011 3:31 PM, Jens Kühnel wrote: > > I'm using PFSense 2.0-RC3. I'm playing around with VPN and stumbled upon > > Bug #475. > > > > Do I understand it correctly that L2TP does not encrypt at the moment? > > > > I googled around, but I couldn't find a trusted source for confirmation. > > Hope to get it here. > > I mentioned it in passing here: > > http://doc.pfsense.org/index.php/Android_VPN_Connectivity#pfSense_2.0 > > It is not encrypted. It's purely a tunneling protocol from what I could > tell. As far as I saw mpd didn't have options to encrypt L2TP on its own. > > Jim > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
