Everything Wants a Second Life

Nothing has only one use until you decide it does.

If I Can't See It, I Don't Understand It

Nothing has only one use until you decide it does.

If I Have to Do It Twice, I Build a System

Nothing has only one use until you decide it does.

Think Inside the Box

Nothing has only one use until you decide it does.

Embrace the Mistake

Nothing has only one use until you decide it does.

Thursday, April 30, 2026

My Network Has No Firewall Right Now. Here's Why That's Temporary.

  April 30, 2026  , ,   No comments

1,250 Square Meters. 30+ Devices. No Logic.

WHERE IT STARTED

The property has around 1,250 square meters — house, offices, storage, and a store. At any given time there are 20+ active devices on the network. On busy days that number climbs to 30. TVs, phones, tablets, PCs, POS systems, security cameras, and everything in between.

The original setup was a collection of repeaters with no logic behind them. Each one doing its own thing, creating its own network, fighting with everything else. The result: devices losing connection constantly, having to manually switch WiFi every time you moved across the property, IP conflicts between wired and wireless devices, and zero visibility into what was actually happening on the network.

This wasn't a simple home network anymore. It hadn't been for a long time. It needed a proper solution.

The Decision: Skip the Easy Option.

WHY OPNSENSE

The ISP router does what ISP routers do — basic connectivity, no real control. For a network this size with this many different types of devices and use cases, that wasn't enough. I needed something more robust.

I chose OPNsense. And I'll be honest — it's more complex than it looks. The learning curve is real. But what it gave me in return was worth every hour spent figuring it out.

What OPNsense Actually Did.

THE SETUP

The first step was identifying every device on the network. Every single one. Then assigning DHCP static mapping — each device gets the same IP every time, no exceptions. That alone solved half the problems.

Then came the rules:

  • Safer DNS — blocked adult content at the network level, for every device
  • Kids schedule — no internet after 9:30pm, automatically, no arguments
  • Employee limits — messaging works, voice calls don't. This one was a delight.
  • Guest bandwidth — visitors get connection, but not comfortable connection
  • Moonlight priority — clean, uninterrupted path for game streaming
  • Office file sharing — local network visibility between the right machines
  • Odoo access — business software reachable only by the right people

Everything was working exactly as it should. The network was finally under control — device by device, rule by rule. And most importantly: one place to see everything that was connected.

Until It Wasn't.

THE FAILURE

The Intel NUC running OPNsense was a 2014 model. A solid machine for its time — but running 24/7 as a firewall took its toll. It started shutting down every 15 minutes. No warning, no gradual degradation. Just off.

That was the end of OPNsense — at least for now.

As an immediate fix, I handed control back to the ISP router. The APs are still in bridge mode, which solved the roaming problem. But everything else fell apart — IP management, rules, filters, visibility. All gone.

And that last one — visibility — is what I feel most right now. Look at what I'm working with:


Each AP sees only the devices connected to it. The Tenda shows its 4. The TP-Link shows its clients. Nobody sees the full picture. There's no single place where I can look and know exactly what's on my network — who's connected, what IP they have, how much bandwidth they're using. That visibility is gone.

With OPNsense, I had one dashboard. Every device. Every IP. Every connection. Now I have three separate AP panels that each tell part of the story — and no way to see the whole thing at once.

The part that bothers me most isn't just the technical side — it's the practical impact on the people using the network every day.

My kids now have unrestricted access to content that wasn't appropriate before. The 9:30pm cutoff is gone. There's no schedule, no filter, no DNS blocking adult content at the network level. That's not a minor inconvenience — that's something I want fixed as a priority.

The employees have full internet access during work hours. They can connect to anything, stream anything, use bandwidth freely while they're supposed to be working. It's not that I want to block them completely — it's that I want to make entertainment uncomfortable enough that work stays the priority. Right now that control doesn't exist.

Going from full network control to no network control is a specific kind of frustration. Especially when you know exactly what you're missing — and exactly who it's affecting.

This Isn't About Control. It's About Peace of Mind.

THE REAL REASON

I don't want to sound like someone who controls everything. That's not the point. The point is that having clear rules in place gives you peace — and removes daily decisions that shouldn't need to be made manually every day.

Right now one of my kids' devices has no internet connection at all. That was the safest option available to me without the firewall. It's not elegant. It's not the solution I want. It's what I have until OPNsense comes back online.

Another one of my kids is starting secondary school. That means a school-assigned laptop coming into the house — locked down by the school, but with limited filtering. The school controls what they can control. What happens on my network is my responsibility. I need to be able to create real controls before that device arrives, not after.

When I get ISP bridge mode, I'm also changing the SSID to something different and hidden. No ambiguity about where to connect. One network, known only to the people who should know it.

This kind of setup isn't pretty or elegant. It's only justified while it works. But the alternative is spending thousands of dollars on managed network equipment controlled by someone else — or handing your network over to a cloud service that makes the rules for you. That level of control is exactly what I'm not willing to give up.

The Plan to Bring It Back.

WHAT'S NEXT

The NUC isn't dead yet. The next step is replacing the thermal paste — 10-year-old paste on a machine that ran 24/7 is a likely culprit. I'm planning a stress test after the repaste to see if the hardware is salvageable. If it is, it goes back into service. If it isn't, it gets replaced.

The longer term plan: move OPNsense to the Optiplex 780 — more thermal headroom, more reliable hardware for continuous operation. The ISP has already confirmed they'll switch to bridge mode on their end when I'm ready. When that happens, OPNsense sits between the ISP modem and everything else, running the whole property the way it should be run.

  • Thermal paste replacement + stress test on the NUC — upcoming post
  • OPNsense back online on the Optiplex 780 — upcoming post
  • ISP bridge mode — full network control returns
  • Rules back in place — kids schedule, employee limits, Moonlight priority, everything
  • One dashboard. Every device. Full visibility.

The firewall is coming back. It's just temporary.

Questions about the setup or OPNsense? 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.

RELATED POSTS

  • 100 Meters. One Network. How I Built a DIY Mesh With What I Had — Post #005
  • Moonlight Looks Easy. The Network Isn't. — Post #003
Read More

Three Audio Devices. Three Jobs. No RGB.

  April 30, 2026  ,   No comments

 

The Laptop Had Speakers. The Desktop Didn't.

WHERE IT STARTED

When I was on the Lenovo Legion, audio was solved. Built-in speakers, done. But my daily work includes construction sites — loud environments where you need to hear clearly, protect your hearing, and still be reachable. International work trips added to that. I needed something for the street, for the plane, for the noise.

That's when I bought the TOZO Crystal Pod. And I still have them. Still use them. That purchase was never a mistake — I just kept solving new problems as the setup evolved.


The Crystal Pod Solved the Street. Not the Office.

PROBLEM #1

The Crystal Pod works exactly as intended for outdoor use. Construction sites, travel, loud environments — they isolate well, they're compact, and the battery lasts long enough that running out mid-day isn't a concern.

The problem came when I moved to the desktop and started using them at the desk. The isolation that made them great outside made them impractical inside. I work in a space where people come looking for me constantly. Every visit meant taking them out, pausing everything, having a conversation, putting them back. Multiply that by a full workday and it becomes exhausting.

The Crystal Pod didn't fail. My use case changed. That's a different problem.

Bigger Headphones. Same Problem.

PROBLEM #2

I bought the TOZO HT3 because of the good experience with the Crystal Pod. Same brand, proven quality, and the HT3 has something the pods don't — noise cancelling that works even when connected directly to the PC via cable. That mattered for long work and gaming sessions.

But I fell into the same trap. The HT3 isolates well. Too well for the office. Taking them on and off every time someone walked in became the new version of the same old problem. Better headphones, identical frustration.


The HT3 found its real role: late night gaming sessions from bed. Full isolation, no distraction, completely in my own world. That's exactly what noise cancelling is for.

The Speaker That Replaced Both — For Everything Else.

THE SOLUTION

The Anker Soundcore 2 entered the setup not to replace the headphones — but to handle everything they couldn't. Open office work, calls, audio at the desk without isolation. It sits on the desk like a keychain and goes wherever I go.

What makes it work daily: the Bluetooth source switching is fast. Switching from the PC to the phone mid-task takes seconds. No re-pairing, no waiting. That speed makes it practical in a way that most Bluetooth speakers aren't.

In the car: phone audio via Bluetooth — better than the car speakers.
At the desk: PC audio, calls, YouTube — no headphones needed.
Outside: patio, yard, anywhere — it goes in a pocket.
TV: better audio than the built-in speakers, connected in seconds.

And the battery — the longest of the three. It charges less often than anything else in the setup.


Three Products. Three Jobs. Zero Overlap.

HOW THEY WORK TOGETHER

What took me three purchases to figure out is that each one solves a different context — and none of them tries to do the other's job.

I don't have lab measurements or isolation tests. What I have is real use in real situations — and that's the only test that matters to me.

The Crystal Pod is for when I'm moving. Walking, construction sites, public spaces, travel. Full isolation when the world around me is too loud to ignore. I can't tell you the dB rating. I can tell you it works next to an excavator. One honest limitation: at 2–3 feet from a power tool — angle grinder, drill running at full speed — the noise cancelling hits its limit. That close, the sound is practically at your ear and the pods can't fully compensate. That's not a complaint, that's physics. For anything beyond arm's reach, they handle it fine.

