James Chapman writes: > These plugins are being actively used by users of OpenL2TP and other > L2TP daemons. Please consider for inclusion in the next release of > pppd. Looks OK. I want to do a new release of pppd fairly soon, so this is timely. > Index: ppp-2.4.4/pppd/plugins/pppol2tp/l2tp_event.h > =================================================================== > --- /dev/null > +++ ppp-2.4.4/pppd/plugins/pppol2tp/l2tp_event.h > @@ -0,0 +1,104 @@ > +/***************************************************************************** > + * Copyright (C) 2008 Katalix Systems Ltd > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > + * > + *****************************************************************************/ Could you add the explicit "you can redistribute it and/or modify it..." permission statement here please? > + * Unfortunately, pppd provides no easy way to tell that the new link > + * successfully attaches to the bundle. We use its new_phase_hook to > + * watch state changes. If the new interface reaches PHASE_NETWORK, > + * then it is up. However, pppd sets variables that we need to test > + * _after_ it reaches PHASE_NETWORK, so we use a timer to check the > + * variables. This is messy. It would be much easier if pppd exported > + * a hook for multilink interface up. So, send me a patch to do that... :) Paul. -- To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
