Forum Discussion

Stefan_Klotz_85's avatar
Stefan_Klotz_85
Icon for Cirrus rankCirrus
Jul 14, 2014
Solved

TCP monitor with sending a byte sequence

One of our customers is using a TCP/IP based application and instead of using the default TCP monitor, they will check their application with sending a specific byte sequence after the TCP connect. I...
application delivery
availability
LTM
TMOS
  • 0x0ff_info_1420's avatar
    0x0ff_info_1420
    Jul 23, 2014

    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 ?

     

Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
Jul 14, 2014

Here's a thought: use an external monitor with netcat and xxd. Here's an example:

echo '47455d782...hex data...0a0d0a' | xxd -r -p | nc 10.70.0.1 80

Take a look at the sample_monitor Bash script under /config/monitors and you should get an idea on how to deploy the above.