Moonlight Looks Easy. The Network Isn't

Remote Gaming Was Always the Goal.

THE BACKSTORY

Before Moonlight, I was a GeForce Now user. Cloud gaming on someone else's hardware was simple, with no setup or maintenance. You just connect and play. It worked, until it didn’t. GeForce Now isn’t available in Bonaire. Plus, with over 20 devices sharing the same network, the latency made it unplayable. So, I stopped paying. 

But the idea never left. Playing from the couch, from bed, or anywhere in the house without moving hardware has been the goal for years. Moonlight is the version of that idea I can control. My hardware, my network, my rules.





Moonlight Looks Easy. The Network Isn't.

WHERE MOST GUIDES STOP

Every Moonlight setup guide covers the same steps: install Sunshine on the host PC, install Moonlight on the client, pair them, and done. However, those guides do not address what happens when your network pushes back. 

This is the part that nobody documents: the actual issues I faced while setting up Moonlight across a property with 20 to 24 active network clients, multiple access points, and no direct access to the ISP router.

Problem #1: The Client Couldn't See the Host.

ACCESS POINTS IN THE WRONG MODE

My property has multiple WiFi access points covering the house, offices, and store — roughly 100 meters of coverage total. The APs were running in standard router mode, which means each one was creating its own network segment. My bedroom client and my office PC were on different subnets.

Moonlight requires both devices to be on the same network segment. If they're not, the client simply won't see the host — no error, no explanation, just nothing.

The fix: bridge mode on all access points. Each AP needed to be configured to pass traffic through to the main network rather than create its own. Once all devices were on the same segment, Moonlight could find the host immediately.

When configuring bridge mode, match the AP settings as closely as possible to the ISP router configuration. This keeps the network stable and reduces the chance of conflicts when clients move between access points.

Problem #2: The PC's IP Kept Changing.

DYNAMIC IP IN A 24-CLIENT NETWORK

This network has 20–24 active clients at any given time — TVs, phones, tablets, and PCs across the whole property. In that environment, a dynamic IP isn't just inconvenient. It breaks everything that depends on finding your machine by address.

Every time the PC's IP changed, Moonlight lost the connection. The client had the old address cached and couldn't find the host. Wake-on-LAN stopped working. MacroDeck lost the server. Everything that depended on knowing where the PC was on the network broke simultaneously.

That screenshot shows exactly what happens: three entries for the same machine. One with the current IP, two with old hostnames that no longer resolve. Every time the IP changed, I had to manually update every app that depended on it.

The fix: a static IP. When I had OPNsense running, I used DHCP static mapping — the router always assigned the same IP to the PC's MAC address. That was the cleanest solution. When OPNsense went down, I switched to a manual IPv4 assignment directly in Windows network adapter settings. Less elegant, but reliable.

The key when setting a static IP in Windows: make sure you're using an address outside the DHCP range of your router, and on the same subnet. Getting this wrong will drop your connection mid-configuration — which I learned the hard way.

Problem #3: 2.4GHz Is Not an Option.

WIFI BAND MATTERS MORE THAN YOU THINK

Once the network was stable and the IP was fixed, I still had latency issues when streaming from certain spots in the house. The problem was the WiFi band.

2.4GHz has more range but significantly less bandwidth. For Moonlight — which is streaming full HD or 4K video in real time — 2.4GHz isn't enough. You'll get stuttering, artifacting, and input lag that makes gaming impossible.

5GHz only for Moonlight. Make sure your client device is connected to the 5GHz band before opening Moonlight. On a crowded network with 20+ clients, 2.4GHz is already congested. 5GHz gives you the bandwidth you need for smooth streaming.

My setup: the bedroom AP broadcasts both bands with the same SSID. I manually force the tablet and phone to connect to 5GHz when using Moonlight. The difference is immediate — smooth streaming vs. constant stuttering.

What OPNsense Changed.

THE IDEAL SETUP

When I had OPNsense running on a dedicated Intel NUC, everything was more stable. DHCP static mappings meant the PC always had the same IP without touching Windows settings. Firewall rules gave me visibility into what was happening on the network. Everything connected cleanly.

OPNsense went down when the NUC burned out — a separate story for a separate post. I'm planning to bring it back online on new hardware. When that happens, Moonlight will get even more stable because I'll have proper network control again.

