How to use hcitcptest

You can’t run the hcitcptest program on the same port that you are already running on a thread.  You won’t be able to bind to that tcp port.

If you are debugging a thread that is already defined and running, and you want to see what is being sent and received, you can temporarily turn up the “engine noise” on that thread using the EO Config (enable_all) for that thread.  Then you can look at log and see the data outbound and the ack/nak inbound.  

You can also save the inbound messages (replies) on an outbound thread so you can see the acks/naks.

Think of hcitcptest as a quick way to create a temporary interface with a one line command.

I have used it for doing quick connectivity testing.

I also found it usefull to verify that our new servers would fail-over the IP address transparently for inbound and outbound traffic even before I put cloverleaf on the box.

That’s right hcitcptest is a standalone perl script that can be copied and run without installing cloverleaf.

I’ve only run it in interactive mode and just type in what I want to send across then hit enter and see what comes back.

That means it can also be useful to quickly send across a bogus message to see if you get the desired NAK behavior.

I did notice in your example you did not supply the -t argument with a value.

Here are the listed options for -t