The HT3 lets me disappear completely — gaming in bed at midnight without disturbing anyone. No RGB lighting turning the bedroom into a light show at 2am. Just sound, darkness, and whatever I'm playing. The noise cancelling works wired directly to the PC, which matters more than any spec on the box.

The Soundcore 2 is for when I can make noise. The desk, the car, the park, the beach with the family. It goes everywhere without thinking about it. Fast Bluetooth switching means it moves between the PC and the phone in seconds — no re-pairing, no waiting.




None of them was a mistake. Each one found its role — just not always the role I bought it for.

Who This Is Actually For.

RIGHT TOOL, RIGHT CONTEXT

  • You work in loud environments and need ear protection that also plays audio
  • You work at a desk where people interrupt you constantly — isolation is the enemy
  • You want one speaker that moves between your desk, your car, and your yard without thinking about it
  • You game at night and need to disappear without disturbing anyone

Questions about any of the three? 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.

ON THIS DESK

Read More

Wednesday, April 29, 2026

How I Repurposed My Daughter's Old Tablet Into a Macro Pad

  April 29, 2026  , ,   No comments

 

My Daughter's Tablet Was Collecting Dust.

WHERE IT STARTED

I bought an Amazon Fire 7 Kids tablet in November 2022. It did exactly what it was supposed to do — durable, controlled, something a kid could actually use without destroying. My daughter used it for years. Then she grew up, the tablet got more boring than what she needed, and somewhere along the way it ended up in a drawer, covered in dust, completely dead.

I found it months later and figured it was done. Plugged in a charger anyway. It turned on. Fully functional. I paid $55 for it in 2022. My daughter used it for two years. And now it runs my entire desk.

I Wanted a Macro Pad. I Didn't Want to Buy One Blind.

THE PROBLEM

From November 2025 I'd been researching how to add more ergonomics to my desk setup. The PC came together fully at the end of February. But coming from the Lenovo Legion that burned out, I wanted more control over the functions I use constantly. A macro pad made sense.

The problem: I don't buy things without knowing they'll actually work in my day-to-day. A dedicated macro pad is a commitment — hardware, software, learning curve. If it doesn't fit the workflow, it just becomes another thing on the desk.

Then I found MacroDeck. Open source. No account. No subscription. You install the server on the PC and the client on any Android device. That's it.

Open Source. No Subscription. No Account Required.

THE SOLUTION

MacroDeck caught my attention for one specific reason: open source, no account, no subscription. No cloud dependency, no monthly fee, no login wall. Install the server on the PC, install the client on any Android device, connect. Done.

I decided to use the Fire 7 that was already sitting on my desk. Wiped the Amazon account, disabled everything I could, installed MacroDeck. It connected immediately.

The Network — Again.

THE FIRST PROBLEM

MacroDeck connects to the PC by IP address. Which means if the PC's IP changes, MacroDeck loses the connection. Every time. While OPNsense was running, DHCP static mapping handled this automatically — the PC always had the same IP. When OPNsense went down, the problem came back.

The fix was the same one I used for Moonlight: manual static IP in Windows IPv4 settings. Set it once, leave it. MacroDeck finds the PC instantly every time.

Not Plug and Play. But Close.

THE CONFIGURATION

The install was straightforward. The configuration wasn't always. Some commands and integrations didn't work on the first try — or the second. Getting the buttons to do exactly what I needed required reading, testing, and some trial and error.

What made it worth it: MacroDeck lets you segment commands by application. Different buttons for different contexts — design work, gaming, system controls. The tablet knows what you're doing and shows you the relevant controls.

I added custom icons I designed myself. No default icon packs, no RGB, no unnecessary visual noise. Just a screen that shows exactly what I need, when I need it.

The main screen handles the essentials: direct app launchers for Photoshop, Illustrator, CapCut, and 3DS Max, live GPU and CPU temperature monitoring, a one-tap hibernate button, and volume controls with the current level visible at a glance.

Each application gets its own subfolder with context-specific commands. The Illustrator page covers the operations I repeat constantly — same color selection, stroke weight, case changes, compound release, expand appearance. Things that were buried in menus now have a dedicated button.

The 3DS Max page solves a specific daily frustration: switching units. Millimeters, meters, centimeters, feet, inches — one tap each. No more digging through settings mid-model.

One limitation worth knowing: the main screen dictates the grid size for the entire setup — and every subfolder inherits that same grid. You can't have a 4×3 main screen and a 2×2 subfolder. Everything follows the same layout. I haven't fully settled on my ideal grid yet. Think about your grid size before you start building — changing it later means reorganizing everything.

One Screen. Everything I Touch Daily.

HOW I ACTUALLY USE IT

The commands I use most are mapped and accessible in one tap. App launchers, system shortcuts, temperature monitoring, media controls. Things I was doing with keyboard shortcuts or mouse clicks that now have a dedicated button on a screen I can glance at without moving my hand.

The detail that surprised me most: it works perfectly with Moonlight. When a remote gaming session on the TUOHAITIME tablet ends, I hibernate the PC directly from MacroDeck on the Fire 7. One tap from the desk surface. Done. I don't need to walk to the office or switch to the keyboard.



$0 Extra. One Tablet. One Afternoon.

WHAT IT TOOK

The Fire 7 was already paid for years ago. MacroDeck is free. The only investment was the time to configure it properly — and the patience to fight through the commands that didn't work on the first try.

If you have an old Android tablet collecting dust, this is the best use I've found for one.

What's Next.

THE ROADMAP

  • OPNsense back online — DHCP static mapping returns, MacroDeck gets more stable
  • Expanding the command library as the workflow evolves
  • Custom designed icon pack — full set, consistent style

If you have an old tablet sitting in a drawer, don't sell it. Don't throw it out. Give it a job.

Questions about the setup or the config? 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.

ON THIS DESK

Read More

Thursday, April 23, 2026

1200 Meters. One Network. How I Built a DIY Mesh With What I Had.

  April 23, 2026  , , ,   No comments

This Isn't a Typical Home Network.

WHERE IT STARTED

Most network guides assume you're covering one house. I'm covering a property — house, storage area, offices, and a store spread across roughly 1,250 square meters (13,450 sq ft). Three access points, 20–24 active devices at any given time, and no direct access to the ISP router.

When I set up Moonlight to stream games from my office to my bedroom, I realized fast that the network was going to be the hard part. Not the software. Not the hardware. The network.

Four Networks. Zero Coordination. Complete Chaos.

THE PROBLEM

Before I fixed it, this is what I was working with: the ISP router doing its own thing, and each access point creating its own separate network on top of that. Four different networks on one property.

Every AP wanted to run its own DHCP server. That meant IP conflicts constantly — especially between devices connected by LAN in the office and devices on whatever subnet the nearest AP decided to assign. Moving around the property meant manually switching networks on your phone or tablet, or restarting WiFi and hoping it connected to the right one. The office equipment connected by ethernet would fight with wireless devices on overlapping IP ranges. It was a mess that got worse the more devices were on the property.

The real breaking point: I had OPNsense running on a dedicated Intel NUC in phase one. DHCP static mapping, full network visibility, everything controlled properly. Then the NUC burned out — literally. I lost OPNsense and had to rebuild the entire network from scratch, manually, without the firewall layer I'd been relying on.

Three APs. What I Had. Nothing New.

THE HARDWARE

I don't buy new when I can reuse. The backbone is a Linksys 8-port switch connected directly to the ISP router — everything on the property flows through that. From the switch, three access points cover the full property:

  • TP-Link Archer C3200 — house coverage. Tri-band: 2.4GHz + 5GHz + 5GHz. Channel 1. Handles the heaviest load.
  • Tenda 11N — center coverage. 2.4GHz only. Channel 6. Covers the middle zone between house and offices.
  • Linksys 2101 — office and storage coverage. 2.4GHz + 5GHz. Channel 11.

All three broadcasting the same SSID: TC_main. Same password. Different channels — 1, 6, and 11 — the three non-overlapping channels on 2.4GHz. No interference between them.




[FOTO: TP-Link AC3200]

[FOTO: Linksys 2101]

Bridge Mode. Same SSID. No Conflicting Channels.

THE FIX

The solution came from reading a lot about WiFi spectrum and how APs interact. Three things had to happen simultaneously.

1. Bridge mode on every AP.
Each AP had to stop acting like a router and start acting like an extension of the main network. In bridge mode, they pass traffic through to the ISP router instead of creating their own subnet. One DHCP server. One IP range. No conflicts.

2. Same SSID, different channels.
Three APs can broadcast the same network name without fighting each other — as long as they're not on the same channel. Channels 1, 6, and 11 are the three non-overlapping channels on 2.4GHz. Each AP gets one. No interference, no competition.

3. Physical relocation.
Part of the problem was placement. I remapped the whole property and physically moved each AP to cover its zone without overlapping aggressively with the others. Two of the three APs weren't physically accessible — that meant ladders, finding them in the walls, pulling them out, reconfiguring, and reinstalling. Not glamorous work.

The transition also required a parallel setup — I added the new unified network manually to every device on the property before switching, so nobody noticed the change when it went live.

What Roaming Actually Looks Like in Real Life.

THE PROOF

