PacketSender | Network utility for sending / receiving TCP, UDP, SSL, HTTP | TCP library

Apparently Windows Defender by default blocks the Unity Editor (but not UdpSenderReceiver).

I had to resolve it by Admitting the Unity Editor on the public domain

The Rules for

• Unity 2019.3.3f1 Editor
• Unity 2019.3.4f1 Editor

had been present and were not modified.
I modified the Rule for Unity 2019.2.4f1 Editor in order to allow access from the public domain (I simply allowed all domains).

am I using the TIdTCPClient safely?

Yes, you are.

Data, on the other hand, not so much, since it is not shown as being a local variable, or even a member of the TPacketSenderLAN class, which means it must be a global variable instead, and thus would be subject to multithread concurrency issues. In this case, it should be a local variable.

Do I have to disconnect it?

I would recommend it, yes, particularly before calling your OnSuccess/OnError handlers. If you don't call Disconnect() manually, the TCP connection will not be disconnected until the TIdTCPClient destructor is called. In this code, there is no reason for the TCP connection to remain active while your event handlers are running.

I don't know if I should call Client.Disconnect; inside the finally block.

I would actually suggest adding another try..finally block just to call Disconnect(), eg:

The logical (and correct) solution is to use mutual exclusion on std::cout. You know the appropriate scope of the lock (in your case, just a single UDP packet, but std::cout cannot guess that).

The fancy solution is boost.asio.strand. You don't need that for simple cases like this, but since you're trying to use boost.asio.io_context you should know that there is another class in boost.asio that could work like you intended.

I have answer about this :

• Thanks alot to @jackw1111, your comment as clue : When working with raw sockets in scripts, most operating system require advanced privileges (e.g. root user) to run them.
• Send packet must in ascii :

I have no idea what this "TCP parsing utility" is but I assume it is something which does not work on the normal TCP stack but instead has either some custom stack (i.e. some embedded system with minimal stack) or tries to capture traffic and process it manually - but wrong.

The difference between these two pcap's is that PacketSender first does the TCP handshake and only then sends the data while the Axis sends the data already within the last packet of the handshake: