M2M: Send Cancel_Operation packet, when knock gets a packet as response that is not "MagicData" packet

First CLI Flasher command leaves the netX inside an endless loop

If the last ACK packet of a command gets lost and the Host has already continued with it's process and the netX is still waiting for the ACK packet (stuck in a loop). Therefore the netX continuously sending the last packet.

Second CLI Flasher command starts a new communication to netX

The host tries to connect to the netX via the knock-knock request.

Host expects the "MagicData" packet as answer, but the netX is inside the endless loop and sends the last packet.

Now the host continues to resend the knock request.

Both side are now stucked inside an endless loop.