Do you know if, after following that wiki, I have to redo it every time I upgrade to the new package from this thread?
Backup your config beforehand.
To add to @cliobrando, there is more information available regarding how these patches and SQM work together here:
@DjiPi
I discovered that SQM and FastPath are mutually exclusive after a lot of testing.
If you want to use SQM to reduce bufferbloat just disable FP.
If you want to use FP to increase you network throughput don't enable SQM.
Yes, that's what the link I posted highlights effectively. However, depending on the patch used, it's either the patch or SQM that get prioritized from what I understand from it.
Thanks @r00t for the firmware! I've got it working great on my C7 V2. Looking forward to the next build.
Quick question: I have a PiHole set-up on my network which is also set up as a dnscrypt-proxy client. I would like to disable the dnscrypt client on the router and instead point my DNS queries to the PiHole. Can someone provide some help with doing this? I'm assuming this is more complex than simply deleting the dnscrypt related packages, since dnsmasq was reconfigured as part of the process of incorporating dnscrypt on the router.
Thanks!
What are the advantages to running "Pi-hole" over doing the dns based ad blocking on the router itself via the simple-adblock package already included in this firmware?
@shunjou There are quite a few advantages; logging, much more useful interface, easier import/export of blocklists, updates to the core program. The primary advantage for me personally, however, is that I have an existing, working, fully configured PiHole setup that I would like to continue to use.
Hello r00t,
good firmware. but I had issues with 5GHz. wlan0 wouldnt come up. I dived into it and found these errors:
root@LEDE:~# dmesg | grep ath10k [ 35.335684] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0 [ 35.554336] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2 [ 35.565226] ath10k_pci 0000:01:00.0: Falling back to user helper [ 35.618789] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed [ 35.628128] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2 [ 35.638653] ath10k_pci 0000:01:00.0: Falling back to user helper [ 42.217086] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2 [ 42.227957] ath10k_pci 0000:01:00.0: Falling back to user helper [ 42.301554] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed [ 42.625982] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000 [ 42.635382] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 1 [ 42.648443] 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 [ 42.708456] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2 [ 42.719066] ath10k_pci 0000:01:00.0: Falling back to user helper [ 42.772180] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed [ 42.788303] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 [ 43.862594] 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 root@LEDE:~#
I checked and firmware-6.bin was not present:
root@LEDE:/lib/firmware/ath10k/QCA988X/hw2.0# ls -al drwxr-xr-x 2 root root 54 Dec 8 12:53 . drwxr-xr-x 3 root root 28 Dec 8 12:53 .. -rw-r--r-- 1 root root 2116 Dec 8 12:53 board.bin -rw-r--r-- 1 root root 246360 Dec 8 12:53 firmware-5.bin
Created a symlink for testing and after a reboot 5GHz was up and running:
root@LEDE:/lib/firmware/ath10k/QCA988X/hw2.0# ln -s firmware-5.bin firmware-6.bin root@LEDE:/lib/firmware/ath10k/QCA988X/hw2.0# ls -al drwxr-xr-x 1 root root 0 Jan 14 18:48 . drwxr-xr-x 1 root root 0 Dec 8 12:53 .. -rw-r--r-- 1 root root 2116 Dec 8 12:53 board.bin -rw-r--r-- 1 root root 246360 Dec 8 12:53 firmware-5.bin lrwxrwxrwx 1 root root 14 Jan 14 18:48 firmware-6.bin -> firmware-5.bin
I dont know much about the boards and specific. Just wanted to mention it, in case someone has the same issue....
Cheers
Alex
PS: I still got some errors, but as long as its working I will keep it. Dont have much time to dive into it:
root@LEDE:~# dmesg | grep ath10k [ 19.309720] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0 [ 19.533547] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2 [ 19.544429] ath10k_pci 0000:01:00.0: Falling back to user helper [ 19.597884] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed [ 19.995107] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000 [ 20.004512] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 1 [ 20.017590] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00029 api 6 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 88595bb8 [ 20.062620] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2 [ 20.073231] ath10k_pci 0000:01:00.0: Falling back to user helper [ 20.127339] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed [ 20.143467] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 [ 21.229556] 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
firmware-6.bin is not necessary, it doesn't even exist for QCA998x yet, ath10k falls back transparently to firmware-5.bin instead - a symlink is not necessary.
But if I remove it and reboot wlan0 will not come up. I saw only firmware-5 on GitHub and -6 only for 990x I believe. As said, I am a noob, just mentioned it...
Hi @r00t,
Have you seen [Solved] Archer C7 V2.0 Overclock?
Do you think will be great to implement in your optimized firmware?
Thanks,
1 Like
it would be very interesting to translate and put in the FW the option of installing the modified U-boot and allowing to do or not overclocking and according to will the user.
1 Like
So lately my 5G was turning off until I switched it to 20 instead of 40 width and now my internet goes down until I either reconnect "wan" or reboot my router.
Has anyone else been getting this?
LOG
Wed Jan 17 16:02:46 2018 daemon.err uhttpd[2210]: cat: write error: Broken pipe
Wed Jan 17 16:03:05 2018 daemon.notice netifd: wan (1809): udhcpc: received SIGTERM
Wed Jan 17 16:03:05 2018 daemon.notice netifd: Interface 'wan' is now down
Wed Jan 17 16:03:05 2018 kern.info kernel: [57559.720184] eth0: link down
Wed Jan 17 16:03:05 2018 daemon.err miniupnpd[2944]: Failed to get IP for interface eth0
Wed Jan 17 16:03:05 2018 daemon.warn miniupnpd[2944]:
SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Wed Jan 17 16:03:05 2018 daemon.notice netifd: Interface 'wan' is disabledWhat ashame that a good build like this only works for 1 revision of the same router when v4 is not much different and being widely sold currently.Looks like i'm not the only person looking for a v4 revision.. frustrating.I just bought this router today hoping to use this but seems I cannot.
@Chrisnetika
The difference is the flash chip: V2-> 16MB, V4 -> 8MB
You can replace the flash chip and use the V2 build.
Buy: Flash chip link
Video: How to replace
I can confirm it works.
why does wikidev list the v4 with 16mb flash then?
On top of that all the official firmware files on the tp-link website for v4 are over 14mb in size, not sure where your getting your info but from my research the only difference is the wireless chipsets and both are supported in Lede.
Perhaps the reason is this builds goes off latest stable and not snapshot, I understand v4 support was added in merely few days after latest stable.
Sorry,
You are right V4 has 16MB flash. I was confusing routers, in my case I have a WDR7500 V5 and I converted it to an Archer C7 V2 replacing the flash chip.
WDR7500 v2 v3 v4 and v5 can be converted to Archer C7 v2 because they use the same HW, but seems that C7 v4 isn't the same HW as V2.
Archer C7 V4 HW= QCA9561+QCA9888
Archer C7 V2 HW= QCA9558+QCA9880
That's why this build will not work for you.
Yes that is the difference from the "not much difference" part i'm referring to.I do see that it eventually got the needed support in LEDE trunk unfortunately it seems this build(and many others) use the stable releases.It is all good, my frustration is at myself for not knowing about the different hardware revisions before going to walmart to buy it not knowing that version I was getting was no good.Sometime this coming week i'm gonna return it and looking to get Netgear R7800 which seems way better and plenty support here for it and no different rev nonsense.. for now anyway.I am glad to see that there is life on LEDE forums, much welcome change from openwrt forums which in it good days was just as lively.I always look forward to see different builds made by the community.
Hi, i can confirm this behaviour.
Getting the same thing since the last update. Is there a solution to fix this?
Otherwise a great release. THx @root