Show HN: I built a(nother) house optimized for LAN parties

Original Article ↗ Hacker News Discussion ↗

Netboot architecture & management

  • Many commenters admire the iSCSI netboot + copy-on-write design, especially the “maintain one image, clone instantly to 20 PCs” aspect.
  • Alternatives proposed:
    • PXE + Clonezilla / multicast imaging before parties; seen as simpler by some but slower and more bandwidth-heavy.
    • Local SSDs with occasional reimaging and relying on Steam’s LAN update sharing.
    • Commercial/“LAN center” stacks like CCBoot, GGRock, ZFS snapshotting; some operators prefer homebrew ZFS.
  • Concern over stability: onboard Marvell/Aquantia 10G NICs are widely reported as flaky; multiple people recommend used Intel x520/x540 SFP+/10GBase‑T cards from eBay.

OS, streaming, and virtualization

  • Current setup: Linux server, Windows clients; several suggest moving clients to Linux now that Proton/Steam support has improved, to avoid brittle Windows iSCSI boot issues and enable server-side CoW on local disks.
  • Others report success with GPU‑passthrough gaming VMs and multiseat setups, but note anti‑cheat issues, PCIe lane limits, and complexity.
  • Cloud game streaming (e.g., Stadia, GeForce Now) is debated:
    • One user reports GeForce Now in Austin feels almost local.
    • The builder’s test of Stadia felt subtly “wrong” even when latency wasn’t consciously noticeable, making them distrust streaming for LAN play.

Hardware, networking & peripherals

  • 10G network generally praised; some note Windows should handle 10G fine with proper drivers and RSS.
  • Long cable runs are handled with active fiber-based “SlimRun” DP/HDMI/USB cables; commenters confirm similar solutions.
  • Keyboard choice (cheap membrane Logitech K120) triggers debate:
    • Some argue lack of n‑key rollover and feel is bad for fast shooters.
    • Others say typical WASD+Shift+Ctrl combos are fine and guests can bring their own peripherals.
  • No headsets: deliberate choice so people talk in person; some suggest open‑back/bone‑conduction as a compromise.

Cost, wealth, and housing

  • LAN cabinetry + hardware quoted at ~USD 150k; house is “7‑digit”.
  • Reactions split:
    • Many celebrate the project as a fun, social use of money and a marginal driver of new housing and local labor.
    • Others see it as conspicuous consumption in a housing crisis and tie it to broader inequality, suggesting higher taxes or structural reform.
  • A long subthread debates:
    • Zoning and permitting vs. crime/financialization as drivers of housing costs.
    • Role of tax policy (including wealth vs. income taxes, treatment of “unearned” investment income).
    • Leverage in homeownership and how primary residences function as retirement assets.

Austin vs Bay Area and quality of life

  • Builder describes Austin as similar to Bay Area but more relaxed: shorter distances, no wildfire smoke, more varied weather, visible ongoing construction, and falling prices due to building.
  • Counterpoints:
    • Some argue Bay Area’s natural environment is vastly superior; Texas is framed as sprawl, heat, and car dependency.
    • Others note good cycling routes near Austin and say practical experience varies by neighborhood and lifestyle.

LAN culture & social aspect

  • Strong nostalgia for ’90s/2000s LANs: BNC terminators, IPX/SPX, manual IP allocation, Peg‑DHCP, driver hell.
  • Opinions differ on what “counts” as a LAN party:
    • Some feel it must involve everyone bringing their own rigs and shared troubleshooting.
    • Others see built‑in stations as essential once people have kids and less time, and value “show up and play”.
  • Many highlight that the most impressive part isn’t the tech but maintaining a long‑term friend group willing to travel for annual LANs.

House design, cats, and infrastructure

  • Cat features (catwalks, cat doors, dedicated litter “bathrooms” with fans) receive lots of positive attention; suggestions include VOC sensors and chip‑based monitoring.
  • Continuous exhaust fans may hurt HVAC efficiency; commenters propose timers, heat‑recovery routing, and better shading/films to reduce 10–12kW HVAC draw.
  • Cabinetry cost surprises people; discussion attributes expense mainly to custom design and labor rather than materials.