Hello Amit
Thanks for for help.
No this did not make much difference, but I had forgot the TI lwiplib.c
file has loads of includes, that was pulling in 1.4.1 files in!
As you have it working , could you please say if it is just a case of
changing all the references to 1.4.1 to 2.0.2 or is
On 18.05.2017 21:37, goldsi...@gmx.de wrote:
> Jan Menzel wrote:
>> At the end, the buffer size required for encrypting/decrypting
>> transmitted/received data is something, that depends on your setup and
>> on configuration options commonly available. So, if you carefully
>> control and debug
Jan Menzel wrote:
At the end, the buffer size required for encrypting/decrypting
transmitted/received data is something, that depends on your setup and
on configuration options commonly available. So, if you carefully
control and debug your setup you probably can run with less memory.
Hi Sandeep!
I've an application where about 500kb of JS-Code, webpages and other
stuff is loaded by the browser initially. This does not require more
then 2..3 connections in parallel (a pool of 4 clients was always enough).
At the end, the buffer size required for
Noam Weissman wrote:
> Is there a way to limit the number of concurrent HTTP connection, say to one ?
Listen backlog does not help much here. You'd have to close the listener after
accepting the first connection.
Reopening it later might require SO_REUSE though.
Alternatively, you could set
Hi Simon,
Is there a way to limit the number of concurrent HTTP connection, say to one ?
If this can be done we may be able to run HTTPS with an overhead of about 40K
for SSL/TLS
BR,
Noam.
-Original Message-
From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On
Marco Jakobs wrote:
> It's not that easy as we are using NAT which needs to be modified as some
> structures seems to have changed between LwIP 1.4.1 and 2.0.2.
Oh, yeah. Well, NAT should not be *that* different from any callback API
application...?
> I wanted to test the difference, but after
Sandeep wrote:
> Could you please give me a rough figure of how much RAM it may
> use, just to know whether it is viable in the above said system?
The most consuming part is that TLS requires 16 kByte per direction and
connection as encrypt/decrypt buffer.
As modern web browsers open multiple
Thank you all for the response.
I am planning to use an RTOS + lwip + mbedTLS in an embedded system which
has 6MB flash memory and 768KB RAM. Goal is to run an https web server. RTOS
could be eCOS or FreeRTOS; yet to be fixed.
@ Simon - Could you please give me a rough figure of how much RAM it
Hi Simon,
>Yes, but have you actually tested 2.0.x to see it increased?
Not yet. It's not that easy as we are using NAT which needs to be modified as
some structures seems to have changed between LwIP 1.4.1 and 2.0.2. I wanted to
test the difference, but after >100 compile errors I gave up for
10 matches
Mail list logo
