✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316), with Beelink Mini S12 Pro Mini PC (Intel N100, 16GB, 500GB SSD) as a strong alternative.

A LAN party on Linux is not hard, but it punishes improvisation: half the room cannot see the server, one machine spends the first hour patching over congested Wi-Fi, and someone discovers the headline game has no LAN mode at all. All are planning problems, solvable the night before with a wired switch, a written address plan, and one modest Linux box in the corner.

This playbook assumes a living room or garage, six to sixteen players, and a mixed room of Linux desktops, Steam Decks, and Windows machines. It covers the network layout, how game files move around the room, the server box’s role, which games support local play, and where mixed-OS friction hides.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

A Linux LAN party works best wired: one unmanaged gigabit switch at the centre, every PC on a planned static address, and one Linux box acting as game server and file cache. Preload games, enable Steam local network transfers, and pick titles with real LAN modes, because most modern live-service games still need the internet.

The network plan

Put a single unmanaged gigabit switch in the middle of the room and run a cable from it to every seat. Unmanaged matters: there is nothing to configure or misconfigure, and the switch forwards traffic at wire speed. Size it one step above your headcount. Sixteen ports covers most home parties.

Give the room its own addressing plan instead of trusting automatic assignment. Pick a private range, put the server box at the first address, hand each seat a fixed address in sequence, and tape the plan to the switch. Static addresses remove the classic delay where a server runs perfectly but half the room looks for it on an address it had yesterday.

Keep the house router as an uplink only, for logins and games that insist on phoning home; party traffic should never need to leave the switch. Turn off wireless once cables are in, because several systems quietly prefer a remembered Wi-Fi network even with a cable plugged in.

The content plan

The biggest quality-of-life upgrade in modern LAN parties is that Steam can copy an installed game from one PC to another over the local network instead of downloading it again. The feature, local network game transfers, lives in Steam’s download settings and works between Linux and Windows machines alike. One machine, ideally the server box or the host’s desktop, holds a complete, updated copy of every listed game. Guests missing a title start the install, and Steam pulls the files from the local peer at switch speed.

Prepare the day before: update every listed game on the master machine and verify the files so the shared copy is clean. Guests should arrive with Steam logged in, transfers enabled, and the games owned, since transfers move files, not licences.

For groups that meet regularly, the next step up is a caching proxy on the server box: open-source LAN cache projects store intercepted downloads on local disk, so repeat downloads of the same title arrive at local speed. It only pays off across multiple events, but it turns patch day into a non-event. Either way, the internet is for logins, never bulk data.

The server box

One modest Linux machine should run the evening’s infrastructure: the dedicated game servers, the file share, local voice chat if you want it, and the cache if you run one. It does not need a gaming GPU. Dedicated servers for LAN-friendly titles are light on CPU and memory, and a low-power mini PC or NAS-class box with a quad-core processor and solid-state drive handles several at once while staying quiet.

Install the servers before the event, not during it. SteamCMD fetches dedicated server builds for Valve titles and many third-party ones, most with documented Linux builds. Start each server at home, join it from a second machine, and confirm it appears at its planned address. A server that has never had a client connect is a hypothesis, not a server. Wire it into the main switch.

A NAS can play this role if it uses an x86 processor and supports containers. A mini PC is more flexible, running a full desktop Linux distribution with no platform limits. Storage speed beats capacity here: a solid-state drive keeps transfers snappy when twelve people hit the box at once.

The game list reality

Build the list around what actually works in a room, because the modern catalogue splits sharply in two. On one side sit titles with real local play: sandbox and survival games with dedicated servers, strategy games with LAN lobbies, classic shooters, and host-based co-op games. Minecraft, Factorio, Terraria, Valheim, Left 4 Dead 2, Age of Empires II: Definitive Edition and Counter-Strike 2 in local-server mode are the shape of a reliable list: all keep working with the internet reduced to a login check.

On the other side sit the live-service headliners. Fortnite, Valorant, Apex Legends, Destiny 2 and most current hero shooters have no LAN mode and no local server; they matchmake through the publisher’s infrastructure and treat a LAN party as eight separate internet sessions sharing a sofa. They gain nothing from your switch, and an outage ends the match for everyone. Never build the night on them.

Proton changes none of this. A Windows-only game with a LAN mode generally keeps it under Proton, because the networking is ordinary socket traffic, and if it runs well solo it behaves the same on the wire. Test the exact build before the event, since a fresh patch can change behaviour.

Mixed-OS friction points

Linux and Windows machines play together well, but a few seams show up predictably. Firewall prompts are the first: Windows guests may have the network classified as public, which silently blocks discovery and direct connections, so every Windows player should set the party network to private before the first match. On Linux, an active firewall needs the game ports allowed or a pause for the evening.

Discovery is the second seam. Some games find servers by broadcast, which works only when everyone is on the same subnet. When discovery fails, direct connection by IP address is the universal fallback, which is why the server box has a fixed address on the printed plan. Finally, versions must match everywhere: a game stale on one machine excludes that player from every lobby, so the content plan and the version check are the same step.

