Hi Sylvain,

Thanks for PPP explanation, I withdraw my words about it. Indeed I
really appreciate and respect your great work to the world, considering
this is the path I need to embark on someday. Perhaps I am only focusing
the problem itself, but ignore the other features you worked on.

Thank you,
Jackie



On 01/24/15 04:09, Sylvain Rochet wrote:
> Hello Jackie,
>
>
> On Fri, Jan 23, 2015 at 11:43:33PM +0800, Jackie wrote:
>> Hi Sylvian,
>>
>> Yeah, you are right.
>>
>> If I am correct, actually LWIP provides a basic structure of PPP stack,
> Well, your version, perhaps, but I must disagree, you are not correct.
>
> lwIP provides a PPP stack with PPPoS(erial) PPPoE(thernet) and PPPoL2TP 
> (Layer 2 Tunneling Protocol) support, as well as supporting PAP, CHAP, 
> MSCHAPv1, MSCHAPv2, EAP, IPCP, IP6CP (IPv6), VJ Compression.
>
> This is quite far from a "basic structure", this is a bit hard to read, 
> considering the amount of time I spent on working on PPP support, but I 
> know you are just reading the source code of a very very very old lwIP 
> version :-)
>
>
>> how to send the data down to SIO also depends on the OS currently in
>> use, some special methods can be done in order to increase the
>> robustness of the system. So our supplier just did some work based on
>> LWIP's PPP stack, adding more optimization.
> Yeah, in master, the SIO input fonction is thread safe, and of course 
> the SIO output is called from the stack and usual threading care should 
> be applied.
>
>
>> So I think my issue is not from LWIP itself, but our supplier's code.
> Or from a very old lwIP version, which is almost exactly the same from 
> our point of view ;-)
>
>
> Sylvain
>
>
> _______________________________________________
> lwip-users mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/lwip-users

_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to