Feature #64
Remove dependency on TCP ports for 2-way communication (passive mode)
Status: | Closed | Start: | ||
Priority: | Normal | Due date: | ||
Assigned to: | Mirco Bauer | % Done: | 100% |
|
Category: | Server | |||
Target version: | 0.6.4 | |||
Complexity: | ||||
Votes: | 0 |
Description
Currently both the client and server need open ports for successful communication. Since most home-level connections come with port restrictions, and because you can basically do everything inside a single TCP connection, remove the need of a client having an open TCP port.
History
Updated by Mirco Bauer 5940 days ago
I agreed with Cobrian that a temporarly solution using TcpChannel + SSH tunnel (controlled by smux) is acceptable to solve firewall and NAT issues. In the long term the TcpChannel itself should be smarter or be replaced by something else.
Updated by Mirco Bauer 5912 days ago
- Status changed from New to Closed
- 1 set to fixed
Implemented in SVN r427
Updated by Mirco Bauer 5815 days ago
- Status changed from Closed to Feedback
- 1 deleted (
fixed)
Well this is not fully completed yet, as you can't configure it.
Updated by Mirco Bauer 5697 days ago
- % Done changed from 0 to 80
The Engine Manager needs SSH settings.
Updated by Mirco Bauer 5673 days ago
- Target version changed from 0.8 to 0.6.4
Updated by Mirco Bauer 5600 days ago
- Status changed from Feedback to Closed
- % Done changed from 80 to 100
SSH is now fully configurable with the GUI.
Implemented in git commit 15440b60da30f55775edf75e42bcb7ca9a140002