This is what the roaming looks like captured live with WiFiman while walking the property. No manual switching. No restarting WiFi. The device finds the strongest AP automatically.





What you're seeing in the screenshots: the phone connected to the TP-Link at -49 dBm, then switching automatically to the Tenda at -55 dBm as I moved across the property. Same network. No manual switching. The AP Roaming event is visible right there in the graph.





Not Perfect. Functional.

CURRENT LIMITATIONS

This setup works — but I won't pretend it's flawless. Some devices occasionally lose internet connectivity. The culprit isn't the mesh — it's the ISP. When the ISP drops coverage or runs out of available IPs, devices on 2.4GHz get stuck. The fix is simple: switch to 5GHz and the connection comes back immediately.

Some devices don't switch APs aggressively enough on 2.4GHz. They'll hold onto a weaker signal longer than they should before roaming. It's a known limitation of how WiFi roaming works without a proper controller — each device decides when to switch, not the network.

For Moonlight specifically: 5GHz only. The Tenda 11N is 2.4GHz only — so Moonlight runs through the TP-Link AC3200 or the Linksys 2101, both of which have 5GHz. On a 20+ device network, 2.4GHz is too congested for game streaming. 5GHz is what makes it smooth.

The Ideal Setup I Had and Lost.

WHAT OPNSENSE CHANGED — AND WHY IT'S COMING BACK

When OPNsense was running, everything was cleaner. DHCP static mapping meant every device always had the same IP — the PC, the NAS, everything. Firewall rules gave full visibility into what was happening on the network. Moonlight was more stable because the host PC's address never changed.

The NUC burned out and took that layer with it. Right now I'm running manual static IP on the PC through Windows IPv4 settings — not elegant, but it works. The ISP confirmed they'll switch to bridge mode on their end once I'm ready, which means OPNsense will eventually sit between the ISP modem and everything else, running the whole property properly.

When OPNsense comes back online, the ISP handoff problem goes away. Proper DHCP control, static mappings for every device, firewall visibility. That's the next phase — and it'll get its own post.

What's Next.

THE ROADMAP

  • OPNsense back online on new hardware — proper DHCP control and firewall rules
  • ISP switching to bridge mode — full network control under OPNsense
  • NAS for automatic backup across the whole property
  • Detailed bridge mode guide for each specific router used here

If your network problem is that you have too much property to cover with one router, the answer isn't buying a $400 mesh system. It's understanding why your current APs are fighting each other — and making them stop.

Questions about the 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

Read More

I Didn't Need a Gaming Mouse. Then I Did.

  April 23, 2026  , ,   No comments

The Keyboard Broke. That's How This Started.

WHERE IT STARTED

My Lenovo Legion's GPU connection burned out. Not worth the repair. I stripped the drives and moved on — but I still needed a keyboard and mouse while building the new desktop, and I wasn't in the mood to manage cables on top of everything else.

The Logitech MK270 wireless combo made sense. Fast, affordable, no extra dongle mess. I used it for about a year. It did exactly what it was supposed to do — until it didn't.




After a Year, the Keyboard Started Fighting Back.

WHAT BROKE THE DEAL

It wasn't sudden. Shift started requiring more force than it should. Then Enter. Then Space. Keys that should register on a light press started needing deliberate pressure — the kind where you notice you're pressing instead of just typing. I don't know if it was dust, wear, or just the cost of a budget keyboard. But it was consistent, and it was spreading.

The mouse was a different issue. The MK270 mouse works — but it's not built for precision. When your daily work includes 3D modeling in 3DS Max and you're gaming on the same machine, you start feeling the gap between a mouse that tolerates you and one that responds to you.

The MK270 didn't go in the trash. It now runs the bedroom Moonlight setup — wireless keyboard and mouse for streaming from bed. Right tool, right place.

$35.99. One Mouse. No Regrets.

THE UPGRADE

I picked up the Logitech G502 Hero for $35.99 on Amazon. At that price point I wasn't expecting a revelation. What I got was a mouse I spent one full day configuring in G HUB — and haven't touched the settings since.





  • Logitech G502 Hero — Hero 25K sensor · 25,600 DPI · 11 buttons · adjustable weights

11 Buttons. I Use 3. Here's Why That's Not a Problem.

MY ACTUAL CONFIGURATION

The G502 Hero has 11 programmable buttons. Every review is excited about macros, DPI cycling, and the sniper button. I stripped all of that out.

The two side buttons pre-mapped to Forward and Back? With big hands, I was triggering them constantly by accident mid-session. Disabled. The DPI cycle buttons? Gone — I set one value and left it there. Profile cycling? Removed. Weights? Out of the mouse entirely, running it as light as possible.





