Revision history [back]

https://github.com/abhinavjain241/comm_tcp looks like it was aiming to be a generic TCP/IP ros node- it or one of its forks could be a good starting point for a lot of these questions (like #q219872). It sends strings received by the client node and the server node publishes out any string it receives.

For talking to netcat I couldn't get a netcat client to talk to a comm_tcp server, but the other way around worked:

netcat -l 4444
rosrun comm_tcp client_node 127.0.0.1 4444
rostopic pub /client_messages std_msgs/String "data: 'foo'"

It puts the incoming String in a buffer and sends it repeatedly, but that is easy to fix.

Dynamic reconfigure for ports and server ip address and for connecting and disconnecting would be useful. Adding UDP and most anything else netcat can do would be good also.