Optional Telegram SOCKS5 input (#137)
- Add a separate, opt-in SOCKS5 CONNECT listener (loopback port 1080 by default),
alongside the existing MTProto/FakeTLS listener, with a shared connection budget. - Bridge plain and secretless-obfuscated abridged/intermediate/padded MTProto to
the existing WSS/Cloudflare/upstream/TCP fallback ladder and pool. - Resolve client destinations using exact Telegram DC mappings: common IPv4
DC and media endpoints plus the IPv6 DC1–5 addresses built into the official
clients, with explicit signed DC:IP mappings on top. An address in neither but
inside Telegram's published ranges is routed by the DC the client's
obfuscated header names, as Telegram Desktop always does, so new media
addresses keep loading. One whose header names none is closed with a warning
that media will not load. Addresses outside Telegram, arbitrary hostnames and
UDP/BIND are refused. Each outcome is logged once per address; repeated
rejections go to debug level. - Add an OpenWrt LuCI switch, listener settings and DC mappings, plus English and
Russian Forkop setup guides linked from README. - LuCI shows each listener's connection links with a Copy button: the MTProto
tg://proxylink per secret, and for SOCKS5 asocks5://URL for router
services plus atg://sockslink when it is reachable from the LAN. They
come from the new--print-links, so LuCI and the startup banner agree.
This input has no authentication and is intended for a local routing service or
trusted LAN. It is not a generic web proxy, TUN interface, or UDP calling tunnel.