I vote for sharing.
Perhaps you could write a patch or give an example and us interested
users can also help ?
What about the API ? I guess there is the need for a new function that
returns the number of available responses and provides a means to
retrieve them either one by one or all at
You should not free the pcb in the error callback, it does not get a pcb
as a parameter (unless you provide it). It is intended for you to free
your resources (if any).
Some people advocate for the check your goesintos mantra.
I personally prefer smaller and tighter code.
There is a nice
Hi all,
I found my problem i messed up with the acknowledgement. I used ->len
instead of ->tot_len.
Thanks for the help.
Norbert
Am 2016-09-09 11:01, schrieb norbert.kle...@student.fh-kiel.de:
Hi Jan,
thank you for your fast reply. I don't use the window update function.
The unexpected
Hi,
As it turned out it was a problem with the MAC address, that I cannot
understand at all. I changed the MAC address and it worked like a charm.
The odd part is that previously I had tried at least 20 different MAC
addresses that didn't work. Most of them were from online MAC generators,
but
Hi Norbert!
The advertised receive window size specifies the amount of memory the
stack can consume without further acknowledgement. Once the application
side has read received data and acknowledged/freed it, the receive
window is enlarged by this amount and - after a certain timeout - a
Hi all,
I have a small question. Under which circumstances does the lwIP stack
reduce the window size even while the window update is disabled.
I am sending 16 kB to the microcontroller (lwIP-Stack) copy them to a
certain address and send them back to the laptop (linux). At the end of
the
