[1.64.0] - 2026-06-01
- FIXED: DNS redirect didn't work - when a set sent its DNS lookups to a chosen server (the set's DNS tab), names failed to resolve and the internet seemed to hang. Redirected DNS now works as expected.
- IMPROVED: MTProto Telegram routing is more reliable, especially for media - the WebSocket routing (bridge mode) now works on phones as well as desktop, loads media more reliably, and always prefers WebSocket regardless of the proxy server's transport setting. Data centers without a WebSocket edge no longer stall when the shared fallback domains get rate-limited. New "Cloudflare Worker" support adds a free, per-user relay (no domain to buy) for accounts where media, reactions, or stickers still fail to load - see Settings -> MTProto Proxy.
- FIXED: Copy buttons did nothing when the Web UI was opened over plain HTTP - copying commands, set exports, or system info silently failed on installs reached by LAN IP (for example
http://192.168.1.1), because browsers only allow the modern clipboard API over HTTPS or localhost. The fallback copy path now works in those cases too. - FIXED: Memory and CPU slowly climbed when the watchdog repeatedly repaired a site - each watchdog repair left behind a background task that never stopped, piling up over days until b4 was killed. #227
- FIXED: Traffic page lumped every connection under "Unknown" in the Aggregated view - on networks where b4 cannot map a client IP to a MAC address (for example devices behind another router), the Devices sidebar collapsed all traffic into a single "Unknown" device, even though the Raw feed clearly showed different source IPs. Connections without a known MAC are now grouped by their source IP, so each device appears separately.
- FIXED: Filter box did nothing in the Traffic page's Aggregated view - multi-term filters like
!github + !googlewere treated as one literal text match, so the view usually showed nothing. The Aggregated view now uses the same filter syntax as the Raw feed: combine terms with+, exclude with!, and target a column withfield:value. - ADDED: More checks in the DPI Detector - the DPI Detector page can now also measure how quickly your DNS servers respond and test whether Telegram works (download speed, plus whether all of Telegram's servers are reachable). The existing checks were made more accurate at telling apart the different ways a provider can block or tamper with a connection, the list of sites and servers it tests was refreshed, and a new "Legend" explains what each result means. The DPI Detector is based on the dpi-detector project.
What's Changed
- feat: implement WebSocket connection pooling and improve MTProto tran… by @DanielLavrushin in #229
- fix: ensure DHCP service stops when the pool is stopped by @DanielLavrushin in #231
- Refactor code structure for improved readability and maintainability by @DanielLavrushin in #232
- feat(dns): implement DNS forwarding and resolution with fragmentation… by @DanielLavrushin in #234
- feat: enhance traffic filtering and aggregation functionality by @DanielLavrushin in #235
- feat(detector): add DNS availability and Telegram reachability checks by @DanielLavrushin in #236
Full Changelog: v1.63.0...v1.64.0