Getting Back on Grid
Based on sentdex's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Starlink provides the baseline internet at the office, but mesh Wi‑Fi through trees and walls produced inconsistent speeds and periodic drops.
Briefing
A terminally online ranch setup is getting real internet back across multiple buildings by combining Starlink with Ubiquiti point-to-point wireless links—after earlier Wi‑Fi approaches proved too slow and unreliable through trees and walls. Starlink delivers roughly 100 Mbps down at the ranch office (sometimes higher, sometimes lower) but the upload is only around 10 Mbps, and the connection quality degrades when trying to spread that signal across 100–300 meter gaps between buildings. Mesh Wi‑Fi (Google Wi‑Fi/Nest) and prior bridging experiments can reach far—sometimes even through two walls and dense trees—but performance becomes inconsistent: the main PC sees about 30 Mbps down (with periodic drops), while phones land around 2–4 Mbps down, making video calls unreliable.
The core constraint is physical cabling. Running Ethernet for 100–300 meters isn’t practical with standard copper without intermediate gear, and any repeater/switch would require power in the middle of the property—something the setup lacks. Wi‑Fi extenders also haven’t worked well in past attempts, and the “mesh everywhere” approach, while workable, doesn’t meet the reliability and throughput targets for building-to-building use.
To solve that, the ranch owner pivots to directional wireless: Wi‑Fi bridges and point-to-point links. After researching the difference, the plan becomes clear—use Ubiquiti NanoStations as a focused beam between two buildings, creating a near “physical line” connection without trenching fiber or stringing long copper runs. Because the NanoStations need Power over Ethernet, PoE injectors are added so power and data can travel together. The installation strategy is also practical: mount the weather-resistant NanoStations on the outside of a wall, run a short Ethernet segment through the wall, then continue internal networking from a switch and rack.
Setup is described as fast and app-guided. The first unit is configured as a bridge, the second unit is paired through the mobile app, and alignment guidance in the app helps rotate the hardware for optimal pointing at long distances. The owner initially tests the concept before committing to permanent mounting, then trims nearby branches and clears line-of-sight obstacles to prevent wind or rain from blocking the link.
Once aligned, the building-to-building link delivers “100+ Mbps down,” which matches the Starlink performance goal—while upload remains limited by Starlink rather than the wireless bridge. Internally, Starlink’s router feeds a switch that powers mesh Wi‑Fi units for the house, while the Ubiquiti link feeds another switch in the server room. Networking is intentionally tiered: gigabit switching is used where NanoStations top out, and a 10‑gig switch is reserved for the most critical devices.
The result is a hybrid architecture: satellite internet arrives at one building, then a directional Ubiquiti point-to-point bridge carries it across the property to other structures. The approach avoids long cable runs, reduces the reliability problems seen with tree-and-wall Wi‑Fi propagation, and sets the stage for future expansion—potentially even solar-powered mesh nodes and wildlife monitoring—though that would be more expensive and power-hungry than the current plan.
Cornell Notes
The ranch setup restores reliable internet across multiple buildings by pairing Starlink with Ubiquiti NanoStations configured as a directional bridge/point-to-point link. Starlink provides about 100 Mbps download but spreading it via mesh Wi‑Fi through trees and walls yields inconsistent speeds and periodic drops, with phones often limited to a few Mbps down. Long Ethernet runs (100–300 m) are impractical without powered intermediate equipment, and Wi‑Fi extenders haven’t delivered dependable results. After clearing line-of-sight and using PoE injectors, the NanoStation link delivers “100+ Mbps down,” effectively matching Starlink’s performance while keeping the upload constrained by Starlink. The network is then distributed internally with gigabit switching and mesh Wi‑Fi for the house.
Why didn’t mesh Wi‑Fi alone solve the ranch’s multi-building internet problem?
What makes long Ethernet runs difficult at 100–300 meters in this setup?
How do Wi‑Fi bridges/point-to-point links differ from mesh Wi‑Fi in practice?
What hardware and power approach enables the NanoStation link?
What installation steps were used to make the link reliable?
How is the network distributed after the building-to-building link comes in?
Review Questions
- What specific performance targets (download, upload, latency, reliability) did the ranch owner set, and which approach failed to meet them?
- Why does the lack of power along the property make repeaters/switches impractical for long Ethernet runs?
- How does line-of-sight alignment and physical obstacle removal (trees/branches) affect the outcome of a point-to-point wireless link?
Key Points
- 1
Starlink provides the baseline internet at the office, but mesh Wi‑Fi through trees and walls produced inconsistent speeds and periodic drops.
- 2
Copper Ethernet becomes impractical over 100–300 m without powered intermediate equipment, which the property lacks.
- 3
Directional wireless bridging (Ubiquiti NanoStations) is used to replace long cable runs with a focused beam between buildings.
- 4
PoE injectors power the NanoStations, simplifying installation by combining power and data over Ethernet.
- 5
Mobile app setup and alignment guidance reduce the risk of mispointing, but line-of-sight still requires trimming obstacles.
- 6
After alignment and obstacle clearing, the NanoStation link delivers “100+ Mbps down,” matching Starlink’s download performance.
- 7
Internal networking is tiered with gigabit switching as the practical ceiling for NanoStation throughput, reserving 10‑gig for high-priority devices.