1. Project Overview

The simplest solution available: connect any two computers anywhere on the internet directly with just one command! No public IP, no server relay, no installation, and no registration required. Ideal for beginners, supporting intranet penetration and NAT traversal.

2. Open Source License

Licensed under Apache-2.0

3. Screenshots

4. Feature Overview

Features

1. Direct connections between two computers! Direct connections! Direct connections! No third-party servers involved, so you don't have to worry about data privacy leaks.

2. One command is all it takes. No installation, registration, public IP, or configuration files required.

3. Direct connections are based on QUIC, offering high performance and encryption.

Note: Starting with version 1.1.6, communication security has been enhanced, making it incompatible with older versions.

Introduction

1. Run the same program on both computers. Add the --remote option on one computer (hereafter referred to as the remote side) and the --local option on the other (hereafter referred to as the local side).

2. The connection between the local and remote sides is a direct peer-to-peer connection, without passing through any third-party server.

3. The local side can access the remote side, but not vice versa.

4. If you need the reverse connection or need to access multiple remote sides, simply run multiple instances of the program or launch multiple Docker containers.

5. Multiple local sides can connect to one remote side, but one local side cannot connect to multiple remote sides. Use the same --key to establish the corresponding connection relationship.

6. Because the direct connection process is complex, repeated retries may occur. Connections are usually established within 10 minutes. If the connection fails for an extended period, please report the issue to the author.

7. This program supports both command-line and Docker deployment. The following examples are for reference only; you can switch between the two methods as needed.

8. Windows' built-in antivirus software may classify all programs written in Go as viruses. This program is open source, so you can use it with confidence.

5. Tech Stack

Quick Start

Operating Modes - Introduction

Proxy Mode

The local side needs to specify a local port to provide a SOCKS5 proxy service.

Configure the SOCKS5 proxy on the local side at the system or application level to access all host ports within the network where the remote side is located.

Port Forwarding Mode

The remote side needs to specify a host port within its network, and the local side must also specify a local port.

The local side does not need to configure a SOCKS5 proxy. Simply accessing the specified local port is equivalent to accessing the specified host port on the remote side. However, only this particular port can be accessed.

Note: Port forwarding mode supports only the TCP protocol. Each remote instance can forward only one port, but multiple remote instances can be run.

Proxy Mode - Example

The local side runs on an office computer, while the remote side runs on a NAS at home.

Configure the proxy address on the office computer as follows: socks5://127.0.0.1:18080. You can then access all host ports on your home network, including those on your NAS.

Home NAS (Linux, Docker)

Download the image: registry.cn-shanghai.aliyuncs.com/kony/goodlink

docker rm goodlink -f; docker run -d --name=goodlink --net=host --restart=always registry.cn-shanghai.aliyuncs.com/kony/goodlink --key= nas_202412140928

Note: Both the remote and local sides support command-line and Docker deployment. Choose either method. The examples above simply demonstrate both approaches.