Active buttons: Primary click · Secondary click · Scroll wheel (stepped)
Conditional: Forward + Back — only in specific games when useful
Everything else: disabled or removed
One DPI profile: 2000. Report rate: 1000Hz. That's the entire config.


The Thing Nobody Mentions in Reviews.

ONE RGB ZONE. THAT'S IT.

I work long hours at this desk — design, rendering, gaming, all on the same machine. The last thing I want is a peripheral competing for my attention. Most gaming mice default to a full RGB rainbow cycle, and half the reviews treat that as a selling point.

The G502 Hero has one RGB zone: the G logo. I set it to a fixed color and left it. It doesn't pulse. It doesn't cycle. It doesn't react to anything. It just confirms the mouse is on.

My desk doesn't glow. There's no light show competing for attention while I work or play. The G logo is there. That's it. That matters more than I expected — and it's the detail I'd miss most if I switched.

One Day to Configure. Won't Change It.

THE VERDICT

The G502 Hero is the right mouse for a specific kind of person. If you work and game on the same machine — long sessions, precision matters, same desk for everything — you need a mouse that moves with you through both without switching.

What I like about it isn't the spec sheet. It's that once you strip it down to what you actually use, it disappears. It's comfortable with big hands. It's precise enough for 3D design work and responsive enough for gaming. And it doesn't light up your desk like a Christmas tree.

Not for everyone. If you're doing light office work and won't use the programmable buttons or precision sensor, the MK270 mouse does the job for less. But if your setup is anything like mine, $35.99 is one of the better purchases on this desk.

Who This Is Actually For.

RIGHT TOOL, RIGHT PERSON

  • You work and game on the same machine and need one mouse that handles both
  • You have large hands and most mice feel cramped after an hour
  • You want real DPI control without paying $100+
  • You don't want RGB competing for your attention all day
  • You're willing to spend a day configuring to get a setup that lasts years

Questions about the setup or the config? 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.

ON THIS DESK

Read More

Tuesday, April 21, 2026

Moonlight Looks Easy. The Network Isn't

  April 21, 2026  , , ,   No comments

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

Read More

Gaming in the Caribbean: What I Learned About CPU Temperature the Hard Way

  April 21, 2026  , , , , , , , ,   No comments

The GPU Upgrade That Didn't Feel Like One.

WHERE IT STARTED

I had a Lenovo Legion 5 Pro for three years. RTX 3060, solid machine, handled everything I threw at it — 3D rendering, design work, gaming. Then the GPU connection burned out. Not worth microssoldering, not worth the repair cost. I stripped the NVMe drives and moved on.

What I had left was an old i5 with 16GB RAM and a GTX 1070. Not ideal, but functional. That became my workstation while I bought parts piece by piece to build something proper.

First purchase: an RTX 5060. That's where the problems started.

A New GPU in an Old Machine. Big Mistake.

THE FIRST PROBLEM

I installed the RTX 5060 in the old i5 build expecting a performance jump. What I got instead was FPS dropping to the floor the moment I opened any game. The GPU wasn't the bottleneck. The CPU was — and the thermal paste on that old i5 was completely dry.

A $7 thermal paste swap from a local store dropped temperatures enough that I could actually play. Not great — but playable. That $7 fix bought me time while I finished the build.

Lesson learned early: thermal paste dries out. If you're dropping a new GPU into an old system and performance doesn't match expectations, check the CPU temps before blaming the hardware.

The Proper Build. Same Problem.

THE SECOND PROBLEM

Eventually I had all the parts. Intel Core i7-14700F, ASUS B760M-AYW, 32GB DDR4 RAM repurposed from the old build, the RTX 5060, and 6.4TB of storage across four drives. A proper machine.

I fired it up. Opened a game. FPS dropped to the floor again.

The i7 comes with a stock cooler. It works — technically. Under normal office loads it's fine. But the moment I pushed it — gaming, rendering, anything sustained — temperatures spiked to nearly 100°C. The CPU was throttling itself to avoid damage, pulling performance down to stay alive.

I live in Bonaire. Ambient temperature sits between 30–32°C year-round, with humidity around 80%. The office has no AC at night. The stock cooler was never going to be enough in these conditions.

And there was another problem I hadn't fully considered yet: I wanted to use Moonlight to stream games remotely from my bedroom. When you stream remotely, the PC runs under full load even when you're not in the room. With the stock cooler and no AC, that wasn't sustainable. Sessions would degrade, temperatures would spike, and performance would drop mid-game.

The Fix. One Component. Real Numbers.

THE THERMALRIGHT PEERLESS ASSASSIN 120 SE




The Thermalright Peerless Assassin 120 SE. Dual 120mm fans, six heat pipes, and a price point that makes it one of the most recommended air coolers available. I installed it and ran real tests — GPU-Z open, Moonlight streaming from the bedroom, playing demanding titles for full sessions.

