Using P2P or server relay, connect multiple LANs to enable communication between any networked devices across these LANs.
The authors and contributors of this project are not liable for any direct, indirect, incidental, special, or consequential damages arising from the use, modification, copying, or distribution of this code. Under no circumstances shall the authors or contributors be held liable for any contractual, tort, or other legal responsibilities.
Users of this project are responsible for ensuring compliance with local laws and regulations. The authors and contributors assume no responsibility for any illegal activities or legal issues resulting from the use of this code. Users must ensure lawful usage within their jurisdiction.
This code is strictly intended for legal, ethical, and compliant purposes. The authors prohibit any use for illegal activities, attacks, abuse, or other malicious actions, including but not limited to unauthorized access, network attacks, etc.
For user convenience, this project provides public messenger servers and public relay servers. When using these services, users must comply with local laws and regulations. The authors, contributors, and server providers are not responsible for any illegal activities or legal issues arising from the use of these public servers.
- Encrypted configuration files
- Encrypted communication (SSL for all traffic)
- Hole-punching support: TCP (including IPv6) and UDP
- Hole-punching library: Use
linker.tunnelin your projects - Relay connections with seamless switch to direct P2P once a hole is punched
- Cross-LAN networking: Virtual NIC for building LANs between clients (P2P, point-to-network, network-to-network)
- Virtual NIC library: Use
linker.tunin your projects - Port forwarding: Forward local ports to remote client ports
- Server penetration: Register ports/domains on a server to access internal services
- Permission management: Master client controls permissions, exports/configures sub-client settings
- Custom authentication: Validate connections via
HTTP POSTfor beacon, relay, and penetration - Traffic statistics: Track beacon, relay, and penetration traffic on servers
- Network configuration: Master client sets up networks, auto-assigns IPs to all clients
- Distributed architecture: Multiple relay nodes for massive scalability
- SOCKS5 proxy: Dynamic port forwarding without specifying ports
- Easy integration: Use
linker.messenger.entryto embed into your projects - CDKEY，It can temporarily lift certain restrictions
In a .NET 8+ project, install the NuGet package linker.messenger.entry
LinkerMessengerEntry.Initialize();
LinkerMessengerEntry.Build();
LinkerMessengerEntry.Setup(ExcludeModule.None);
米多贝克
