How to Use Duowire
What to do on the Host, what to do on the Remote, and how to point real tools at the connection once it's up.
Host and Remote
1. Open Duowire on the PC whose network you want to reach.
2. Click “Share this network” to generate a connection code — random by default, or set a memorable permanent one for a machine you share often.
3. Send the code to whoever's connecting in — that's it.
4. Duowire handles the rest automatically: it tries a direct peer-to-peer link first, and falls back to the relay if NAT or a locked-down network gets in the way.
Full video walkthroughs
Real screen recordings of Duowire in use, start to finish.
First-time setup and network sharing
Paste the relay-config string once per machine, then share your network with a connection code.
Direct P2P on an unrestricted network
Connect with a code and watch the link upgrade from the relay to a direct peer-to-peer tunnel.
Connecting via relay on a restricted network
When direct P2P can't form — locked-down Wi-Fi, symmetric NAT — the relay carries the tunnel instead.
Adding a SAP application server
Forward a SAP application server to a dedicated loopback address and log on through the SAP Logon pad.
Adding a custom port forward
Forward any LAN service — like a self-hosted app — to a local loopback address and open it directly.
Platform guides
Step-by-step instructions for your platform, including install, SAP GUI setup, and troubleshooting.
Example use cases
SSH into a machine on the Host's LAN
Simplest path — define a port-forward once, then connect straight to it:
ssh user@127.0.0.1 -p 2222Or route any SSH target through the SOCKS5 proxy directly:
ssh -o ProxyCommand="nc -X 5 -x 127.0.0.1:1080 %h %p" user@192.168.1.50Connect to SAP GUI on the remote network
Duowire assigns a dedicated loopback IP per SAP application server. Add a new entry in the SAP Logon pad using that address:
Application Server: 127.10.1.2 · System Number: 00 · Client: 100SAProuter strings and direct logon both pass through unchanged.
Reach self-hosted apps through the SOCKS5 proxy
Point any SOCKS5-aware client at the proxy and browse the LAN normally:
curl --socks5-hostname 127.0.0.1:1080 http://homeassistant.local:8123In Firefox, enable “Proxy DNS when using SOCKS v5” in network settings so LAN hostnames resolve on the Host's side instead of failing locally.