← All Docs

LAN Party Toolkit

Plan a LAN party network: see how devices find each other, look up game server and console ports, build a port-forward plan, and run a pre-party checklist.

Try LAN Party Toolkit →

What It Does

The LAN Party Toolkit helps you prepare a home or venue network for a game night. It explains how devices discover each other on a LAN, lists the ports used by common game servers, consoles, voice chat, and media apps, builds a plain-text port-forward plan for the host machine, and walks you through a hardening checklist for before and after the party.

What It Cannot Do

No web page can scan your network. Browsers have no raw sockets, so a page cannot ping, send ARP requests, or listen for mDNS and SSDP announcements, and browsers hide your local IP address. This tool never probes your network. It gives you the terminal commands to see devices yourself (arp -a, dns-sd, avahi-browse, nmap -sn on networks you own) and points you to your router's client list.

How to Use It

  1. Open LAN & Home > LAN Party from the top menu.
  2. Read How devices find each other and copy the commands for your operating system to see what is on your network.
  3. In Party service ports, filter by category or search a game name or port number.
  4. Tick the services you plan to run. LAN only services need no router change; Forward to host services only need forwarding when players join over the internet.
  5. Enter the host machine's LAN IP address and click Build plan to get the list of forwards to add on your router.
  6. Work through the Pre-party isolation checklist, then copy or download it.
  7. After the party, use the checklist's last section to remove the forwards and rotate the WiFi password.

Port Forwarding and UPnP

If everyone is in the same room, you do not need any port forwarding: LAN games find each other locally. Forwarding is only for players joining over the internet, and it should point at one host with a static DHCP lease. UPnP lets any device on the network open ports on the router; prefer manual forwards for the evening and remove them afterwards. Never forward remote administration ports such as RCON, SMB (445), or Remote Desktop (3389).

Isolation for a Party

  • Put players on a network separate from your home devices: a party VLAN, or the guest network with client isolation turned off for the evening.
  • Keep guest-to-home isolation on so players cannot reach your storage, printers, or cameras.
  • Set Windows guest PCs to the Public network profile and turn file sharing off.
  • Turn on SQM or Smart Queue if the router has it, and pause large downloads during play.

Use Cases

  • Home game nights: a Minecraft, Valheim, or Source server for friends, with a forward plan you can undo.
  • Console NAT problems: the documented Xbox, PlayStation, and Nintendo Switch ports in one place.
  • Venues and clubs: a repeatable checklist for setting up and tearing down a temporary network.
  • Learning: how ARP, mDNS, SSDP, and NetBIOS reveal devices, and why routers hide them.