Network Optimization
My trusted iMac Pro (2017) has started falling short for more demanding tasks. To keep pace with video editing, AI workloads, and virtualization, I added a modern Intel x64 workstation to my setup.
The iMac still performs well for office work and regular development, especially now that the heavier apps are offloaded. This also presented an opportunity to reorganize the network infrastructure.
Previously, the WiFi router also served as the DNS server, but OpenWRT was unstable. After a complete firmware refresh, I reconfigured it to act solely as an access point for two wireless networks:
- 2.4GHz: Legacy devices (e.g., 2010 MacBook Pro)
- 5GHz: High-speed access for modern devices
Next, I repurposed the 19" Short-Rack mini-ATX Linux server to act as a central node in the network. Docker deployments will shift from it to the new rig that has more than enough RAM and storage to handle that. The 19" now runs multiple services:
- Time Server (Chrony)
- DNS Server (Bind9)
- AdBlocker (Pi-hole)
- SMB Shared Drive (32GB)
I configured the time server to pull updates directly from Stratum 0 servers which will ensure <0ms clock synchronization across all devices. The DNS service works in tandem with Pi-hole, which serves as a filtering layer. I define additionally a local DNS Zone to resolve for .lan domains e.g. iphone.lan or server.lan. This makes navigating within my domain more pleasant. For upstream DNS, I configured reliable, uncensored U.S.-based resolvers.
With Pi-hole in place, I now benefit from network-wide ad blocking across all devices—very effective.
File sharing is handled via a 32GB SMB share, simplifying device-to-device transfers. While I primarily use SSH and Parsec for remote access, the lack of drag-and-drop support in Parsec makes the SMB drive particularly convenient. Parsec, however, allows me to use only one monitor (the iMac) and access all Windows devices via real-time H.264 streams. Most graphics cards support hardware encoding and decoding of H.264, which makes this very light on the CPU. This setup is a significant advantage over using Remote Desktop Protocol, which is unsuitable for higher resolutions, refresh rates, or any fast-changing visuals.
After having spent quite some time reworking this setup, the new task ahead will be to tackle the IP request from Steam, that the release of the WTF-Model can move forward.