How to choose

Scale the kit to the headcount. For four to six players, an eight-port switch, a pack of short patch cables, and the host’s desktop doubling as the server box is enough. For eight to twelve, move to a sixteen-port switch, add a dedicated server box so the host’s machine stays free to play on, and preload through local transfers. For twelve to sixteen, keep the layout but add solid-state storage and a written run sheet. At every size, choose cables by the room: short leads near the switch, one long run to the router, and spares always.

Who should skip this

Skip the full wired build if your group is four people who only play online live-service titles; a switch adds nothing when every match runs on the publisher’s servers, and a decent router is the whole setup. Skip it, too, if the venue cannot run cables safely. And if your games are all single-player or couch co-op on one screen, the existing living-room setup already does the job.

The kit

NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316)

NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316)

NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316)

Check price on Amazon

The centre of the layout: sixteen gigabit ports in a fanless metal case that never needs configuring. One port goes to the router, one to the server box, the rest to seats.

Specs:
– Ports: 16 gigabit RJ45
– Type: unmanaged, plug and play
– Model: GS316-300NAS
– Housing: metal, desktop or wall mount
– Power draw: 8.1 W maximum

Cable Matters 10Gbps 5-Pack Snagless Cat 6 Ethernet Cable (6 ft, Black)

Uniform short leads for seats nearest the switch, so every desk gets the same cable and troubleshooting stays simple. Snagless boots survive being coiled and re-run at every event.

Specs:
– Category: Cat 6 UTP, rated to 10 Gbps
– Conductors: 24 AWG bare copper
– Bandwidth: 550 MHz
– Length: 6 ft per cable, pack of 5
– Model: 160001-BLK-6×5

Cable Matters 10Gbps Snagless Cat 6 Ethernet Cable (25 ft, Black)

The one long run in the kit: router to switch, or switch to the far table, with no join in the middle and no coupler to fail mid-match.

Specs:
– Category: Cat 6 UTP, rated to 10 Gbps
– Conductors: 24 AWG bare copper
– Connectors: RJ45, gold-plated contacts, snagless boot
– Length: 25 ft
– Model: 160001BLK25

Beelink Mini S12 Pro Mini PC (Intel N100, 16GB, 500GB SSD)

Beelink Mini S12 Pro Mini PC (Intel N100, 16GB, 500GB SSD)

Check price on Amazon

The server box pick: a low-power quad-core mini PC running a full Linux distribution, several dedicated game servers, and the group’s file share. Solid-state storage keeps transfers quick when the whole room connects at once.

Specs:
– Processor: Intel N100, 4 cores, up to 3.4 GHz
– Memory: 16 GB DDR4
– Storage: 500 GB M.2 SSD
– Display: dual HDMI, up to 4K at 60 Hz
– Networking: Wi-Fi 6, Bluetooth 5.2, RJ45 Ethernet

Synology DiskStation DS224+ 2-Bay NAS

Synology DiskStation DS224+ 2-Bay NAS

Synology DiskStation DS224+ 2-Bay NAS

Check price on Amazon

The alternative server box for hosts who also want shared storage in the same unit. Its x86 processor serves files to the room and runs containerised services such as a game cache.

Specs:
– Processor: Intel Celeron J4125, quad-core, up to 2.7 GHz burst
– Memory: 2 GB DDR4, expandable to 6 GB
– Bays: 2, for 3.5-inch or 2.5-inch drives, sold diskless
– Networking: 2 gigabit RJ45 ports
– Software: Synology DSM with container support

FAQ

Do Linux and Windows PCs really play together on the same LAN server?
Yes. A dedicated server does not care which operating system its clients run, and a Proton client speaks the same network protocol as the Windows build. Match game versions across the room and the mixed setup is invisible in play.

Can we run the whole party with no internet connection at all?
Mostly. Steam needs periodic sign-in, and some games authenticate online before opening their LAN modes, so plan for a light internet presence for logins. Installs, updates, and the matches themselves can all stay local.

Is Wi-Fi good enough if cables are impractical?
For a few players in online games it can be, but it removes every advantage here: local transfers slow down, discovery gets unreliable, and latency varies seat by seat. If anyone can be wired, wire the server box first.

What should the host prepare the night before?
Update and verify every listed game on one master machine, install and test-join each dedicated server, print the address plan, and lay the cables out once to measure the runs. An hour of prep buys an evening with no setup.

Final verdict

A Linux LAN party succeeds on logistics, not hardware heroics: one unmanaged gigabit switch, a written address plan, one small Linux box serving games and files, and a list chosen for real LAN modes instead of box art. Steam’s local transfers have removed the download bottleneck, and Proton means the mixed room needs no special pleading. Wire it once, test it the night before, and the technology disappears.

Explore Our Guides & Free Tools