UDP availability depends on the client, core, node protocol, network environment, and rules; an HTTP test alone cannot confirm it. Check the node declaration, policy-group selection, TUN interception, and UDP logs together. On the same node, compare results with UDP/TUN enabled and disabled. If the log says unsupported, switch protocols or nodes; if it says timeout, investigate network restrictions.
Do the node, protocol, and TUN all support UDP?
Generate real traffic with the target game, voice app, or QUIC app. Verify that the current node supports UDP, the policy group has the right node selected, and TUN is intercepting the app.
- Does the current node protocol support UDP?(See Outbound proxy configuration)
- Has the policy group selected a node that supports UDP?
- Is TUN or the application proxy intercepting UDP?
- Does the log show UDP timeout or unsupported?
Route game, voice, or QUIC traffic to the correct policy group
- First confirm that the node and protocol declare UDP support(See Connectivity FAQ)
- Enable the relevant UDP option or TUN setting in the client
- Use rules to route the relevant game, voice, or QUIC traffic to a UDP-capable policy group
- If it still fails, ask the configuration provider whether the server-side node supports it
A working HTTP website does not mean UDP is working
Some network environments restrict UDP
QUIC problems can also be affected by the browser, DNS, or network policy