The current agent/manager communications are over UDP, and I'd really appreciate them being over TCP to help tunnel them through more complex NAT/tunnel scenarios. In particular, being able to route them over an ssh port forward would be excellent.
There are a bunch of 'workarounds' on the net, based on nc or socat, but they are all inadequate because they assume packet boundaries are preserved over TCP (which is clearly not the case). They tend to work for the first couple of packets and then go wrong when multiple packets are sent in quick succession.
I had a quick look at the complexity of implementing this, and whilst the agent end looks reasonably straightforward, the manager end poses some issues, particularly with the routing of active response packets.
Note: This issue has been automatically migrated from Bitbucket
Created by mprocter on 2013-03-15 07:57:07+00:00
The current agent/manager communications are over UDP, and I'd really appreciate them being over TCP to help tunnel them through more complex NAT/tunnel scenarios. In particular, being able to route them over an ssh port forward would be excellent.
There are a bunch of 'workarounds' on the net, based on nc or socat, but they are all inadequate because they assume packet boundaries are preserved over TCP (which is clearly not the case). They tend to work for the first couple of packets and then go wrong when multiple packets are sent in quick succession.
I had a quick look at the complexity of implementing this, and whilst the agent end looks reasonably straightforward, the manager end poses some issues, particularly with the routing of active response packets.
Note: This issue has been automatically migrated from Bitbucket Created by mprocter on 2013-03-15 07:57:07+00:00