Arch Linux

baronmog

Member

Registered: 2013-11-01

Posts: 60

xl2tpd unrecognized option 'lock' after 1.3.7 upgrade

After the xl2tpd 1.3.7 upgrade, I started getting the following error

xl2tpd[3969]: /usr/sbin/pppd: In file /etc/ppp/vpn.options.xl2tpd: unrecognized option 'lock'

I downgraded back to 1.3.6, and the vpn connection works fine again.

TRAC

Member

Registered: 2008-02-23

Posts: 5

Re: xl2tpd unrecognized option 'lock' after 1.3.7 upgrade

Same problem, here. Downgrading the daemon solved it for me, too. Any workaround for the new version available?

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 12,926

Re: xl2tpd unrecognized option 'lock' after 1.3.7 upgrade

$ pacman -Fo /etc/ppp/vpn.options.xl2tpd
$ 

That file doesn't come with xl2tpd (or any other package), so it must have been generated.
try re-generating it ?

Last edited by Lone_Wolf (2016-04-30 12:16:51)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

TRAC

Member

Registered: 2008-02-23

Posts: 5

Re: xl2tpd unrecognized option 'lock' after 1.3.7 upgrade

Yeah, that is embarrassing. I did not recognize that I created the options file a few month ago. Removing "lock" statement re-enabled the vpn-connection. Seems like the new version of xl2tpd does not recognize "lock" anymore and prohibits the connection if it is present.

Cheers Lone_Wolf for the hint.

baronmog

Member

Registered: 2013-11-01

Posts: 60

Re: xl2tpd unrecognized option 'lock' after 1.3.7 upgrade

$ pacman -Fo /etc/ppp/vpn.options.xl2tpd
$ 

That file doesn't come with xl2tpd (or any other package), so it must have been generated.
try re-generating it ?

It's the vpn connection config file. Why does xl2tpd barf all over the place on a config option that previously worked? Particularly when it's just a minor number update on xl2tpd?

Looks like there's already a bug report on the xl2tpd github page, but no response yet.