Hi all! Find attached ppp-2.4.2-r3.ebuild and a patch (ppp-2.4.2.persist_cbcp.patch) that permits to a single pppd to request a callback and stay persistent to answer the new call. I create this patch in order to have a single pppd for the initiation and the answer of a callback. When I was start kppp to initiate a callback, it wasn't able to have the kppp process informed with the callback answer, because a new pppd was started. With this patch, the first pppd (that is one that initiates the callback) answers the callback, if the 'persist' flag is set, and the kppp shows all information of the answered callback (speed, rate, etc). I use a new USE FLAG (persist_cbcp) in order to apply (or not) this patch. Regard, Andrew
Created attachment 40537 [details] ppp-2.4.2-r3.ebuild (Enhancement)
Created attachment 40539 [details] /usr/portage/net-dialup/ppp/files/2.4.2/ppp-2.4.2.persist_cbcp.patch (Enhancement)
I've decided to stop adding enhancements on versions < 2.4.3, mainly because I don't wanna reopen the can of worms - finally, ppp-2.4.2 does not have As you probably know, there are issues with persist feature in 2.4.3 (see bug #74093), therefore I postpone this till that issue is solved. if persist problem gets solved and kppp still doesn't handle call back conections as it should, reopen it.
