Re: [lwip-users] tcp_write function merges 2 different packets while sending

[Liju John]

Still you can disable the streaming feature of the TCP and send like udp packets with TCP_NODELAY set socket option on the TCP level. This option is available on the socket. You can explore on it.

--Liju.

On Mon, Dec 23, 2019 at 2:57 PM Ajay Bhargav <address@hidden> wrote:

TCP will tend to merge that’s expected behaviour. You need to check your server side application. SSL usually reads the expected number of bytes while handshaking/doing any kind of transaction. So even if packets are merged server side will read bytes in expected order.

 

-Ajay

 

 

From: Urvi
Sent: Monday, December 23, 2019 2:39 PM
To: address@hidden
Subject: Re: [lwip-users] tcp_write function merges 2 different packets while sending

 

Thank you Everyone for your reply.

 

First of all I am using TLS/SSL handshaking over lwIP for my IoT

application. So I can't opt for UDP instaed of TCP.

Second thing is that all data packets of any size (i.e. 6/45/51/384/854

bytes) are generated by TLS library at the time of handshaking. So I don't

have any control on data packet framing as it is done by tls library.

 

So in this case how am I able to overcome this problem?

 

 

 

 

--

Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html

 

_______________________________________________

lwip-users mailing list

address@hidden

https://lists.nongnu.org/mailman/listinfo/lwip-users

 

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users