That is everything, just be aware that flow-offloading might not be totally stable yet (possibly causing spurious reboots, on all architectures) - so if you aren't scratching at the performance limits of your device, it might be better to keep it disabled.
thanks a lot
M
Tanks for reporting!
Luci package disappeared from config due to some symbol changes on master.
Rebuild and uploaded default image with luci included.
2 Likes
I've being using flow-offloading for months and never encountered any problem with my Archer C7 v2, I'd say it's already quite stable for end users point.
It gives issues in my wndr3800
But i got sqm / upnp and simpleadblock
I could test again in this latest build if its stable but usually it feels laggy and ends up hanging my internet eveeeentually
Edit:
installed the latests snapshot into a WNDR3700v4
it also has 4.14.90 kernel, everything works like this one here
it has offloading, been testing it, works fine too 
will try the 3800 later
New build:
Changelog:
- kernel version 4.14.91
- all ath79/generic changes till commit adc8b374e3818a3d71dde22de6d2b8a72ccaf540
- all package changes till commit 8cfbcfd7570a023dfac81f6678256dd8968b5c67
2019/01/08 (4.14.91-1-b7f863e0896642b15e1f9f4e8680800b)
Included features / packages (build with: -O2):
default build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
- luci
minimal build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
Supported device images:
- D-LINK DIR-825 B1
- NETGEAR WNDR3700
- NETGEAR WNDR3700 V2
- NETGEAR WNDR3800
- Phicomm K2T
- TP-Link Archer C7 V2
- TP-Link RE450 V2
- TP-Link WDR3600
- TP-Link WDR4300
- TP-Link WDR4900 V2
- TP-Link WR1043 V1
- TP-Link WR1043 V2
- TP-Link WR1043 V3
- TP-Link WR1043 V4
- TP-Link WR2543 V1
- Ubiquiti UniFi AC Pro
- Ubiquiti UniFi AC-Mesh
- Ubiquiti UniFi AC-Mesh Pro
- Ubiquiti UniFi AC-Lite
- Ubiquiti UniFi RouterStation Pro
Download 4.14.91 (default build)
Download 4.14.91(minimal build)
1 Like
Does this image support TP-Link Archer C7 V5?.
It seem its already ported to ath79/dts 18 days ago
qca9563_tplink_archer-c7-v5.dts
Thank you
Hi @Juppin,
I tried your build on my Archer C7 v2 and switched back to the one from r00t because of slower wireless speed. Difference is aprox. 10%. Nevertheless on both builds I never get more than:
tx bitrate: 6.0 MBit/s
rx bitrate: 650.0 MBit/s VHT-MCS 7 80MHz short GI VHT-NSS 2
I would expect at least 3 spatial streams ("VHT-NSS 3"), as both Router and my S8 are MIMO3x3. I googled arround and saw that others are reporting 3 streams even with older devices (S5). Please see "Attempting mesh on ath10k" . Is this an actual bug of the ATH10K or do you have higher link speeds on your router ?
On the other hand, the upload link speed never changed, it's only "6.0 MBit/s" on the 5GHZ channel.
Best regards.
Sorry dude i do not have a device with ath10k... My ath79 devices are ath9k only.
New build:
Changelog:
- add build for TP-Link Archer C7 V1
- add build for TP-Link Archer C7 V5
- kernel version 4.14.94
- all ath79/generic changes till commit 45a2771953fb351879c332105c8d270c6daed0a7
- all package changes till commit c059c283fed882885afb2c854ea9c55700df8d4c
2019/01/22 (4.14.94-1-1a8c5132c3487c0a39281ef696b5066e)
Included features / packages (build with: -O2):
default build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
- luci
minimal build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
Supported device images:
- D-LINK DIR-825 B1
- NETGEAR WNDR3700
- NETGEAR WNDR3700 V2
- NETGEAR WNDR3800
- Phicomm K2T
- TP-Link Archer C7 V1
- TP-Link Archer C7 V2
- TP-Link Archer C7 V5
- TP-Link RE450 V2
- TP-Link WDR3600
- TP-Link WDR4300
- TP-Link WDR4900 V2
- TP-Link WR1043 V1
- TP-Link WR1043 V2
- TP-Link WR1043 V3
- TP-Link WR1043 V4
- TP-Link WR2543 V1
- Ubiquiti UniFi AC Pro
- Ubiquiti UniFi AC-Mesh
- Ubiquiti UniFi AC-Mesh Pro
- Ubiquiti UniFi AC-Lite
- Ubiquiti UniFi RouterStation Pro
Download 4.14.94 (default build)
Download 4.14.94(minimal build)
1 Like
Hi,
I have a TP-Link Archer C5 v1.20. Some time ago, I have flashed TP-Link's Archer C7 v2 firmware because there was a much more recent version solving security issues. The router worked for a couple of days. After that, the 5 GHz wifi stopped working. Then I have flashed again OpenWRT's firmware, this time for Archer C7, and after a couple of months I have found this thread and I have flashed this firmware.
The 5 GHz still fails every 2 - 3 days. The last time it failed it was yesterday with the 4.14.91-1-b7f863e0896642b15e1f9f4e8680800b version. Looking in the kernel log, I have found the messages mentioned by RelentlesS on November 18th, 2018:
[ 12.529018] firmware ath10k!fwcfg-pci-0000:00:00.0.txt: firmware_loading_store: map pages failed
I have updated to 4.14.94-1-1a8c5132c3487c0a39281ef696b5066e and I get these messages:
[ 12.092037] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 12.378052] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/fwcfg-pci-0000:00:00.0.txt failed with error -2
[ 12.388759] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 12.529018] firmware ath10k!fwcfg-pci-0000:00:00.0.txt: firmware_loading_store: map pages failed
[ 12.538213] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
[ 12.549093] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 12.799289] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[ 13.083719] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/ct-firmware-5.bin failed with error -2
[ 13.094870] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.184601] firmware ath10k!QCA988X!hw2.0!ct-firmware-5.bin: firmware_loading_store: map pages failed
[ 13.194222] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/ct-firmware-2.bin failed with error -2
[ 13.205370] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.375632] firmware ath10k!QCA988X!hw2.0!ct-firmware-2.bin: firmware_loading_store: map pages failed
[ 13.385254] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[ 13.396137] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.566927] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 13.576289] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
[ 13.587168] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.757602] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: firmware_loading_store: map pages failed
[ 13.766921] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
[ 13.777810] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.955897] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: firmware_loading_store: map pages failed
[ 13.965256] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
[ 13.976136] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.147436] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: firmware_loading_store: map pages failed
[ 14.159887] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 14.169270] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[ 14.181665] ath10k_pci 0000:00:00.0: firmware ver 10.1-ct-8x-__fW-022-1bbfa151 api 2 features wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT crc32 66e0dff7
[ 14.329912] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[ 14.340524] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.448630] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[ 14.457907] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 15.476384] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16 peers: 127 tid: 256
[ 15.493833] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
[ 15.500164] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424 sw-crypt: 0 ct-sta: 0'
[ 15.508310] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24616 iram: 26584'
[ 15.576397] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 2 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
Later, I get these lines:
[ 31.856956] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16 peers: 127 tid: 256
[ 31.874404] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
[ 31.880755] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424 sw-crypt: 0 ct-sta: 0'
[ 31.888931] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24616 iram: 26584'
[ 31.957432] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
[ 32.855854] ath10k_pci 0000:00:00.0: NOTE: Firmware DBGLOG output disabled in debug_mask: 0x10000000
I am not sure if the firmware was loaded successfully and I'll be back with a message if it fails again. Nevertheless, I am interested why the AC wifi card ends working (there's not even a carrier). The N one (2.4 GHz) keeps working after the AC one failed.
Best regards,
Alex.
Later edit: it seems like firmware-2.bin was loaded. The file is stored in /lib/firmware/ath10k/QCA988X/hw2.0/ and it is provided by the ath10k-firmware-qca988x-ct package. The firmware is provided by Candela Technologies and the version is 10.1.something. I went to the official page of the ath10k firmware page and there it is mentioned that the kernel 4.x requires at least 10.2. The ath10k-firmware-qca988x package provides that version of firmware. Could anyone enlighten me about the difference?
I just upgraded from LEDE 17.01.5 to the latest Ath79 build; my WDR4300 is responsible for pppoe. I noticed that my upload speed dropped from 10 mbit to 0.1 mbit when enabling flow-offloading. Additionally, with flow offloading enabled, my router's system load averaged above 3; with flow offloading disabled, my load average is closer to 0.1.
Clearly there is something going on here.
Is there some place I should enable flow offloading other than the 'defaults' section?
Thanks
Kernel 4.19 for ath79, at least for the WDR43xx, is pretty stable. I've been using it for some time. If you plan on having to host a million packages for ath79, you could safely bump the kernel version with some minor patches.
2.4Ghz Wifi on WNDR3800 is significantly slower than ar71xx. Test with speedtest, ar71xx can reach 10.5MB/s, while ath79 only has 6.5MB/s. I am sure 40mhz enabled.
How can I fix that? Thanks.
juppin,
The new stable version 18.06.2 seems not include ath79 into the binaries. Would you please be kind enough build ath79 with the stable version for us?
We appreciate for your dedication, and keep up the good work.
1 Like
The openwrt-18.06 branch doesn't contain (any) support for ath79, you either have to use master (snapshots) or wait for the next major release (19.0[123].0).
New build:
Changelog:
- kernel version 4.14.97
- all ath79/generic changes till commit 420376ab50b1e8ed7f6aea1f0211d9ab040303d9
- all package changes till commit e643653a491689fcd4b8c24af5dc1e4cf608bbec
2019/02/05 (4.14.97-1-5b6a3ca48474b7641d6db132ea53d731)
Included features / packages (build with: -O2):
default build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
- luci
minimal build:
- same packages as on openwrt snapshot / trunk builds
- support for ath9k dynack
Supported device images:
- D-LINK DIR-825 B1
- NETGEAR WNDR3700
- NETGEAR WNDR3700 V2
- NETGEAR WNDR3800
- Phicomm K2T
- TP-Link Archer C7 V1
- TP-Link Archer C7 V2
- TP-Link Archer C7 V5
- TP-Link RE450 V2
- TP-Link WDR3600
- TP-Link WDR4300
- TP-Link WDR4900 V2
- TP-Link WR1043 V1
- TP-Link WR1043 V2
- TP-Link WR1043 V3
- TP-Link WR1043 V4
- TP-Link WR2543 V1
- Ubiquiti UniFi AC Pro
- Ubiquiti UniFi AC-Mesh
- Ubiquiti UniFi AC-Mesh Pro
- Ubiquiti UniFi AC-Lite
- Ubiquiti UniFi RouterStation Pro
Download 4.14.97 (default build)
Download 4.14.97 (minimal build)
4 Likes
My connection is 1Gbps fiber, I may not noticed it before, the speed test I just done indicate the download speed (680Mbps) is significantly higher than upload speed (180Mbps or so).
The flow offloading is enabled, BTW. Any idea on what's going on? At some point, as I remembered, the upload speed was comparable to the download speed.
Flow-offloading is an optimization based on heuristics (identify packets belonging to a longer running connection, a flow, and treat them identically - by letting later packets bypass most of the netfilter code), these are likely to work better with downloads (single server, many related packets) than uploads. In general any ar71xx/ ath79 device is seriously underpowered to service a 1 GBit/s line, you need mvebu or x86 (or mt76 with hardware flow-offloading, if your firewalling needs are very simple) to cover this.
2 Likes
May I ask for a new model to include in the next build?
The GL-AR300M-NOR works without problems.
1 Like