Package: xl2tpd
Version: 1.3.6+dfsg-1
Severity: important
Tags: upstream
Dear Maintainer,
IPSEC configuration working
xl2tpd config working
ppp config working
now let's imagine that I am connecting with the right ipsec secret but mistyped
the CHAP password on the iphone (client), the connection is rejected (nnormal
behaviour) BUT
i am now connecting with the right secret and ppp password (CHAP)
connection is rejected as well!!!!
when restarting both IPSEC (openswan) and xl2tpd services and connect with
right secret and password then it works.
so basically the wrong ppp password somehow messes up xl2tpd, maybe you do not
close pppd channel properly ...
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armhf
Kernel: Linux 3.16.0-45-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xl2tpd depends on:
ii libc6 2.19-0ubuntu6.9
ii libpcap0.8 1.5.3-2
ii ppp 2.4.5-5.1ubuntu2.2
xl2tpd recommends no packages.
xl2tpd suggests no packages.
-- Configuration Files:
/etc/xl2tpd/l2tp-secrets changed [not included]
/etc/xl2tpd/xl2tpd.conf changed [not included]
