proxy?

[Zibri]

I don't know how to pose this question...

but can websocked instead of listening on a local port, connect to a remote server?

Let's say machine A is behind a firewall. Machine B is rechable by the world Machine C wants To connect to machine A

il would be nice if websocked could connect to a server on machine B so machine C can connect to the same server and talk to machine A

[asergeyev]

Why not to run basic HTTP proxy? It's simple to configure nginx or write basic program that would handle requests on machine B and sent them to A. Websocket connections are regular HTTP.

Surely you can also run websocketd and proxy with it but it to another instance somehow. I just think it's overkill...

Another relatively computationally expensive option is to run websocketd on machine B and configure it to run ssh username@A command

(ensuring proper auth using private keys so ssh does not ask for a password)