Website、Documentation、Join QQ Group
Users are responsible for complying with local laws and regulations. It must not be used for illegal or criminal purposes.
Using P2P or server relay, connect multiple LANs to enable communication between any networked devices across these LANs.
| amd64 | x86 | arm64 | arm | |
|---|---|---|---|---|
| Windows | ✔ | ✔ | ✔ | |
| Linux | ✔ | ✔ | ✔ | |
| Linux Musl | ✔ | ✔ | ✔ | |
| Openwrt | ✔ | ✔ | ✔ | |
| Android | ✔ |
- Hole punching connections, supporting TCP, UDP, IPv4, and IPv6
- Relay connections, with self-hosted relay nodes and support for multiple relay nodes
- Cross-region networking: peer-to-peer, peer-to-network, network-to-network, automatic virtual IP allocation, subnet mapping (resolving multi-LAN subnet conflicts)
- Port forwarding: forwards a client's port to another client's port
- Server penetration: access internal network services via ports or domains (supports scheduled tasks for timed auto-enabling/disabling)
- SOCKS5 proxy: while port forwarding requires specifying ports, the SOCKS5 proxy can handle all ports
- Encrypted configuration files
- Permission management: the main client has full control, allowing the export and configuration of sub-client settings and delegated admin rights
- Custom authentication: via HTTP POST, you can define verification rules for allowing connection beacons, relays, and intranet penetration
- Traffic statistics: monitors traffic for beacons, relays, and intranet penetration on the server
- CD-KEY: temporarily unlocks certain restrictions, such as relays and intranet penetration
- More，Documentation
- Uses the linker.tunnel library for hole punching
- Uses the linker.tun virtual NIC library, including Linux TUN and Windows Wintun adapters, NAT conversion, and subnet mapping
- Uses the linker.snat library for NAT conversion
- Uses linker.messenger.entry for full-feature integration
Buy the author a coffee to keep the project alive!
米多贝克