Yes. This is what you're looking for: https://github.com/infinitnet/lede-ar71xx-optimized-archer-c7-v2/blob/master/patches/812-enable-bbr-congestion-control.patch
1 Like
how can you test it compared to cubic or reno? lol
Keep in mind those benchmarks are not run on a consumer router but on the Google Cloud servers!
Like I said before BBR is made for servers not for routers.
1 Like
@Bartvz
Yep, I know, BBR was designed for datacenters and big network links, and now is availiable for everyone with the 4.9 kernel. Why not use it? Maybe I won't see a noticeable change but It's the CUBIC replacement, and if for one reason it makes my internet connection worse I'll just switch back to CUBIC, and I'll post here why.
in my statistics i dont see much of a change but whatever, its something new i'll go with it. Also anyone staying on top of those base files with new images? if i knew how to modify an image id make em daily. i just know how to use the make imagebuilder and the sdk a bit, not how to use binutils to setup everything else.
New image every 24 hours: https://github.com/infinitnet/lede-ar71xx-optimized-archer-c7-v2/tree/master/nightly
Isn't your router a "server" for your home network???
No, it's a router for your home network. BBR only makes sense when you run a VPN server or something like that on your router (then your router would be a "server") and then also only if you run it in TCP mode, which you shouldn't. I added BBR because it was requested and doesn't hurt - but it doesn't make a lot of sense on a router either.
1 Like
That is also my understanding, BBR can be useful whenever a TCP endpoint is active (Luci, SSH, Samba for the risk appetite?), and is neutral in other cases.
1 Like
Yes, exactly.
still a stable kernel for the most part right?
Why wouldn't it be? As you can see there are no complaints so far and I'm sure LEDE upstream wouldn't have moved to it if it wasn't. 
so does this mean the firmware isnt present?
[ 19.442078] fast-classifier: starting up
[ 19.446263] fast-classifier: registered
[ 19.567860] PPP generic driver version 2.4.2
[ 19.582486] PPP MPPE Compression module registered
[ 19.597922] NET: Registered protocol family 24
[ 19.609577] PPTP driver version 0.8.5
[ 19.678046] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
[ 19.683989] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 19.947606] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[ 19.958507] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 20.239680] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[ 20.285839] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[ 20.296752] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 20.377278] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 20.700529] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 20.709917] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 1
[ 20.722991] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00029 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 88595bb8
[ 20.768023] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[ 20.778627] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 20.832753] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[ 20.848853] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 21.924854] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[ 22.033406] ath: EEPROM regdomain: 0x0@sycohexor if I remember correctly that messages are just informative, the kernel is loading the correct firmware for your board.
If you see your radios up it means the firmware was loaded.
Also python 2.7.14 saying GCC 5.5.0 on linux2? does that mean it wasnt built in 7.2? maybe thats why im getting so many errors with trying to install modules.
@r00t, is there a chance you could also provide an optimized build for the C7 v4? Snapshots are already available and they work just fine, as far as I can tell. QCA9563 based, vs QCA9558 on the v2. I'd be more than willing to test one of your builds.
If not, could your work be adapted to that version? Thanks.
Hi,
I have currently Archer EU C7 v2 with 150427, but I see TP-Link has an upgrade to 170803.
Is there any point of upgrading original firmware before I install r00t's? Does the new version block unofficial builds?
PS: what's the IP and password for r00t's firmware?
hi,
where a find stock firmware 170803, em tp-link site only have 150725