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] 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-17 Thread Simon Goldschmidt
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 obvious? If not I will provide some code

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

2012-01-17 Thread Ian Wilson
Hello all, I can provide more details than this (incl. lwip debgs and wireshark logs) but I wanted to find out first if there is something obvious before imposing on people to parse my detailed data. I have tried to search for relevant Q&A's but with no success. I have a lwip based system r