p2pRemote Advanced Features Guide

Manage devices

Use recognizable aliases and remove only devices that are retired, reinstalled, or no longer used. Presence updates periodically, so a recently disconnected device may take a short time to appear offline.

Remote assistance with a connection code

Remote assistance connects to another person's device without sharing accounts. The invite includes a device connection code and one-time password.

1. The recipient generates an invite.
2. They send the full invite through a trusted channel.
3. The helper pastes the invite or enters the code and password.
4. Start the connection and wait for the tunnel.
5. Use the resulting address in RDP, VNC, RustDesk, or another remote application.

Note: The one-time password rotates after use. Do not publish or retain old invites.

Active and passive tunnels

• Active: this device initiated the connection.
• Passive: another device connected to this device.
• Tunnel Status separates both groups and shows duration and network details.
• Disconnect any unrecognized passive session immediately.

Latency, traffic, and speed tests

Connection details show duration, latency, and transferred data. Speed tests measure current round-trip delay and bidirectional throughput; Wi-Fi, background traffic, inter-ISP paths, CPU, and security tools affect results.

Note: Speed testing consumes sustained traffic and should be limited on metered networks.

Recovery and manual recreation

The client attempts recovery after a short interruption. If recovery expires, close tunnel applications, clean up the failed session, restore both networks, and create a new tunnel.

Configure remote LAN access

1. Run ipconfig on the passive endpoint and identify the remote subnet.
2. Select This device and enable peer LAN access.
3. Enter one IPv4 CIDR per line, such as 192.168.1.0/24.
4. Save, disconnect, and recreate the tunnel.
5. Reach remote devices by their real private addresses.

• 127.0.0.0/8 and 100.99.71.0/24 cannot be exposed.
• Forwarding supports TCP, UDP, and ICMP.
• Android can consume remote LAN routes but cannot expose its own LAN.
• Overlapping local and remote subnets can cause routing conflicts.

Background and unattended operation

• Closing the window normally leaves the tray app and service running.
• Fully quitting prevents the endpoint from accepting connections.
• Enable startup where required and prevent target sleep.
• Verify account recovery and presence after reboot.
• Do not let adapter power saving disable connectivity.

Platform limitations

• Android can initiate but cannot currently accept a tunnel or expose its LAN.
• Windows Home cannot host built-in RDP; third-party options require separate evaluation.
• LAN access depends on the passive endpoint service remaining available.
• Tray, startup, and notification behavior varies by platform release.