Here's what I measured:

GPU-Z Playing with AC on 



GPU-Z Playing without AC on 



GPU-Z Just closing the game: 



GPU-Z Playing without AC at 3pm: 



Stock cooler under load: ~99°C. Throttling.
After $7 paste swap: ~80–85°C. Playable.
Thermalright PA 120 SE, AC on, gaming: 60.4°C GPU.
Thermalright PA 120 SE, AC off, office closed, 30°C ambient: 64.4°C GPU · 56°C CPU.
Close the game — back to 41.5°C in under a minute.

That last number matters. The cooler doesn't just manage heat under load — it dissipates it fast. The delta between AC on and AC off is less than 4 degrees under full gaming load. In a Caribbean climate with no AC running, that's the difference between a system that throttles and one that doesn't.

Why This Matters for Remote Streaming.

THE MOONLIGHT CONNECTION

Most cooler reviews test on a desk, in a controlled room, with AC running. That's not my situation and probably not yours either.

When I configured Moonlight to stream from my office to my bedroom — about 100 meters away — temperature management became critical. The PC runs at full load whether I'm sitting in front of it or streaming from bed. If the cooler can't handle sustained load in a hot, closed room, Moonlight becomes unusable.

With the Thermalright, it's not just usable — it's reliable. Two hours of God of War at 3pm on a Saturday, ambient temperature around 31°C, GPU sitting at 48.1°C between sessions. Fans at 36%, nearly silent.

I also do 3D rendering — full apartment interiors for clients. The i7-14700F's 20 cores handle complex scenes without issue, and the cooler keeps temperatures in check during long render sessions. It's not just a gaming cooler — it's what makes the whole workflow sustainable.

One More Thing: Dust.

BONAIRE REALITY

Living in a tropical island environment means dust accumulates fast. I run a cleaning routine every 3–4 weeks to keep temperatures controlled. Dust is one of the fastest ways to undo good thermal management — it insulates heat and reduces airflow.

If you're in a similar climate, build the cleaning routine into your maintenance schedule. It's not optional — it's part of the system.

What's Next on Temperature.

THE ROADMAP

The Thermalright solved the immediate problem. But I'm not done. Future plans include adding more case fans for better airflow and potentially a solar-powered mini AC unit to drop ambient temperature in the office by a few degrees. Water cooling is also on the table for a future build iteration.

When those happen, I'll document them here with real data — before and after numbers, not marketing claims.

  • Bringing OPNsense back online — covered in an upcoming post
  • More fans + ambient temperature control — future post
  • Water cooling — future build post

Temperature management isn't glamorous. Nobody talks about it until something throttles or burns out. But if you're building a system for sustained work and gaming — especially in a hot climate — it's the investment that makes everything else work.

Questions about the build or the cooling 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.

THE FULL BUILD











Read More

Friday, April 17, 2026

How I Game and Work From Bed Using One PC — No Extra Hardware Needed

  April 17, 2026  , , , , , , ,   No comments

Same Desk. Same Machine. Not Enough Freedom.

THE PROBLEM

I work at a desk. My gaming setup IS my work setup — same machine, same room. An i7-14700F paired with an RTX 5060, built for 3D design, rendering, and gaming. But long work sessions have a cost: when the day is done, the last thing I want is to walk back into the office just to play or fix something quick.

My office and bedroom are close to each other. But close isn't the same as there. Some nights my wife is watching her shows. Some mornings I'm up before 6am and don't want to wake anyone. The office felt like the only option — and that got old fast.

The solution wasn't buying a second PC. It was building the right system around the one I already had — so I can use it from anywhere in my home without moving a single cable.

Here's exactly what I built, what I use, and how it works. If your situation is anything like mine — one powerful machine, multiple spaces, shared living — this might work for you too.

Where Everything Runs

THE OFFICE SETUP






This is the machine. An Intel Core i7-14700F with 20 cores handles design work, 3D rendering, and game streaming simultaneously — without breaking a sweat. Paired with an RTX 5060, it's built to handle whatever I throw at it, including running remotely while I'm in another room.


The build:

65°C. Office Closed. AC Off.

THE COOLER — THE PART NOBODY TALKS ABOUT

Thermalright Peerless Assassin 120 SE installed
GPU-Z gaming with AC on — 60.4°C

Gaming with AC on — GPU: 60.4°C

GPU-Z gaming without AC — 64.4°C

Gaming without AC — GPU: 64.4°C · CPU: 56°C

GPU-Z after gaming without AC — 41.5°C

After closing game — GPU back to 41.5°C in under a minute

