The new version of v2rayN supports multiple cores, the most common being Xray and sing-box. Most people can just use the default Xray, but when some new protocol nodes cannot be connected, switching to sing-box can often solve the problem. This article explains clearly how to cut and when to cut.
1First understand: what does the kernel do?
The kernel is the program actually responsible for connection, encryption and decryption, v2rayN is just the interface (see The relationship between the kernel and the client). Different kernels have different support ranges for protocols, which is why sometimes the same node can be used by changing kernels.
2How to choose between Xray and sing-box
- Xray (default): The main kernel of v2rayN has complete support for VMess, VLESS, Trojan, Shadowsocks, and Reality, and is the first choice for daily use.
- sing-box: For some newer protocols (Hysteria2, TUIC etc.) support more complete and stable. If your node uses this type of protocol, you will have a better experience using sing-box.
3where to switch kernel
The switching method varies slightly depending on the version. There are two common entrances:
- Cut by node: When editing a node, there is a "Core Type" option in the configuration. You can individually specify whether to use Xray or sing-box for this node. Hysteria2 / TUIC nodes usually use sing-box automatically.
- Global default: In the core/Core related page of "Parameter Settings", you can set the default kernel type.
After switching, it is recommended to "restart the service" to allow the new kernel to take effect.
Can't connect to the core after cutting it? First make sure the kernel is installed. If you want to use sing-box, you must have the sing-box kernel file in your computer. Go to "Check for Updates" to update/download the corresponding kernel, otherwise the startup will fail because the kernel cannot be found.
4Update the kernel separately
In the menu "Check for Updates", v2rayN body, Xray kernel, and sing-box kernel are updated separately. When encountering a new protocol node not working, the first reaction should be Update the corresponding kernel to the latest, rather than just updating the v2rayN interface. For the complete update process, see Upgrade update tutorial.