Comments by Gabriel Lassonde (Top 2 by date)

Gabriel Lassonde 11-Feb-21 23:20pm View

Thank you for the suggestion!
I was able to use Wireshark to analyze the packets in both directions!
What a nice application.

I first looked at the packets sent (local ip to public ip) and I can confirm that the packets looked all good!

So I looked at the received packets (public ip to local ip) and the garbage data was exactly where I was expecting it.

a few things I noticed:
- Data was sent in "large" chunks... packets with 60k+ bytes.
- Data was received in fairly small chunks ~1400 bytes.
- at the middle of the transmission wireshark reported a bunch of "out of order" packets - is that problem?
- the garbage data data was just 16 bytes (out of 8mb) at the start of the data section one of the received packet.

so.... what conclusion should I take from this?

Gabriel Lassonde 10-Feb-21 10:19am View

Thank you for the links.
Regarding boost::asio::async_write, writing data larger than 65536 bytes - Stack Overflow[^]
I release the async_read buffer memory in the completion hander passed to async_read. I expected this is sufficient to ensure that the read operation is completed before releasing its memory.