Protocol
Set global proxy, Freedom, and Blackhole defaults.
Updated
Protocol is the Settings page for global behavior that applies beyond one manual node. It covers proxy multiplexing, direct-connection Freedom behavior, and Blackhole response behavior. Changes save when you leave the Protocol screen.
Main Protocol screen
Proxy
Multiplexing combines multiple proxy connections over one TCP connection.
Multiplexing
Turns Mux on or off. It can reduce repeated connection setup for many small requests, but it also makes more traffic depend on one underlying connection.
xUDP UDP 443
Controls how Mux treats UDP traffic on port 443, which is often used by QUIC and HTTP/3. Allow lets that traffic use xUDP, Reject blocks that xUDP path, and Skip leaves it out of this special handling.
TCP and xUDP Concurrency
Limits how many TCP or xUDP streams can share Mux at once. Use No Limit when you do not need a cap; lower values can calm bursty traffic, while higher values can keep busy nodes from queuing too quickly.
Freedom
Freedom controls direct-connection behavior for traffic that does not use the selected proxy node.
TLS Hello Fragmentation
Splits the first TLS greeting for direct Freedom traffic. It can help only on paths that specifically need fragmentation; otherwise it may make direct HTTPS traffic slower or less predictable.
Target Strategy
Chooses how direct traffic resolves names into IP addresses. AsIs keeps the original target, UseIP resolves before dialing, IPv4 or IPv6 choices prefer one address family, and Force choices can fail when that family is unavailable.
Fragment controls
Length chooses fragment size, Interval chooses the pause between fragments, and Max Split limits how many pieces Tunna can make. Smaller, slower fragments are more intrusive and should be used only for a measured direct-route problem.
Blackhole
Blackhole controls blocked traffic behavior.
Response
Choose silence or an HTTP 403 reply for blocked traffic. Silence is cleaner for general blocking; HTTP 403 is useful when you want a browser or app to receive an explicit denied response.
Noises and Final Rules are child pages
Both rows show counts on the Protocol screen. Inside each child page, use Add, tap a row to edit, swipe to delete, and drag rows into the order you want.
Noises
Use Noises only when your provider or support instructions ask for them on direct Freedom traffic. They send extra random or user-entered packets with a chosen address family and delay; most users should leave the list empty.
Random
Sends generated bytes. Use it only when the needed packet size is known.
String, HEX, Base64
Sends exactly the packet text you provide in the selected format.
Final Rules
Use Final Rules as a last allow/block gate for direct Freedom traffic. Most routing work belongs on the Routing Rules page; this child page is for direct traffic that needs a final narrow exception or block.
Allow or Block
Choose the final decision, then narrow it only when the network, port, or IP range is known.
Network, Port, IP
Leave optional fields empty for a broad rule. Block Delay waits before dropping matching traffic and should stay short unless support asks otherwise.
Practical protocol uses
Limit Mux experiments
Use Multiplexing, xUDP UDP 443, and concurrency together only when your provider supports that behavior.
Good fit A provider profile or support instruction expects Mux or xUDP behavior.
Not ideal You are trying to fix a node whose basic protocol settings are not confirmed.
Tune direct traffic
Freedom settings affect direct outbound behavior, not traffic that is sent through the selected proxy node.
Good fit Your Default Route or a rule sends traffic to Freedom.
Not ideal You expect these settings to alter Proxy traffic.
Choose block behavior
Blackhole response controls what blocked traffic receives at the end of a route decision.
Good fit HTTP 403 is more useful than silence for a blocked HTTP request.
Not ideal You want blocked traffic to receive no response.
Protocol saves when you leave
The main Protocol controls save on leave. Noises and Final Rules use child pages: add or edit rows there, then return to the Protocol page with the revised counts before leaving.