Practical tools for system, network, security, and operations administrators.

NET-C0149 · Wireless & RF

How to Plan a Point-to-Point Wireless Link

Plan one point-to-point wireless hop you are allowed to build, and stop if the path is not clear.

Updated 25 October 2026 · How-To

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

A point-to-point plan names two ends, a frequency, a Fresnel clearance, and a fade margin. The planners draft those figures. Line of sight that crosses a property or a coordinated band you do not hold is a plan you do not build.

Rain fade matters on higher frequencies and longer hops. Write the margin. If the tools say the zone is blocked, the answer is a different path or a wire, not more power.

One hop. Aligning radios is a later visit with a rollback, which on a wireless hop means you can still reach the radio if the aim is wrong. Out-of-band management is part of the plan.

Do not use the calculators to aim at a network you do not administer.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Name two ends you may use.
  2. Check clearance and fade.
  3. Write management that survives a bad aim.
  4. If the zone is blocked, stop.
  5. Keep power legal.
  6. Do not align the radios in the writing hour.

Mistakes that outlive the command

How to Plan a Point-to-Point Wireless Link goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for How to Plan a Point-to-Point Wireless Link: The ends are permitted. Clearance is written. Management survives a miss. Power is legal. And radios stay unaligned.

Checks before you call it done

Confirm this before you call the change done: Both ends are named. The margin is in the note. A blocked zone stopped the plan. Power is within the limit. And no radio was moved yet. If one of those fails, stop.

Before you leave the device

How to Plan a Point-to-Point Wireless Link ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.