Secure reverse connection
Posted: Mon Sep 05, 2011 8:24 amClient encrypt + agent listener + agent server + agent forwarder + server decrypt
Take remote desktop as an example.
A. admin side:
1. network:
listen port = 5389, to port = 4389, to host = 127.0.0.1
2. coding :
select client, select encryption compress + AES
3. click start(0) standard routing
4. agent:
a. port forward definitions: 0.0.0.0,4389,127.0.0.1,4389,TCP
b. client common: s port = 2222, ip = 59.148.187.182 (agent server ip)
c. click start(2) button
d. click apply changes, for port forward definitions
B. control side:
1. network:
listen port = 4389, to port = 3389, to host = 127.0.0.1 (or another remote network computer ip)
2. coding :
select server, select encryption compress + AES
3. click start(0) standard routing
4. agent:
a. client common: s port = 2222, ip = 59.148.187.182 (or 127.0.0.1 if agent server is running on same control pc)
b. click start(3) button
Issue mstsc (terminal service client), type in 127.0.0.1:5389
If you issue command on your computer, ip always using 127.0.0.1. If access from another computer to your admin computer, type LAN ip of your computer.
Performance, compare normal connection with secure reversion connection
If connected, cpu usage is very slow. If click admin side connections button, you will find that remote desktop is using very less bandwidth. Compare with connecting remote pc by mstsc without Magic Router, the speed is almost the same.
Actually, remote desktop connection is encrypted, you do not need to make double encryption. This secure reverse connection sample is a theory.
If found error connection, try the following step by step.
1. Made connection simple first.
2. Test agent setup without encryption, without start up standard routing.
3. Test no agent, with coding client and server mode with encryption.
Take remote desktop as an example.
A. admin side:
1. network:
listen port = 5389, to port = 4389, to host = 127.0.0.1
2. coding :
select client, select encryption compress + AES
3. click start(0) standard routing
4. agent:
a. port forward definitions: 0.0.0.0,4389,127.0.0.1,4389,TCP
b. client common: s port = 2222, ip = 59.148.187.182 (agent server ip)
c. click start(2) button
d. click apply changes, for port forward definitions
B. control side:
1. network:
listen port = 4389, to port = 3389, to host = 127.0.0.1 (or another remote network computer ip)
2. coding :
select server, select encryption compress + AES
3. click start(0) standard routing
4. agent:
a. client common: s port = 2222, ip = 59.148.187.182 (or 127.0.0.1 if agent server is running on same control pc)
b. click start(3) button
Issue mstsc (terminal service client), type in 127.0.0.1:5389
If you issue command on your computer, ip always using 127.0.0.1. If access from another computer to your admin computer, type LAN ip of your computer.
Performance, compare normal connection with secure reversion connection
If connected, cpu usage is very slow. If click admin side connections button, you will find that remote desktop is using very less bandwidth. Compare with connecting remote pc by mstsc without Magic Router, the speed is almost the same.
Actually, remote desktop connection is encrypted, you do not need to make double encryption. This secure reverse connection sample is a theory.
If found error connection, try the following step by step.
1. Made connection simple first.
2. Test agent setup without encryption, without start up standard routing.
3. Test no agent, with coding client and server mode with encryption.