Comment 2 for bug 999806

Another note, found a post online (don't remember where) which said adding a 'password "secret"' line to the /etc/ppp/<connectionname>.options.l2tpd file just under the name line (secret being the password to authenticate to the vpn) allowed it to work.

I've confirmed that this is the case. When the line is in the config file the connection works, without it it fails. This isn't very secure since the password is stored in plain text in this workaround, but hopefully it will help determine where the actual problem lies.

following is the scrubbed config file I'm successfully connecting with on my amd64 platform:

# /etc/ppp/<connectionName>.options.xl2tpd - Options used by PPP when a connection is made by an L2TP daemon
# $Id$

# Manual: PPPD(8)

# Created: Mon Oct 22 10:27:44 2012
# by: The L2TP IPsec VPN Manager application version 1.0.9
#
# WARNING! All changes made in this file will be lost!

#debug
#dump
#record /var/log/pppd

plugin passprompt.so
ipcp-accept-local
ipcp-accept-remote
idle 72000
ktune
noproxyarp
asyncmap 0
noauth
crtscts
lock
hide-password
modem
noipx

ipparam L2tpIPsecVpn-<connectionName>

promptprog "/usr/bin/L2tpIPsecVpn"

refuse-eap
refuse-pap
refuse-chap
refuse-mschap

remotename ""
name "<username>"
password "<secret>"

usepeerdns
nobsdcomp
nodeflate
novj