Re: [lwip-users] lwip with libcurl and memory corruption !

2011-02-07 Thread Prashant R
Hi , So I am getting the data as expected , however I have replaced socket calls in libcurl with lwip_ calls . Yes Martin in right in the sense that libcurl is doing the the send -read - select loop . Thanks , On Mon, Feb 7, 2011 at 1:47 AM, Martin Velek wrote: > I would suppose he is usin

[lwip-users] lwip with libcurl and memory corruption !

2011-02-07 Thread Prashant R
I am currently running this on an embedded platform . I am able to successfully send and receive HTTP using lwip however I see some corruption when I repeat this operation . This consistently happens after around 4 iterations of this use case . I am looking for clues to debug this . For libcu

Re: [lwip-users] Sending UDP data beyond MTU size

2011-02-07 Thread Timmy Brolin
I do work with another popular BSD based commercial embedded TCP/IP stack. In a certain specialty industrial protocol there is a requirement to reduce the Ethernet MTU for TCP/IP traffic. But when I implemented this, the TCP/IP stack did not work very well. Turned out that the fragmentation code in

Re: [lwip-users] VPN Client for incoming PPP connection

2011-02-07 Thread Marco Jakobs
Hi Simon, thank you for your thoughts ... PPTP would be pretty enough - not the encryption is the task here, as the radio link is secure - i need a way to tunnel other subnets over the PPP connection, so that the remote devices can be addressed by their own LAN IP and that broadcast telegrams

Re: [lwip-users] lwip with libcurl and memory corruption !

2011-02-07 Thread Kieran Mansley
On Sun, 2011-02-06 at 21:56 -0800, Prashant R wrote: > Is there a good starting point to debug this ? It's almost certainly a threading problem caused by the way you're interfacing to lwIP. Which lwIP API are you using? Does your application have multiple threads accessing lwIP? Can you give a

Re: [lwip-users] lwip with libcurl and memory corruption !

2011-02-07 Thread Martin Velek
I would suppose he is using the lwip socket API via a libcurl calls. Maybe the libcurl expects the socket API is at 100% compatible with BSD sockets. If the libcurl handles non-blocking sockets with a standard way ( send - read how many sent - select loop), it may fail due to lwip does not support