Re: [lwip-users] lwIP 2.0.0 IPV6 Thread Awareness

Try to use lwIP 2.0.0 core locking feature instead, it does what you try to do with your own mutexes: http://www.nongnu.org/lwip/2_0_0/group__lwip__opts__lock.html#ga8e46232794349c209e8ed4e9e7e4f011 http://www.nongnu.org/lwip/2_0_0/pitfalls.html Ciao Dirk -- Dirk Ziegelmeier *

[lwip-users] lwIP 2.0.0 IPV6 Thread Awareness

Hello again everyone, I've got a question about thread-safety using 2.0.0 in IPV6 mode. I've tried searching for a solution on here but I'm somewhat stumped and could use some help. Prior to this I've been using the 1.4.1 core in IPV4 mode, each call to the core was surrounded with a mutex.

Re: [lwip-users] Switching to dual stack LwIP

yes, see examples in lwip-contrib apps! On Thu, Oct 6, 2016 at 2:33 PM, Aditya Prakash wrote: > > Hi, > > Two years back I made a web server based on LwIP that uses two sockets, > one for IPv4 and one for IPv6. > > However recently I have seen that there have been a

Re: [lwip-users] LWIP timeouts

Hi, Really sorry for posting the query. I found the problem in my porting layer, actually in LWIP 1.4.1 timeouts logic was not based on sys_now() API, that's why the timeouts worked there properly. Now in LWIP 2.0 timeouts logic started using sys_now() API and the problem was in his API in