Northeast Miami-Dade County, FL · A past field engagement; exact dates not published
Case Study: Replacing a Dying SSL-VPN With WireGuard in Miami-Dade
A business in northeast Miami-Dade County was living with a remote access setup everyone had learned to apologize for: an aging SSL-VPN appliance that crawled through file transfers and dropped voice calls mid-sentence. Replacing it with WireGuard, a modern kernel-level VPN protocol, turned remote access from the office complaint into something nobody thinks about, which is what infrastructure is supposed to be.
By Lazaro Anias, founder & engineer. Published . Updated .
- Location
- Northeast Miami-Dade County, FL
- Project period
- A past field engagement; exact dates not published
- Scope
- Remote-access migration, device keys and traffic priority
Where it stands: The migration replaced the old remote-access appliance. File transfers improved and recurring voice-call complaints stopped in the period following the change.
The challenge
- An end of life SSL-VPN appliance with degrading performance and a support clock running out.
- Remote file transfers slow enough that staff drove to the office for large jobs.
- VoIP calls over the tunnel dropping regularly, which for a business phone system is not an inconvenience, it is missed business.
What we built
WireGuard at the edge
We replaced the aging appliance with WireGuard and reviewed the network path used for remote work.
A staged cutover with both systems live
The new tunnel ran alongside the old appliance during transition, so users moved over in groups and the old system was only unplugged after the last one confirmed clean.
QoS attention on voice traffic
VoIP packets got priority treatment through the new tunnel, addressing the drop problem at both the protocol and the queue level.
The results
- File transfers ran roughly three times faster in comparisons made during the migration. This was an observed project result, not a controlled protocol benchmark.
- Recurring VoIP-drop complaints stopped after the migration and traffic-priority changes.
- The VPN software had no recurring license fee. Configuration, key management and ongoing support remained necessary.
Client not named by policy. The location is published at county level; the throughput figure is a rounded comparison from the migration period, not a laboratory benchmark.
Related services