ml-ppp bundle dies if initial link fails (even in 2.4.7)
Hi all
We can't seem to get ml-ppp to work in a stable way (nor PPPoE, nor PPPoL2TP). Even when I found out the master_detach option, we compiled 2.4.7 but that didn't to the trick.
All links may fail, except for the one who created the bundle, if that happens, the link goes down, if-down scripts are called, and all other links are nicely closed.
Does anybody have a solution for that?
P.S. tried killing pppd with the HUP signal (as mentioned in the man), tried interrupting the link somewhere in the middle, so the LCP fails, nothing has helped me so far
kind regards
Arne
Hello!
Arne Van Theemsche schrieb am Thu, 02 Oct 2014 09:29:31 +0200:
Quoted 5 lines
Hi all
We can't seem to get ml-ppp to work in a stable way (nor PPPoE, nor PPPoL2TP). Even when I found out the
master_detachoption, we compiled 2.4.7 but that didn't to the trick.All links may fail, except for the one who created the bundle, if that happens, the link goes down, if-down scripts are called, and all other links are nicely closed.
This works here without any problems (using SIGHUP). We use the latest Linux kernels from the 3.14 and 3.16 branches (3.14.19 and 3.16.3 at the moment) and pppd 2.4.6. However, pppd is heavily patched as we implemented Dial-on-Demand over ML bundles, which is not possible with the stock pppd. I'm afraid I haven't found the time yet to send the patches upstream :-/ But you can look into them by yourself:
Quoted 4 lines
Does anybody have a solution for that?
P.S. tried killing pppd with the HUP signal (as mentioned in the man), tried interrupting the link somewhere in the middle, so the LCP fails, nothing has helped me so far
What happens if you send a SIGHUP to the master pppd? Is there nothing in the logs?
Regards,
Christoph Schulz