Chap authentication fails?

Bug #999476 reported by Colin Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
l2tp-ipsec-vpn (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Release: Ubuntu 12.04
Package version: l2tp-ipsec-vpn 1.0.6-1 and l2tp-ipsec-vpn-daemon 0.9.8-1

Expected:
I expected to connect to my VPN with the same configuration settings entered into the GUI as I did with the same version Ubuntu 10.10

What Happened:
With the same configurations used on 10.10 my VPN with Ubuntu 12.04 fails to connect.

In comparing the logs between 10.10 and 12.04, I noticed that the logs statements were similar up to the point where it says "CHAP authentication succeeded"

I was able to connect if I updated my /etc/ppp/chap-secrets file manually to:
username * password *

The VPN client should be able to use the password entered into the GUI

Attached is 2 logs, one failed connection in 12.04 and one successful connection in 10.10. Some information is redacted/fabricated in the logs like IP addresses, etc.

Revision history for this message
Colin Harrington (colin-harrington) wrote :
Revision history for this message
Colin Harrington (colin-harrington) wrote :
Revision history for this message
Werner Jaeger (werner-jaeger) wrote :

I tested your scenario with Ubuntu version 12.04 and could not reproduce the described behavior.

I successfully connected with PPP chap authentication to the publicly available VPN www.britishtvanywhere.com.

Here is the corresponding log:
May 22 08:06:47.885 Starting xl2tpd: xl2tpd.
May 22 08:06:48.932 xl2tpd[6481]: Connecting to host vpn9.usaip.eu, port 1701
May 22 08:06:48.977 xl2tpd[6481]: Connection established to 78.129.227.67, 1701. Local: 1894, Remote: 36315 (ref=0/0).
May 22 08:06:48.978 xl2tpd[6481]: Calling on tunnel 1894
May 22 08:06:49.020 xl2tpd[6481]: Call established with 78.129.227.67, Local: 2528, Remote: 1, Serial: 1 (ref=0/0)
May 22 08:06:49.022 xl2tpd[6481]: start_pppd: I'm running:
May 22 08:06:49.022 xl2tpd[6481]: "/usr/sbin/pppd"
May 22 08:06:49.022 xl2tpd[6481]: "passive"
May 22 08:06:49.023 xl2tpd[6481]: "nodetach"
May 22 08:06:49.023 xl2tpd[6481]: ":"
May 22 08:06:49.023 xl2tpd[6481]: "file"
May 22 08:06:49.023 xl2tpd[6481]: "/etc/ppp/www.britishtvanywhere.com.options.xl2tpd"
May 22 08:06:49.024 xl2tpd[6481]: "ipparam"
May 22 08:06:49.024 xl2tpd[6481]: "78.129.227.67"
May 22 08:06:49.024 xl2tpd[6481]: "/dev/pts/2"
May 22 08:06:49.025 pppd[6482]: Plugin passprompt.so loaded.
May 22 08:06:49.025 pppd[6482]: pppd 2.4.5 started by root, uid 0
May 22 08:06:49.029 pppd[6482]: Using interface ppp0
May 22 08:06:49.029 pppd[6482]: Connect: ppp0 <--> /dev/pts/2
May 22 08:06:49.800 pppd[6482]: CHAP authentication succeeded
May 22 08:06:50.891 pppd[6482]: local IP address 172.31.156.45
May 22 08:06:50.892 pppd[6482]: remote IP address 172.31.156.0

I did not have a /etc/ppp/chap-secrets file, the password was delivered, as expected, by the VPN client via passprompt.so

To further investigate the issue could you please manually enable PPP debugging by uncommenting the debug line in file /etc/ppp/MyVPN.options.xl2tpd and attach the then resulting log ?

Changed in l2tp-ipsec-vpn (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.