BBR is Google's open-source TCP congestion control algorithm. On cross-border, higher-loss routes it often gives a big lift to download/upload throughput and lowers latency. Most mainstream WawaNode plans already ship a kernel that supports it — here is how to turn it on.
Step 1: Check your kernel version
BBR requires kernel 4.9 or newer. SSH into your server (or use the browser SSH console or VNC console on the service detail page) and run:
uname -rIf the version is below 4.9, use Reinstall OS on the service detail page to pick a newer image (such as Debian 12 or Ubuntu 22.04); those kernels include BBR out of the box.
Step 2: Write the sysctl config
Append these two lines to /etc/sysctl.conf:
echo "net.core.default_qdisc=fq" >> /etc/sysctl.conf
echo "net.ipv4.tcp_congestion_control=bbr" >> /etc/sysctl.confThen apply it immediately:
sysctl -pStep 3: Verify it is active
sysctl net.ipv4.tcp_congestion_control
lsmod | grep bbrThe first command should return net.ipv4.tcp_congestion_control = bbr, and the second should show the tcp_bbr module. That means BBR is on — no reboot needed, it takes effect right away.
Why BBR is faster
Traditional algorithms like CUBIC cut their rate sharply whenever they see packet loss, and cross-border routes are naturally lossy. BBR does not treat loss as the signal; it actively models available bandwidth and round-trip time to pace sending. That lets it keep the pipe full and deliver steadier throughput on lossy links.
Still stuck?
If BBR will not enable or your route still behaves oddly, open a ticket at 控制台 → 工单 (/dashboard/tickets/new) and link the affected service so we can help investigate.