Hi, Simon. Thank you for the clarification about when to use the API calls or not.
I tried calling ppp_listen() from my callback, as you suggested, and that makes it work. So, yeah, I must have been blocking up the whole stack. D'oh! (And when I look back at ppp.txt, it uses ppp_connect(), as opposed to pppapi_connect(). It pays to read carefully.) -- G From: lwip-users [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, 23 May 2016 15:42 To: Mailing list for lwIP users <[email protected]> Subject: Re: [lwip-users] PPP as Server Disconnect/Reconnect Problem Under 2.0.0 Beta1 Greg Smith wrote: Additionally, and this is the important part, I want to resume listening for a new connection. So I call pppapi_listen() again at the end of my link status callback function (which happens to look a lot like Sylvain's example in ppp.txt :-) ). Coming back to the original post, you must *not* call API functions from tcpip_thread. Maybe this is your problem. I think the callback is called from tcpip_thread, so by blocking on a semaphore effectively blocks the whole stack. The API functions are meant to get you into the tcpip_thread to call things. If you already *are* in this thread, call 'ppp_listen()' instead. Simon --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
