Forum Discussion
CirrusTCP monitor with sending a byte sequence
Why do you use -l parameter ? It's mean listen so, your commands wait for connexion and send your binary payload.
The nc error message tell you that you can't listen on an interface you don't own. Till now, I didn't know we could specify the address. :p
But what you do there is not what I wanted to explain to you in my first post. I told you (but not clearly, i admit :p) that you could use regular TCP monitor in TMSH or GUI. In the field Send String and in the field Receive String you can actually use the escaped string. ;) More simple than with the nc script no ?
CirrusWhy do you use -l parameter ? It's mean listen so, your commands wait for connexion and send your binary payload.
The nc error message tell you that you can't listen on an interface you don't own. Till now, I didn't know we could specify the address. :p
But what you do there is not what I wanted to explain to you in my first post. I told you (but not clearly, i admit :p) that you could use regular TCP monitor in TMSH or GUI. In the field Send String and in the field Receive String you can actually use the escaped string. ;) More simple than with the nc script no ?
Amit585731Nimbostratus
Hi, can you please suggest what will be the correct send and monitor string for below requirement: UDP monitor should probe on 2723 and it should contain the string "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789" with a hex value of 02 before the string and a hex value of 00 after it. So the full hex string of the data segment would be: 02 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 30 31 32 33 34 35 36 37 38 39 00. The servers will respond with their hostname (e.g., host1 or host2) followed by a pipe character ("|") followed by the string sent ("ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789") to indicate success.- 0x0ff_info_1420Your send string should be you hex string escaped (\x02\x41...\x00), and something like "\x68\x6f\x73\x74\x31..." for your received I guess.
