← Back to Engineering Blog
🗓️ Sep 15, 2011 ⏱️ 3 min read

Debugging the Air: Troubleshooting Packet Loss on WiMAX & RF Links

🎙️ Listen to Article READY
AI Audio Synthesis Narrator
Share Post:

“The link was rock solid all morning. But exactly at 4:00 PM every day, like clockwork, the connection would choke. By 5:30 PM, it cleared up completely.”

For enterprise customers in 2011, “The Cloud” was a focused beam of radio waves blasting through urban smog.

I was assigned a ticket at Spectranet that defied every standard troubleshooting playbook. A high-priority client was suffering 40% packet loss every afternoon.


The Debug: CLI vs. Physical Reality

I performed standard Network Operations Center (NOC) diagnostics. I blamed the router configuration.

  • Interface Config: Clean, no rate-limiting drops.
  • CPE Errors: Zero CRC errors on Ethernet interfaces.

From the safety of the SSH terminal, everything looked perfect. Yet the customer’s VoIP calls were dropping continuously.

[!IMPORTANT] Diagnostics from a remote SSH session can lie if you ignore physical layer telemetry. When terminal output looks clean but packets are dropping, the problem is physical.

# # Alvarion BreezeNET Wireless Telemetry Check
# breeze-cli > show link-status
  Signal Strength (RSSI): -82 dBm [CRITICAL]
  Signal-to-Noise Ratio (SNR): 12 dB [DEGRADED]
  Retransmit Rate: 44.2%

The Roof Climb

I drove to the customer site and climbed up to the rooftop antenna mast.

I connected my laptop directly to the Received Signal Strength Indicator (RSSI) diagnostic port. The signal was fluctuating violently—swinging from a solid -62 dBm down to -85 dBm (near total silence).

[!NOTE] Line of Sight (LoS): RF links require a clear Fresnel Zone (an elliptical volume around the visual line of sight). Any obstruction inside this zone scatters the radio signal.

Then I saw the culprit.

It wasn’t rain fade or atmospheric interference. It was a 100-foot construction crane.

A nearby building crew swung a heavy crane boom directly through our point-to-point wireless path every day at 4:00 PM to unload steel beams. The metal lattice scattered the 5.8 GHz radio waves like a mirror.


The Fix: Wrench and Muscle

You cannot write a Python script or configure a route-map to bypass a steel crane arm.

I had to unbolt the mounting bracket, physically manhandle the outdoor unit (ODU), and repoint it toward a secondary relay tower 3 kilometers away to establish a clean Fresnel zone.

  • Shifted azimuth 15 degrees right.
  • Re-tightened mounting bolts.
  • Result: RSSI locked at -58 dBm. Zero packet loss.

The Verdict

Key Takeaway

Always Check Layer 1 First.

Never forget that all software abstractions rest on physical hardware and electromagnetic physics. You cannot code your way around bad physics—sometimes, the only tool that can fix the network is a 14mm wrench.

SKS

Sachin Kumar Sharma

Associate Director (Infrastructure & Cloud Architecture Strategy) | 20+ Yrs Exp

Architecting resilient multi-cloud enterprise landing zones, SDN overlay fabrics, DevSecFinOps automation pipelines, and autonomous Agentic AI platforms.