Forum Discussion
TCP monitor with sending a byte sequence
- 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 ?
Hi Stefan, there are examples of using TCP hex string monitors with Oracle Coherence Extend Proxies. You can find both native TCP and External script monitor examples in this deployment guide:
http://www.f5.com/pdf/deployment-guides/oracle-coherence-extend-dg.pdf
You do need BIG-IP version 10.2 or higher for this to work I believe.
-Chris.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com