Date: Sun, 19 Nov 2017 21:59:39 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: Eugene Grosbein <eugen@grosbein.net> Cc: "Muenz, Michael" <m.muenz@spam-fetish.org>, freebsd-net@freebsd.org Subject: Re: OpenVPN vs IPSec Message-ID: <20171119145939.GG82727@admin.sibptus.transneft.ru> In-Reply-To: <5A119716.5020307@grosbein.net> References: <20171118165842.GA73810@admin.sibptus.transneft.ru> <b96b449e-3dc1-6e75-e803-e6d6abefe88e@spam-fetish.org> <20171119120832.GA82727@admin.sibptus.transneft.ru> <d92dff62-3baf-a22d-bfac-5a668b276259@spam-fetish.org> <20171119143054.GC82727@admin.sibptus.transneft.ru> <5A119716.5020307@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eugene Grosbein wrote: > > > I have a personal success story of establishing transport mode IPSec > > between Windows and FreeBSD/racoon. But when other OSes are involved, > > I have the impression that there is no pure IPSec, it's usually > > IPSec+L2TP, and that's where the FreeBSD part becomes complicated > > (interaction between ipsec, mpd5 and racoon is required). > > No interaction between mpd5 and racoon is required to make IPSec+L2TP working. > In fact, mpd5 starts its part only when IKE/IPSEC part is already completed > and runs its unencrypted L2TP protocol over existing IPSec tunnel without knowning it. That's great but then you need 1) authentication in IKE/racoon and 2) authentication in mpd5? How do you handle that (and how do you configure the Windows client for it)? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171119145939.GG82727>