p2p-port-mapping

p2p port forwarding/mapping across NAT/firewalls, Access your server anywhere.
中文说明

Features

• P2P port forwarding/mapping, eliminating the need for a data relay server.
• P2P TLS encrypted port forwading/mapping, keep your data secure.
• No requirement for administrator or root privileges.
• NAT traversal without the need for router configuration.
• Supports multiple clients and multiple connections for each tunnel.
• Utilizes node-datachannel to establish a data tunnel, with SCP rates reaching up to 400Mbps for the tunnel.

Installation

1. install nodejs
2. git clone https://github.com/yuanzhanghu/p2p-port-mapping.git
3. cd p2p-port-mapping
4. npm install

Example1: remote SSH (verified on linux)

Assume that we want to do ssh from computer B to computer A across firewalls, we can do port mapping like:
1. on computer A (which want to share port), mapping port to serverKey:
 node main_server.js --port 22

get printed log:
 2023-11-08 19:37:10 mappingServer info: server_registered, local port:22 ====> serverKey:KJASD2DW2 

please write down the serverKey.

2. on computer B, mapping serverKey in to a localhost port:
// above serverKey is used on computer B
  node main_client.js --port 8082 --key <serverKey-displayed-in-step1>

get printed log:
2023-11-08 19:37:20 mappingClient info: tunnel established. serverKey:KJASD2DW2 ====> local port:8082


3. now we can do this on B:
ssh user@localhost -p 8082

above command will ssh to A actually.

Example2: remote Desktop (verified on linux and windows)

1.Assume that we want to do remote desktop access from computer B to computer A across firewalls.
On computer A (which want to share desktop), enable remote desktop sharing, mapping port to serverKey:
 node main_server.js --port 3389

get printed log:
 2023-11-16 17:37:10 mappingServer info: server_registered, local port:3389 ====> serverKey:KJASD2DW2
write down the serverKey, which will be used in step 2.

2.on computer B, do this: 
 node main_client.js --key KJASD2DW2 --port 9389

get printed log:
2023-11-16 17:37:41 startClient info: tunnel established. serverKey:KJASD2DW2 ====> local port:9389
3.Then  on computer B: we can do remote desktop access to localhost:9389, which is actually accessing to A.

Signal Server For WebRTC

Current signal server is using socket.io running on ai1to1.com, you can run your signal server as well. Source code is located in signal_server/, just run:

python3 api_server.py

STUN / TURN Server For WebRTC

Currently using:

[
  'stun:stun.l.google.com:19302',
  'turn:free:[email protected]:3478',
]

You can change them in startCleint.js and startServer.js

Contact

email: [email protected]