For now, the manual Windows static IP and bridge mode APs get the job done. Not elegant, but solid.

The Setup That Works.

CURRENT CONFIGURATION

Current working configuration:

  • Host PC: Static IP assigned manually in Windows IPv4 settings
  • Sunshine: Running on the host PC, accessible via the static IP
  • Access points: All configured in bridge mode — same network segment
  • Client devices: Connected to 5GHz band only when using Moonlight
  • Wake-on-LAN: Enabled in BIOS + Windows — PC wakes remotely in seconds

From the bedroom, living room, front porch, or anywhere on the property — connect, wake the PC, stream. It works because each piece of the network is configured to support it.

What's Coming.

ROADMAP

  • Bringing OPNsense back online — proper DHCP control, firewall rules, full network visibility
  • NAS for automatic backup of every device on the property
  • More detailed guide on bridge mode configuration for the specific routers I'm using

Beyond the Setup. Building Spaces.

WHAT THIS MAKES POSSIBLE

The technical setup is only part of it. Once Moonlight works reliably, you start thinking differently about your living space. I'm not locked to one desk anymore — and that opens up possibilities.

I'm actively looking at ways to add gaming zones around the house. A foldable desk in the bedroom is already on the list. The goal isn't to fill every room with hardware — it's the opposite. One powerful machine, zero extra hardware, and the freedom to play wherever makes sense at that moment.

That's what remote streaming actually gives you. Not just convenience. A different relationship with your space.

If you're setting up Moonlight and it's not working, the problem is almost always the network — not the software. Start with bridge mode, fix the IP, switch to 5GHz. In that order.

Questions about the network setup? Drop them below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.

NETWORK GEAR

Comments

Post a Comment

Popular posts from this blog

From Fear to Control: What Self-Hosting Gave Me

Image
From Fear to Control: What Self-Hosting Gave Me A DIFFERENT KIND OF POST I'll confess something. When I first started experimenting with self-hosted services, it wasn't because I wanted a cool homelab. It wasn't because I wanted to play with Docker, firewalls, VLANs, or enterprise-grade networking. It started from something much simpler. Need. And fear. I had old equipment sitting around collecting dust. Hardware that technically still worked, but had no purpose anymore. At the same time, I felt an increasing need for something I couldn't fully get from consumer-grade solutions: control. I wanted more security. I wanted more visibility. Most importantly, I wanted to better protect my children. That was the real beginning. Like many parents, I tried the usual tools first. I explored what Google Family Link offered. I tried the parental controls built into Microsoft Windows Family Safety. I tested schedules, device restrictions, app limits, and whatever...
Read more

When One Problem Turns Into Two

Image
When One Problem Turns Into Two The calm before... This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product mentioned here is something I personally own and use. I'd enjoyed almost a month of absolute peace. My OPNsense firewall was working flawlessly, without a single outage. It was performing so well that, to be honest, I'd fallen into that dangerous state of complacency where you don't even check the logs or the connection. You simply assume everything will be fine forever. Until this morning. At 7:01 AM, I sat down at my computer ready to start the workday and was met with the worst possible screen: No connection. At first, nothing made sense. The infrastructure had been stable for weeks. The OptiPlex running OPNsense was powered on. The NUC was powered on. Physical links? At first glance, all good. Ever...
Read more

Google Photos Was Free. Until It Wasn't. Here's My Setup Now.

I Trusted Google With Ten Years of Memories. Then the Rules Changed. The problem... The problem... Photography has always been one of my favorite hobbies. Not professionally — I never went that route. But personally, I've taken photos of everything that matters to me: family moments, projects, travel, random memories, everyday life. Back in 2015, I discovered Google Photos. Honestly, it felt revolutionary. Before that, managing photos was a mess — my phone constantly filled up, I had to manually copy everything to external hard drives, and I ended up with four or five different drives scattered everywhere. Finding a specific photo from years ago meant remembering which drive had it, connecting it, and hoping I'd organized things correctly. Google Photos changed all of that. Every photo available instantly from anywhere. Search by face, color, event, date, location, objects inside the image. If I wanted photos of my wife, I could simply search for her face. At the time, it felt ...
Read more