Skip to content

Add a routing switch that blocks QUIC to force TCP fallback - #9

Merged
MimoProxy merged 1 commit into
mainfrom
kernel/block-quic
Nov 21, 2026
Merged

MimoProxy merged 1 commit into
mainfrom
kernel/block-quic

Conversation

@MimoProxy

Copy link
Copy Markdown
Owner

Summary

  • New routing.block-quic setting: off (default), proxy, all.
  • A flow counts as QUIC when it is UDP to port 443, or UDP sniffed as QUIC. TCP is never affected.
  • proxy rejects QUIC only when the final outbound (after group resolution) is not direct; all also rejects direct QUIC. Explicit reject / reject-drop rules keep their own outcome.
  • Rejected flows reuse the existing UDP reject path (packets dropped, destination remembered briefly), so clients fall back to TCP.
  • Connection history records reject_reason: block-quic. Changing only this setting is treated as a routing change and applies to new flows on commit.
  • Docs updated in the configuration guide and field reference.

Interface changes

FlowInfo gains an optional reject_reason field. No existing fields change.

Testing

  • Compile validation tests for defaults, valid values and invalid values.
  • Routing tests for off/proxy/all across UDP 443 via proxy, direct and named direct, TCP 443, sniffed QUIC on a non-443 port, UDP 53, and reject/drop rules.
  • Commit-level acceptance test.
  • make test and arm64 make vet for darwin, linux, windows and android.

🤖 Generated with Claude Code

routing.block-quic accepts off (default), proxy or all. UDP flows to
port 443, or UDP flows sniffed as QUIC, are rejected when the final
outbound is a proxy (proxy) or always (all). Explicit reject rules keep
their own outcome. Rejected flows reuse the existing UDP reject path so
clients fall back to TCP, and connection history records
reject_reason: block-quic.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MimoProxy
MimoProxy merged commit 35a2c05 into main Nov 21, 2026
17 checks passed
@MimoProxy
MimoProxy deleted the kernel/block-quic branch November 21, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant