Skip to content

Instantly share code, notes, and snippets.

@Nachlor

Nachlor/Lanemu_P2P_VPN_LAN_Gaming.md

Last active October 12, 2025 10:20
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save Nachlor/fdf2a5f9de1c14aecfc4c8617401a2f3 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save Nachlor/fdf2a5f9de1c14aecfc4c8617401a2f3 to your computer and use it in GitHub Desktop.
Download ZIP
Lanemu P2P VPN LAN Gaming
Raw
Lanemu_P2P_VPN_LAN_Gaming.md

Lanemu P2P VPN LAN Gaming

Table of Contents

Preparations (Linux)

Preparations (Windows)

  • Disable SSDP Discovery
    • Open Control Panel
    • Click System and Security
    • Click Administrative Tools
    • Open Services
    • Right click SSDP Discovery and select Properties
    • Click Stop
    • Startup type: Disabled
    • Click Apply and OK
  • Enable DirectPlay and Media Features
    • Open Control Panel
    • Click Programs
    • Click Turn Windows features on or off
    • Expand Legacy Components
      • Check DirectPlay
    • Check Media Features
    • Click OK
  • Allow DirectPlay and game through Windows Firewall
    • Open Control Panel
    • Click System and Security
    • Click Allow an app through Windows Firewall
    • Click Change settings
    • Click Allow another app
    • Click Browse
      • DirectPlay
        • Go to C:\Windows\SysWOW64
        • Select dplaysvr.exe and click Open
      • DirectPlay 8 (x32)
        • Go to C:\Windows\System32
        • Select dpnsvr.exe and click Open
      • DirectPlay 8 (x64)
        • Go to C:\Windows\SysWOW64
        • Select dpnsvr.exe and click Open
      • Game
        • Go to game directory
        • Select game executable and click Open
    • Click Network types
      • Check Private and Public
      • Click OK
    • Click Add
    • Click OK
  • Optional recommendations

