ve no
> problems turning off the RAW API, comment the use of my TCP server and
> I will be very surprised if that will make any difference. I will test
> that tomorrow :-)
>
>
> Thanks,
>
> Noam.
>
>
> From: lwip-users <
Hi Noam,
On Wed, May 31, 2017, at 11:11 AM, Noam Weissman wrote:
> I am using a base project that is used for testing. This base project
> uses FreeRTOS 8.01 + LwIP 1.41
> + a few modules that work just fine. The base project has a DHCP client
> and a TCP server (Raw API)
> that work just fine.
Hi Noam,
On Wed, May 31, 2017, at 11:11 AM, Noam Weissman wrote:
> I am using a base project that is used for testing. This base project
> uses FreeRTOS 8.01 + LwIP 1.41
> + a few modules that work just fine. The base project has a DHCP client
> and a TCP server (Raw API)
> that work just fine.
Hi Simon,
On Thu, Jan 19, 2017, at 09:50 AM, Tim Cussins wrote:
> > > Any thoughts on the cleanest modification to LWIP that would allow the
> > > receive buffer to be drained?
> >
> > Yes: task #13922 (Remove fatal error handling) has to be done first.
> >
Hi Simon,
Thanks for the quick reply!
On Wed, Jan 18, 2017, at 08:36 PM, goldsi...@gmx.de wrote:
> Tim Cussins wrote:
> > We've encountered a couple of interesting http servers in the wild that
> > redirect, then send a TCP RST immediately.
> > [..]
> > In our case
Hi all,
We've encountered a couple of interesting http servers in the wild that
redirect, then send a TCP RST immediately.
Some http servers do this to avoid the TIME_WAIT state. Viz:
https://support.microsoft.com/en-gb/kb/272933
In our case, the data for the redirect appears to make it into