Here's what nobody talks about: when you stream your PC remotely, it runs under full load even when you're not in the room. My office has no AC at night. With the stock cooler the i7 came with, remote sessions in a closed office pushed temperatures to the point where performance dropped noticeably.

That's when I invested in the Thermalright Peerless Assassin 120 SE. I ran the numbers properly — GPU-Z open, Moonlight streaming from the bedroom, playing Borderlands 4 for a full session. Here's what I got:

Gaming with AC on: 60.4°C GPU. Gaming with AC off, office closed: 64.4°C GPU, 56°C CPU. A difference of less than 4 degrees under full load. Close the game — back to 41.5°C in under a minute. That's not a spec sheet. That's GPU-Z running live.

If you're building a remote streaming setup, the cooler isn't optional — it's the investment that makes everything else work.

A DIY Mesh. Built From What I Had.

THE NETWORK


My office and bedroom aren't in the same building. There's roughly 100 meters between them — house, storage, offices, and a store in between. This isn't a typical home network. It's a small campus.

I don't buy new when I can reuse. The backbone is a Linksys 8-port switch connected to the ISP, feeding the whole property. From there, routers at key points cover every space — a TP-Link AC3200 in the house and a Linksys node in the office storage area. Same network name, different channels, seamless handoff as I move around.

The result: I can connect from the bedroom, the living room, the front porch, or my phone anywhere on the property. Same PC, zero friction. The PC connects directly via the onboard Ethernet on the ASUS B760M-AYW — no adapters needed. That wired connection is what keeps Moonlight latency consistent across 100 meters of property.

Same Room. Different Worlds.

THE BEDROOM SETUP

Bed gaming setup with Moonlight — Borderlands 4


This is the other end of the system. A bed desk, the Logitech MK270 wireless combo, and a TUOHAITIME Android tablet running Moonlight. I wake the PC with Wake-on-LAN, connect in about 10 seconds, and I'm in.

My wife watches her shows. I play Borderlands 4. Same room, same bed, no conflict. We're each doing what we want — and still in the same space. That matters more than any spec on this list.

Early mornings work the same way. I'm usually up before 6am. Instead of either staying in bed doom-scrolling or going to the office, I pick up the tablet, connect, and play from the living room couch. Nobody's sleep gets interrupted. I get my time. It's a small thing that genuinely changes the quality of the day.

Everything at the Desk

THE OFFICE PERIPHERALS

Logitech G502 Hero — Creatively Different Builds

At the desk I use the Logitech G502 Hero. Big hands — I had to disable the two side buttons on the left because I kept pressing them accidentally mid-session. No extra weights installed, running it as light as possible. Scroll wheel in stepped mode. Only the G logo lights up.

That last part matters more than it sounds. It doesn't compete for your attention. It just works. I wouldn't recommend it for light office use if you're not going to use the extra buttons — but for design work and gaming on the same machine, it's the right tool.

The rest of the desk runs lean. A Fire 7 tablet — my daughter's old one, repurposed — now runs MacroDeck as a secondary control surface. Temperature monitoring, macro shortcuts, app launchers. All on a screen that was collecting dust.

Audio runs through an Anker Soundcore 2. No cables, decent sound, doubles as a speakerphone for calls directly on the PC. When I need isolation — or when my wife is working in the same office — I switch to TOZO HT3 Bluetooth headphones. I use them at the desk, in bed, and on the couch. One pair, everywhere.

For the Right Person — Yes.

IS IT WORTH IT?

This setup was built over time, piece by piece, solving real problems. It's not for everyone. If your office and living space are completely separate, or your internet connection isn't stable enough for streaming, some of this won't apply.

But if you're someone who spends long hours at a desk — working and gaming on the same machine — there's a real cost to being locked to that one spot. You stop wanting to be there. The desk stops feeling like a place for leisure and starts feeling like an obligation.

Moonlight solves that. Not perfectly, not for every situation — but well enough that I haven't gone back. Quick work fix at night? Done from bed. Early morning gaming without waking anyone? Done from the couch. That flexibility is worth more than any single component on this list.

Every product linked in this post is something I use every day. Nothing is here for show.

This Build Isn't Finished.

WHAT'S NEXT

That's the thing about building your own system — it's never really done. Here's what's coming:

  • Bringing OPNsense back online for proper network control and firewall management
  • Adding a NAS for automatic photo backup from every device in the house
  • Integrating the open chassis into the desk for a cleaner setup
  • Possibly moving to water cooling for better temperature control and dust management

Each of those is a post. I'll document the process — what worked, what didn't, what I'd do differently. If you're building something similar, follow along.

Questions about the setup? Drop them below. I built this without a guide — figured it out piece by piece over time. Happy to help you figure it out.



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.

Read More