Usage

  • Get the latest Lanemu release by clicking Download under Packages
  • Extract the downloaded Lanemu archive to a new folder called Lanemu
  • Navigate to the OpenJDK page by clicking "Ready for use" JDK version
  • Download OpenJDK
  • Extract the downloaded OpenJDK archive to Lanemu -> build folder
    • Rename the extracted OpenJDK folder to jdk
  • Windows : Install Lanemu network adapter
    • Navigate to Lanemu -> driver folder
    • Right click add_adapter.bat
    • Click Run as administrator
  • Windows : Make sure Lanemu.exe is always run as administrator
    • Navigate to Lanemu -> build folder
    • Right click Lanemu.exe
    • Click Properties
    • Select Compatibility tab
    • Check Run this program as an administrator
    • Click Apply and OK
  • Launch Lanemu
    • Windows
      • Open Lanemu.exe
    • Linux
      • Open the Terminal in Lanemu -> build folder
        • sudo ./jdk/bin/java -jar Lanemu.jar
  • Do you want to join 'Default network'?
    • Click No
  • Click the Options icon and select Global tab
    • Specify Your Name
    • Specify any port in "Listen on Port" (e.g., 6666)
      • At least one user should enable UPnP or forward this port on the router
        • It is recommended to forward this port for both TCP and UDP
        • If you wish to only use TCP
          • Select Network tab and uncheck Use UDP for peer to peer traffic
      • If nobody can forward a port (stuck behind NAT)
        • All users can use hyper-nat (make sure everyone uses the same port)
        • If hyper-nat fails to connect, all users can route Tailscale or other similar VPN through Lanemu
          • Lanemu allows Layer 3 VPNs to work in games that require Broadcast / Multicast
          • Replace all instances of PublicIP:Port with Tailscale or other VPN IP (e.g., 100.111.88.108:6666)
        • Alternatively, one user (Host PC) can create a tunnel (e.g., playit.gg)
          • Lanemu supports TCP+UDP or TCP-only tunnels
          • Tunnel type requirements (TunnelIP:TunnelPort -> 127.0.0.1:LanemuPort)
            • TCP+UDP (e.g., tcp-udp-tunnel.gl.at.ply.gg:5359 -> 127.0.0.1:5359)
              • TunnelPort and LanemuPort must be identical
            • TCP-only (e.g., tcp-tunnel.gl.at.ply.gg:5359 -> 127.0.0.1:6666)
              • TunnelPort and LanemuPort can be the same or different
              • Host PC user must disable UDP option in Lanemu
                • Select Network tab and uncheck Use UDP for peer to peer traffic
    • Click OK
  • Steps for Host PC
    • If you are using hyper-nat
      • Modify hyper-nat options.json file 
        {
    "schema": [
        {
            "mode": "server",
            "proto": "udp",
            "port": "6666",
            "host": "127.0.0.1",
            "secret": "SomeUniqueTextThatIsTheSameForAllPorts"
        },
        {
            "mode": "server",
            "proto": "tcp",
            "port": "6666",
            "host": "127.0.0.1",
            "secret": "SomeUniqueTextThatIsTheSameForAllPorts"
        }
    ]
}
      • Launch hyper-nat
        • Windows
          • Open hyper-nat.exe
        • Linux
          • Open another Terminal in Lanemu -> build -> hyper-nat folder
            • npm install
            • npm run start
      • Windows : Allow hyper-nat through Windows Firewall
        • Check both Private and Public networks
        • Click Allow access
      • Copy your public key from the Console / Terminal
        • Windows
          • Highlight it and press CTRL + C
        • Linux
          • Highlight it and press CTRL + SHIFT + C
      • Send your public key to every Client
    • Create a network
      • Click the New Network icon
      • Select Simple tab
        • Specify Network Name
      • Select Advanced tab
        • If you are using UPnP / Port Forwarding or Tunneling Services
          • Specify your PublicIP:Port or TunnelIP:Port in Known Hosts
            • Example: 82.129.80.111:6666 or tcp-tunnel.gl.at.ply.gg:5359
        • If you are using hyper-nat
          • Specify these network settings
            • Known Hosts: 127.0.0.1:6666
            • BitTorrent Trackers: Empty
            • Enable DHT search for peers: No
      • Click OK
    • Windows : Allow OpenJDK through Windows Firewall
      • Check both Private and Public networks
      • Click Allow access
    • Create an invitation
      • Click the Invite Someone icon
      • Check Allow invitation of others
      • Click Generate Invitation
      • Click Save to a File
      • Click Close
    • Send the invitation file to every Client
  • Steps for Client PC
    • If you are using hyper-nat
      • Temporarily close Lanemu
        • Right click Lanemu tray icon and select Quit
      • Modify hyper-nat options.json file 
        {
    "schema": [
        {
            "mode": "client",
            "proto": "udp",
            "port": "6666",
            "serverport": "6666",
            "publicKey": "CopyPasteTheServerPublicKeyHere"
        },
        {
            "mode": "client",
            "proto": "tcp",
            "port": "6666",
            "serverport": "6666",
            "publicKey": "CopyPasteTheServerPublicKeyHere"
        }
    ]
}
      • Launch hyper-nat
        • Windows
          • Open hyper-nat.exe
        • Linux
          • Open another Terminal in Lanemu -> build -> hyper-nat folder
            • npm install
            • npm run start
      • Windows : Allow hyper-nat through Windows Firewall
        • Check both Private and Public networks
        • Click Allow access
      • Wait until hyper-nat establishes connection to the server
        • The window closes if connection fails, you might have to retry several times
      • Relaunch Lanemu
    • Join a network
      • Click the Accept Invitation icon
      • Click Load from File
      • Click OK
    • Windows : Allow OpenJDK through Windows Firewall
      • Check both Private and Public networks
      • Click Allow access
    • Wait for connection
      • If connection did not occur automatically
        • Option 1 : Click the Connect to Known IPs icon at the bottom
        • Option 2 : Click the Information icon at the bottom and select Connections tab
          • If you are using hyper-nat
            • Enter 127.0.0.1:Port (e.g., 127.0.0.1:6666) next to the Connect To button and click it
          • If you are using other connection method
            • Enter a peer PublicIP:Port or TunnelIP:Port next to the Connect To button and click it
  • Linux : Open another Terminal to add Broadcast and Multicast routes
    • sudo ip route append 255.255.255.255/32 via 0.0.0.0 metric 0 dev tap0
    • sudo ip route append 224.0.0.0/4 via 0.0.0.0 metric 0 dev tap0
@Monsterovich
Copy link

Monsterovich commented Aug 8, 2025 •
edited
Loading

And latency from Lanemu Virtual IP are not stable sometimes, you can see the suddenly 85ms latency while the Pubic IP got stable ~25ms

This is unlikely to be related to Lanemu. Packets are being lost. I can reproduce this randomly on any public IP address. Just make sure you have UDP mode enabled. I would avoid TCP/UDP in TCP when possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment