jpillora / chisel

A fast TCP/UDP tunnel over HTTP

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Random opened port for local binding in case its not given

a-urth opened this issue · comments

Current logic defaults local port to remote one in case former is not given. Maybe it makes sense to use any opened port for local port on a server side at least for reversed connections? Otherwise there is no way for client to determine which port to use for local binding on a server in case there is a lot of connections and ports might be already used on a server while they are free on a client.

Maybe my use case is too specific, but for reversed connections from a client standpoint why would i care what bound to what? And on a server there is multiple of ways to determine which port from which client is bound to what.

On the other hand it might be optional. If for local keyword random is used, then server will choose bind port on random. Kind like stdio is used for specific use case.