How snltty/linker works
Linker is a multi-platform private networking and tunneling application. A user configures a client and signs in to a coordination server, selects peers and connection modes, then uses the resulting tunnel for virtual-network access, port forwarding, or SOCKS5 proxying. The README also describes relay and mesh connectivity, subnet mapping, firewall controls, discovery, wake-on-LAN, and scheduled reverse access. The graph reflects these documented capabilities; sampled controller and tunnel code supports the API-to-messenger and tunnel-orchestration roles, but not every subsystem’s internal wiring.
Main entry points: TunnelTransfer.cs Tunnel engine · SignInApiController.cs Sign-in · TuntapApiController.cs Virtual networking · FirewallApiController.cs Access firewall
Components 21
Client and UI
- Client interface
src/linker.web/src/main.js - App host
src/linker.app/MainPage.xaml.cs - Client APIs
src/linker.libs/web/IApiController.cs
Coordination
- Sign-in
src/linker.messenger.signin/SignInApiController.cs - Traffic reporting
src/linker.messenger.flow/FlowApiController.cs - Client updates
src/linker.messenger.updater/UpdaterApiController.cs
Tunnel connectivity
- Tunnel control
src/linker.messenger.tunnel/client/TunnelApiController.cs - Tunnel engine
src/linker.tunnel/TunnelTransfer.cs - Relay nodes
src/linker.messenger.relay/client/RelayApiController.cs - Mesh forwarding
src/linker.messenger.mesh/MeshApiController.cs
Network services
- Virtual networking
src/linker.messenger.tuntap/client/TuntapApiController.cs - Port forwarding
src/linker.messenger.forward/ForwardApiController.cs - SOCKS5 proxy
src/linker.messenger.socks5/Socks5ApiController.cs - Access firewall
src/linker.messenger.firewall/FirewallApiController.cs - LAN discovery
src/linker.discovery/DiscoveryProtocolHandlerLlmnr.cs - Remote wake-up
src/linker.messenger.wakeup/WakeupApiController.cs - Reverse access
src/linker.messenger.reverse/client/ReverseApiController.cs - Scheduled plans
src/linker.messenger.plan/PlanApiController.cs
Other components
- User
- Coordination server
- Remote peers
Connections 21
- User → Client interface: configures
README.md - Client interface → Client APIs: requests
- Client APIs → Sign-in: dispatches
src/linker.messenger.signin/SignInApiController.cs - Sign-in → Coordination server: signs in
README.md - Sign-in → Tunnel control: selects peers
- Tunnel control → Tunnel engine: controls
src/linker.messenger.tunnel/client/TunnelApiController.cs - Tunnel engine → Remote peers: connects tunnels
README.md - Tunnel engine → Relay nodes: uses relay
README.md - Tunnel engine → Mesh forwarding: uses mesh
README.md - Tunnel engine → Virtual networking: carries virtual traffic
README.md - Tunnel engine → Port forwarding: carries forwarded traffic
README.md - Tunnel engine → SOCKS5 proxy: carries proxy traffic
README.md - Virtual networking → Access firewall: filters access
README.md - Port forwarding → Access firewall: filters access
README.md - SOCKS5 proxy → Access firewall: filters access
README.md - Virtual networking → LAN discovery: proxies discovery
README.md - User → Remote wake-up: requests wake-up
README.md - User → Reverse access: configures access
README.md - Reverse access → Scheduled plans: schedules access
README.md - User → Traffic reporting: views traffic
- User → Client updates: manages updates