Two networks, one company
A separate circuit means separate DHCP, separate firewall, no domain access, and no shared drive. Every system in that building becomes an exception.
A shop, a scale house, a second warehouse, a barn, a pump station — anything you can see from your roof can be on your network at wired speeds. AllTech surveys the path, calculates the link budget, mounts the radios properly, and monitors the link so you find out about a degraded signal before your staff does.
The default fix for an outbuilding is a second ISP circuit. It's the most expensive option and it creates a second network that can't see the first one — so the shop can't reach the ERP, the cameras can't reach the recorder, and the badge reader out there has to be managed separately. The other default is a consumer range extender aimed out a window, which works until the first snowstorm.
A separate circuit means separate DHCP, separate firewall, no domain access, and no shared drive. Every system in that building becomes an exception.
A second business circuit is a monthly bill that runs forever. A wireless bridge is a one-time install.
Fiber between buildings means permits, an excavator, and a parking lot you can't use for a week. Across a public road or a neighbor's easement, it may not be possible at all.
Two access points pointed at each other through a window drop under load and fail the first time a tree leafs out in the path.
If you can stand on one roof and see the other, there is usually a link to be built between them.
A point-to-point link carries a single Layer 2 bridge across the gap. Done correctly it behaves like a long Ethernet cable — same VLANs, same subnet, same management.
Two topologies
What actually determines whether it works
Not "roughly toward it" — an unobstructed visual path. Trees in leaf, a new building, or a grain leg going up will each kill a link.
The signal travels in an ellipse, not a straight line. The middle of a long shot needs vertical clearance above the ground and rooftops, not just a clear sightline.
Transmit power, antenna gain, distance, and frequency have to add up to a margin that survives rain, snow, and heat. We design to fade margin, not to the best-case number on the box.
We survey the noise floor before we pick a band. 5 GHz is crowded in town; 60 GHz is fast and short-range.
A radio on a mast that flexes in wind will lose alignment. Most "the bridge is flaky" calls we inherit are mounting and grounding problems, not radio problems.
The gear we standardize on
We don't publish a throughput chart, because the honest number depends on your path. Expected throughput is calculated from the link budget during the survey, documented in the quote, and measured in both directions at handover.
We look at both roofs, measure distance and elevation, check the Fresnel zone against terrain and obstructions, and scan the local 5 GHz noise floor. If the link won't hold, you hear that before you spend anything.
Band selection, radio and antenna choice, mast height, fade margin, and expected throughput — documented, so the number we quote is the number you get.
Non-penetrating roof mounts, masts, or wall brackets; outdoor-rated shielded cable; proper grounding and surge protection at both ends. This is the part that determines whether the link lasts five years.
Aimed on signal, not by eye. We test throughput both directions, log signal margin and capacity, and hand you the numbers as a baseline to compare against later.
VLANs carried across the bridge so the remote building is on your network — same domain, same firewall policy, same cameras and door access — not a stranded island.
The link is in our RMM and UniFi monitoring. Signal degradation, capacity drops, and reboots alert us. Seasonal re-checks catch tree growth and mount drift before an outage.
Plant floor to a detached warehouse so scanners, printers, and the ERP client all live on one network.
Home office to shop, scale house, or pump station across a field where trenching isn't practical.
City hall to a public works yard, fire station, or water treatment site — often point-to-multipoint from one tall mast.
A second suite across a parking lot the landlord won't let you trench.
Getting cameras at a remote gate or lot back to the recorder without running fiber to it.
A link that goes up quickly and comes down when the job ends.
Site visit to both endpoints. Distance, elevation, obstructions, spectrum scan, mounting options, power and cable runs. Output: a go / no-go with a designed link and a fixed quote. If the honest answer is "trench the fiber," we say that.
Mounts, radios, cable, grounding, surge protection. Aim, test, and integrate into your VLANs and firewall. Baseline throughput and signal margin documented before we leave.
Link monitored alongside the rest of your network. Alerts on degradation, firmware managed, seasonal path re-check. If it drops, we already know.
Faster than most of the buildings it connects, and typically faster than a second ISP circuit would be. The honest number depends on distance, band, and path, so we design the link budget during the survey and document the expected throughput before you commit — then measure it at handover.
Yes. Point-to-point wireless is not a "signal through walls" technology. We need a clear visual path with clearance around it. During the survey we tell you whether you have one — and whether you'll still have one in July when the trees fill in.
A properly designed link has fade margin built in for weather. 5 GHz handles snow and rain with very little loss; 60 GHz is more affected, which is why we pair it with a 5 GHz failover on longer or weather-exposed shots. Wind matters more than weather — it is a mounting problem, and we over-build the mount.
They solve different problems. A wireless bridge is the physical link between two places you can see. A site-to-site VPN or SD-WAN connects sites over the internet, at any distance. For buildings on the same property, a bridge is faster, cheaper to run, and has no ISP in the middle.
A typical two-building link is a fraction of the cost of trenching. That said, if the run is short, the ground is open, and you want a permanent path with no weather exposure, fiber is the better long-term answer — and we install that too. We'll quote both.
On the VPN comparison, see Site-to-Site & SD-WAN; on the fiber alternative, see Structured Cabling.
The tunnel that may run over this link, and the answer when the sites are too far to see.
The fiber alternative when trenching is the better answer, and the cable on both ends of every bridge.
Outdoor coverage at the remote building once it is on the network.
Cameras at remote gates and lots, reporting back to one recorder.
The switch and PoE at each end of the link.
The VLANs and policy the bridge carries across.
Send us the two addresses and we'll tell you on the survey whether a wireless bridge is the right call — including when it isn't.
Trusted by dozens of businesses