pppd to terminate on "LCP: timeout sending Config-Requests" #556
Description
Hi,
We've picked up a few oddball cases where we expect pppd to terminate. It seems the common factor is the last line stating "LCP: timeout sending Config-Requests", eg:
Apr 6 18:56:56 hostname pppd[6145]: Plugin radius.so loaded.
Apr 6 18:56:56 hostname pppd[6145]: RADIUS plugin initialized.
Apr 6 18:56:56 hostname pppd[6145]: Plugin radattr.so loaded.
Apr 6 18:56:56 hostname pppd[6145]: RADATTR plugin initialized.
Apr 6 18:56:56 hostname pppd[6145]: Plugin pppol2tp.so loaded.
Apr 6 18:56:56 hostname pppd[6145]: pppd 2.5.1 started by root, uid 0
Apr 6 18:56:56 hostname pppd[6145]: Using interface ppp1
Apr 6 18:56:56 hostname pppd[6145]: Connect: ppp1 <-->
Apr 6 18:56:56 hostname pppd[6145]: Overriding mtu 1500 to 1363
Apr 6 18:56:56 hostname pppd[6145]: Overriding mru 1500 to mtu value 1363
Apr 6 18:57:26 hostname pppd[6145]: LCP: timeout sending Config-Requests
Apr 7 23:24:15 hostname pppd[6145]: Terminating on signal 15
Apr 7 23:24:15 hostname pppd[6145]: Connection terminated.
Apr 7 23:24:15 hostname pppd[6145]: Exit.
You will note more than 24h later I killed this using "kill 6145" at which point it terminated.
I find it a bit oddball that xl2tpd also doesn't kill the pppd since I'm assuming the remote l2tp service has become non-responsive ... but the simplest "fix" is to just have pppd terminate here I reckon, please confirm my assessment, will look into code.