Introduction

It's a powered BBR TCP congestion control algorithm that can help reduce packet loss and preserve enough speed communication in any deteriorate network environments.

How to use?

1. Execute the following commands, start script:

wget --no-check-certificate -O Tsunami_BBR.sh https://git.io/fjmzL && bash Tsunami_BBR.sh

2. Type "1" then enter, choose a version kernel you want manually, limited Linux kernel 4.9.X ~ 4.13.16.

3. Then type a Linux kernel version(like "4.11.12" etc.) or type "enter" key(default is the latest version of 4.9.X series kernel), once installation succeed, it will automatically restart your server.

4. Log into your server and execute the shell again, type "2" then enter:

bash Tsunami_BBR.sh

5. If the end of script shows that "[Info] tcp_nanqinlang is installed ! [Info] tcp_nanqinlang is running !", the force modified BBR has been installed successfully.

6. This script also provide optimize TCP function.

Platform Support

• Debian 7+ ( i386 && amd64 )

Reference && Thanks

https://github.com/tcp-nanqinlang

Updates

• Disable expired DST Root CA X3 certificate authentication of Debian 9.
• In Debian 9, When wget files from https://kernel.ubuntu.com, system notices that'The certificate of ‘kernel.ubuntu.com’ is not trusted.' because 'The certificate of ‘kernel.ubuntu.com’ has expired.' since component 'ca-certificates' has been installed, the valid time of certificate of https://kernel.ubuntu.com is 2 month left, and the date of system time is corret, if this error continues, this bash will not execute. So I added '--no-check-certificate' to concerned resource.
• Fix downloading error.
• Sometimes I can't speculate the rules of kernel releases from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D, usually, the earlier version is corresponded to earlier release time strictly. But in v4.9.173, v4.9.179, v4.9.180 these three versions, the rule is invalid. If you visited the mentioned link above before June 6, v4.9.173 has been existed in 2~8 May, v4.9.179 should be existed before v4.9.180, but actually, the sequence is v4.9.173, v4.9.179, v4.9.180. I think it is really bad. To refer this situation, please view: https://web.archive.org/web/20190607005845/https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
• Search available 4.9.X series kernel and if press Enter key, the script will upgrade to this kernel automatically.
• fix bugs.