Sergio, no love for Richard Stevens? You always have constructive
advices, I see. :)
On 12/5/2016 5:52 PM, Sergio R. Caprile wrote:
You make capture files smaller by capturing at the right time and
enabling only the hosts/ports you need to see.
You understand TCP by reading Stallings, Comer,
You make capture files smaller by capturing at the right time and
enabling only the hosts/ports you need to see.
You understand TCP by reading Stallings, Comer, Tanenbaum... ;^) The
amount of data sent by a TCP stack is what it thinks best for the
current scenario, given its configuration. It
You are right, bytes are not missing, I just checked. This is not a real
problem then, it's just lack of understanding of TCP. :) It was strange
at first because I don't have similar problems at all when sending from
PC to ZYNQ.
When it comes to capture files, I am quite new to that, so I am
pekez wrote:
> The problem is that after some number of packets, client app receives
> less than TCP_MAX_DATA_LEN (which is 1446) bytes even though it isn't
> supposed to receive packet of that size at that moment. For example,
> after 1013rd packet sent, client receives packet that is less
Hi guys,
I have been trying to implement simple client - server apps that will
help me measure communication performance. Server is running on custom
ZYNQ board and is supposed only to send packets, whereas client is
running on PC and is supposed only to receive packets. I am using Lwip
v1.4.1.
