Commit Graph

19 Commits

Author SHA1 Message Date
Alexey dac7aeeeda Merge pull request #972 from AndreyOsipuk/fix/client-mss-prefix
client_mss: chunk only the start of the initial server response
2026-11-15 13:31:31 +03:00
Alexey cec30d01e8 Config Apply + Pretty Params Descriptions in Docs
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-11-11 23:53:57 +03:00
Andrey Osipuk 7e6fc15ef2 feat(client_mss): chunk only the start of the initial server response
With client_mss_bulk the whole authenticated FakeTLS response (ServerHello,
CCS, emulated certificate records, tickets - typically ~4 KiB) was written in
client_mss-sized chunks: about 50 segments at `tspu`. With ~2% loss at least
one segment is lost in ~64% of handshakes, and the burst takes several RTTs
to pass the initial congestion window.

- New server.client_mss_prefix (Linux, requires client_mss_bulk): `full`
  (default, current behavior), `server-hello` (through the end of the first
  TLS record, capped at 2048 bytes, falls back to `full` on unexpected input)
  or a byte count. Only that prefix is written in MSG_EOR chunks; the rest
  goes out in one write at the bulk MSS.
- Chunk payload accounts for TCP timestamps and never exceeds tcpi_snd_mss.
- Removed TcpMaxSegmentGuard: TCP_MAXSEG on an established socket does not
  change the MSS of outgoing segments on Linux, and its getsockopt/setsockopt
  failures no longer abort the handshake. TCP_NODELAY is set once.
- Docs (en/ru/de), API discovery metadata, strict keys, reload diff.
2026-11-09 15:36:29 +03:00
Alexey 82baf0dda4 Config Parameters synced 2026-11-07 23:06:12 +03:00
Alexey b1502b629b DNS Overrides in Docs 2026-11-06 22:48:06 +03:00
Alexey 4635ecadd3 Retry Jitter in Docs 2026-10-31 14:38:25 +03:00
Alexey 1870ef82a9 Web Limits Wildcard in Docs 2026-10-28 21:29:00 +03:00
Alexey 8f488b254d Max Conns in Docs 2026-10-23 20:29:58 +03:00
Alexey 56e0f000ba Docs 3.5.8 Pull-Up
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-09-27 18:55:31 +03:00
Alexey 9008c37926 API for WEB Docs
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-08-27 21:44:10 +03:00
Alexey d41a8c3220 Docs for WEB: carriers + auto-negotiation + websocket budgets
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-08-27 09:05:06 +03:00
Alexey 4e5bccd2c7 Update deps + Docs for Webosckets in WEB-Modus 2026-08-26 09:56:18 +03:00
Alexey 8e577ec5ca DE and RU WEB debug documentation synchronized 2026-08-25 13:14:19 +03:00
Alexey 596149cab8 Docs for aligned carriers 2026-08-23 10:54:42 +03:00
Alexey e2b7c5c731 Docs for https-lanes
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-08-23 09:06:00 +03:00
Alexey 79ad4cb541 Docs for WEB
Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
2026-08-23 03:32:40 +03:00
Alexey bb0d3ba927 Manifest Revision + Listener Reload Semantics + MSS/SYN-limit Safety 2026-08-22 16:20:55 +03:00
Anton Vinogradov f770756cba fix(synlimit): raise default synlimit_burst from 1 to 24
The generic-path SYN limiter default of burst=1 admits only one new
connection per source IP, then refills at 48/minute (0.8/s). Telegram
clients open several connections at once on startup/reconnect, so the
extra SYNs are rejected with TCP RST until a token accrues — clients
intermittently fail to connect until the app is restarted.

The iOS fast-path (meta length 64) does not match real-world traffic
behind carrier NAT/NAT64 (SYNs arrive as 60 bytes), so the generic path
governs all clients, iPhone included. Raise its default burst to 24 —
the value already used by the iOS path — so a legitimate startup fan-out
passes. Steady-state rate (48/minute) is unchanged, preserving the
anti-TSPU posture.

Updates the default constant, the default-assertion test, and the EN/RU/DE
CONFIG_PARAMS docs.
2026-07-16 13:04:23 +03:00
Alexey 5b3ad0096b Create CONFIG_PARAMS.de.md 2026-07-09 22:42:07 +03:00