If you are reading this, you are likely staring at a blue dot next to a peer in your Hamachi network, indicating a Relayed Tunnel. While this allows you to connect, the performance is often sluggish, latency is high, and file transfers are slow.
Ideally, you want a Direct Tunnel (indicated by a green dot), which offers the speed and low latency of a direct peer-to-peer connection.
This guide outlines the technical reasons behind relayed tunnels and provides step-by-step solutions to force a direct connection.
Hamachi needs inbound/outbound UDP on port 12975 (or 12974–12976 range).
Windows Defender Firewall (Advanced):
12975 → Allow the connection.hamachi-2.exe and HamachiClient.exe in both inbound/outbound.Third-party (e.g., Kaspersky, Bitdefender): Add Hamachi as a trusted application and allow UDP 12975.
Transitioning from a Relayed Tunnel to a Direct Tunnel primarily requires opening a UDP port on the router and firewall. The most effective method is Manual Port Forwarding combined with Windows Firewall exceptions. If the issue persists after these steps, the user should investigate ISP limitations such as CGNAT. hamachi relayed tunnel to direct tunnel fix
How to Fix Hamachi Relayed Tunnel to Direct Tunnel (2026 Guide)
If you are using LogMeIn Hamachi to play games with friends or access files, you may encounter a Relayed Tunnel (indicated by a blue dot) instead of a Direct Tunnel (green dot).
A relayed tunnel means your connection is routing through a LogMeIn server, leading to high latency (lag) and lower speeds, whereas a direct tunnel creates a direct peer-to-peer connection. Here is a comprehensive guide to fixing this, updated for 2026. Phase 1: Basic Troubleshooting (Quick Fixes) Restart the Service: Right-click the Windows start button, select LogMeIn Hamachi Tunneling Engine , right-click it, and select Toggle Power Button:
Click the Power button in the Hamachi UI to take it offline, then click again to bring it back online. Ensure Both Users are Online:
A direct tunnel cannot be established if both parties are not actively online with green dots on their own end. Phase 2: Windows Firewall Configuration (Most Likely Fix)
Windows Firewall often blocks the specific Peer-to-Peer connection Hamachi uses. Open Windows Firewall: Search for "Allow a program" in the Start Menu and select Allow a program or feature through Windows Firewall Change Settings: Change settings button (requires admin rights). Add Hamachi Engine: Hamachi Stuck on Relayed Tunnel
Fixing a Hamachi relayed tunnel (indicated by a blue dot) to a direct tunnel (green dot) typically involves resolving firewall restrictions, restarting services, or configuring port forwarding to allow direct peer-to-peer communication.
Here are the most effective fixes based on common solutions: 1. Fix Windows Firewall Exceptions
The most common cause is the Windows Firewall blocking the Hamachi client.
While there are no major peer-reviewed "academic papers" exclusively dedicated to fixing a relayed tunnel in
, several technical resources and research papers on P2P NAT traversal and UDP hole punching explain the underlying mechanics of how these tunnels function and how to improve them. Technical Documentation and Solutions
Official and community troubleshooting guides identify "relayed tunnels" (indicated by a blue dot) as a failure of direct peer-to-peer (P2P) communication, typically due to firewall or NAT restrictions. Primary Fixes for Direct Tunneling: Step 4: Adjust Hamachi Settings
Firewall Exceptions: Manually allow the Hamachi Client Tunneling Engine (hamachi-2.exe) through both Windows and third-party firewalls. Ensure it is checked for Domain, Private, and Public networks. Manual Port Forwarding: Set a static UDP port in Hamachi's Advanced Settings.
Forward that specific UDP port on your router to your computer's local IP address. Restart the Hamachi service to apply the change.
Traffic Rules: In the Hamachi client, right-click the peer and navigate to Details > Settings > Traffic and set it to Allow All. Related Academic and Technical Papers
For those interested in the networking theory behind these fixes, the following papers discuss the technologies Hamachi uses for direct tunneling:
Integrating Overlay and Social Networks for Seamless P2P Networking: Discusses how private P2P tunnels are established and maintained without central administration, which is the core goal of a "direct tunnel".
A New Approach to Peer-to-Peer VPN Connectivity: Examines how to achieve direct P2P connections and automatic NAT traversal to reduce latency.
Improving VPN performance over multiple access links: Explores system innovations used to maximize VPN throughput and manage varied communication characteristics between peers. Core Concepts Used by Hamachi
The transition from a relayed to a direct tunnel involves technical concepts like: