From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problem with l2tp-isec
Date: Thu, 19 Dec 2013 10:28:41 -0500 [thread overview]
Message-ID: <13686.1387466921@ccs.covici.com> (raw)
In-Reply-To: <201312191504.50766.michaelkintzios@gmail.com>
Thanks -- I followed the wrong wiki, I will see if there is much
difference and check the debugging.
Thanks.
Mick <michaelkintzios@gmail.com> wrote:
> On Thursday 19 Dec 2013 14:27:28 covici@ccs.covici.com wrote:
> > Hi. I am trying to configure l2tp-isec to a server and although it
> > works in Winblows, whenever I put c followed by the name, it times out.
> > I am not seeing any particular bad messages, except that netlink says 20
> > bytes left over after parsing attributes, but there seems to be no
> > solution to that. I am using openswan plus xl2tp.
> >
> >
> > How can I troubleshoot this, or should I post my configs here?
> >
> > Thanks in advance for any suggestions.
>
>
> Have you followed suggestions relevant to openswan and xl2tpd here?
>
> http://wiki.gentoo.org/wiki/IPsec_L2TP_VPN_server
>
> Increase the verbosity of the openswan debugging to see if ipsec is
> established, or why it fails.
>
> If the ipsec association is established, then check the x2ltp configuration
> and set 'debug tunnel = yes' to get more information from it, or start it as
> 'xl2tpd -D' to get some useful information until you get it going.
>
>
> However, if you are using Windows >=7 then it may be better to install and run
> StrongSwan with IKEv2 on Linux, which MSWindows can now support natively and
> do away with L2TP all together. Openswan also supports IKEv2.
>
> --
> Regards,
> Mick
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
prev parent reply other threads:[~2013-12-19 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 14:27 [gentoo-user] problem with l2tp-isec covici
2013-12-19 15:04 ` Mick
2013-12-19 15:28 ` covici [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13686.1387466921@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox