On vyos-1.2-rolling-201908201244-amd64.iso won`t reproduce. All ok, configuration edits are applied.

May close this bug.

I have been trying this new feature out.

1. I had configured an MTU value and I had some sessions connected, I realised I had set it incorrect so I modified it to the correct value. On commit I received an error (sorry I don't have it at present) but to the extent that accel-pppd was not running on localhost:2004.

I had to reboot the router to get it working again.

2. I was having a number of sessions terminating on a regular basis. The underlying config file that gets generated (/etc/accel-ppp/l2tp/l2tp.confg includes a line - lcp-echo-interval=30

A single failure to receive a packet caused a lost session.

lcp-echo-interval needs to be configurable, as well as lcp-echo-failure

I'm currently testing with
lcp-echo-interval=5
lcp-echo-failure=4

and it seems to have resolved the problem for me.
Please could you add configuration options for these parameters.

3. There is no ability to kill/disconnect an individual logged in user session

4. Running the following doesn't make sense

reset vpn remote-access user
Possible completions:

l2tp.config   Terminate specified user's current remote access VPN session(s)

5. No option to restart the l2tp /vpn service via restart command (in case process stops like it did for me)

@drac, thank you for info.
reset commands migrated to vyos-1x, PR bellow
https://github.com/vyos/vyatta-ravpn/pull/13
https://github.com/vyos/vyos-1x/pull/126

Implementation advanced ppp-options

[email protected]# set vpn l2tp remote-access ppp-options 
Possible completions:
   lcp-echo-failure
                Maximum number of Echo-Requests may be sent without valid reply
   lcp-echo-interval
                LCP echo-requests/sec

https://github.com/vyos/vyos-1x/pull/127

@drac , before implementation cli command for restarting l2tp I need explanation how to reproduce issue when daemon is died. Can you detailed explain this?