Re: [lwip-users] Output fails when output size exceeds 14KB while using sockets

2012-01-18 Thread dipswitch
Oke, I found the problem! The problem was that MEM_SIZE was set at 16000 bytes and the TCP_SND_BUF was set to 32KB this leads to an wrong error handling in tcp_write(). Because of this configuration tcp_write() thinks there is 32KB of buffer free, so when it's trying to fragment the packet 19KB tot

Re: [lwip-users] Output fails when output size exceeds 14KB while using sockets

2012-01-18 Thread dipswitch
Note to self, I'll fill a bug when http://savannah.nongnu.org is up again... ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] Incoming packets not seen by lwip_select on second accept

2012-01-18 Thread Joe Bloggs84
On 18/01/2012 6:29 PM, Simon Goldschmidt wrote: Ian Wilson wrote: This all works for the first connection. The problem is that incoming packets are not "detected" by lwip_select for subsequent connections to the listener (after closing the first connection of course). [..] Is this something

Re: [lwip-users] Incoming packets not seen by lwip_select on second accept

2012-01-18 Thread Simon Goldschmidt
Joe Bloggs84 wrote: > [..] I came to the > realisation that I had the first parameter of lwip_select wrong - I had > read the docs (quickly) as it being the count+1 of the number of fd That's the windows way, I think... > rather than "one more than the maximum fd value". ... and that's the p

Re: [lwip-users] Output fails when output size exceeds 14KB while using sockets

2012-01-18 Thread Kieran Mansley
On 18 Jan 2012, at 09:19, dipswi...@hackinthebox.nl wrote: > 2. Add a check of if (TCP_SND_BUF >= MEM_SIZE) to lwip_sanity_check() or > create a compile error in init.c Seems sensible for your configuration, but others might not be allocating packet buffer memory from the MEM_SIZE region, so i