Nope, stock firmware works just nice for 2 weeks, no restarts, no wifi problems (no wifi interruptions, no IPTV freezes, no router freezes, no stuttening on games, no loss of connection between my RPI3 improvised repeater (19.xx had a lot of them for me, Openwrt 15 up to 18 worked great for me (although at the time was for 100Mbps, YMMV)). The problem is not the hardware. (At the very least, not in my case, although the router is being used as a dumb access point, the heavywork is done on a RPI4).
QOS?, That's what you need when you have around 6-8 clients using the internet at the same time in the night, with at least 2 of them doing torrents (i am one, and at the same time using netflix, and doing some light M$VPN Sessions to the work), other uses a Kodi box using IPTV, other plays fallout 76 (WTF!!??... oh well, i don't judge... too much ) and there's another that does remote work using remote desktop clients. Not counting phones, or spotify, that the least of the problems. That's explain why they are paying more for the connection, but also the need for a better QOS manager, that's why, in my case, i use a rpi4, since i couldn't find a better router with OpenWRT support in my country. (Chile). Kinda bumpy supported nowadays, but better than what i had.
Then again, i think the OP would be more than happy using the 18.xx series for what he got. The Archer C7 is more than overkill at that speed. And at least from my experience, stay away from the 19.xx series. The headaches aren't worth it.
I just joined to this forum to let you know that i have an Archer C5 that i converted to a C7 and flashed Archer C7 V3 art eeprom backup years back and that i have zero issues with what you are describing here. Everything works as advertised.
I updated to the latest openwrt three days now but i was on various versions since
Hello, I created an account just so I can thank you for posting this! I have had nothing but headaches for the past month or so due to the 2.4ghz dropping out at least once a day. We have 6 or 7 smart home devices that do not support 5ghz and after jumping between gargoyle and openwrt, I was on the verge of purchasing a separate access point until I came across your post.
I have been running your custom build along with your watchdog script on my Archer C7 v2 for the past few days and I have not encountered a single dropped connection so far! I am so grateful that you were able to share your script and build and I really wanted you to know how appreciative I am, so once again thank you!!!
I've also made a comparison of my TP-Link Archer C7 v2 wireless account point being run
a) using the built-in eth0 switch (four lan ports) to
b) using an additional external switch in front of it (TP-Link SG108E v5.0)
My access point was running fine in scenario a) running multiple wireless SSIDs on radio0 and 1 plus the switching capability. But I had a feeling my gaming performance could be slightly better - it was a feeling by stomach not backed by technical observation and measurement.
I can now tell scenario b) runs better if you'd like to have maximum performance. As I do have a lot of IOT components, e.g. Google Chromecast, Home and Amazon Alexas, the TP-Link SG108E does seem to reduce some multicast load from the TP-Link Archer C7 v2. (measured by using tcpdump on the Wifi AP).
I've also did this improvement to enable IGMPv3 snooping on my Archer Openwrt:
uci set network.[interface_name].igmp_snooping=1
uci set network.[interface_name].igmp_v3=1
uci set network.[interface_name].multicast_querier=0
uci commit network
Source of info:
Thanks so much for sharing it! This image is suitable for the Archer C7 US version?
Uff I don't know the differences between EU and US models. So to be safe better do not use it, I've verified it working on my EU model but have no US model to test.
UPDATE: The US and EU images for the Archer C7 v2 are different. File compare gives the following output:
Here's a 19.07.4 build (with more packages, e.g. bash included) and EU/US variants for the C7v2 model. Link: https://drive.google.com/file/d/16ck-pmNGRlSRCwVT2QKxbBW4hsbtD0TP/view?usp=sharing
Wow nice! Thanks! I'll give it a try when possible! Just out of curiosity, did you find out what is different between the two images?
Yes, see my post above yours. The hex diff shows little difference, I guess it's because of the WiFi regulations that differ between countries?!
I am so glad to have come upon this post. @Catfriend1 I have loaded your image and I am still seeing a drop on 2.4ghz. Any help that anyone can provide is greatly appreciated. I am going crazy trying to figure this thing out. Devices are definitely close enough. Bandwidth is great when it is connected. My printer and doorbell keep disconnecting. It is causing the doorbell to drain the battery very quickly. I couldn't figure exactly how to add in the watchdog script as I am very new to this. Also should I be turning off the WAN6 interface as I am seeing contrasting information in some of the forums?
Device is Archer C7v2 Powered by LuCI openwrt-19.07 branch (git-20.319.48994-50b7ab5) / OpenWrt 19.07.4 r11208-ce6496d796
I keep seeing the below in the log about every 2-3 minutes but I am not sure what it means.
Thu Nov 19 17:37:47 2020 daemon.info dnsmasq-dhcp: DHCPOFFER(br-lan) 192.168.11.191 fc:6b:f0:c4:1a:d8
Thu Nov 19 17:37:47 2020 daemon.info dnsmasq-dhcp: DHCPREQUEST(br-lan) 192.168.11.191 fc:6b:f0:c4:1a:d8
Thu Nov 19 17:37:47 2020 daemon.info dnsmasq-dhcp: DHCPACK(br-lan) 192.168.11.191 fc:6b:f0:c4:1a:d8 DEFAULT
That is the ip address for my video doorbell. Heimvision HMB1.
@Catfriend1 I'm a little confused by your Target Profile: TP-Link Archer C7 v5
I'd have expected that to be v2 by the title of the tread...
Is that intentional? Do you get better results running the build for v5 on v2?
Or do you have both v2 and v5 and this is just the description for the wrong device?
I've done two builds. one for v2 and one for v5.
Did anyone try 19.07.5 official build yet? I'd like to know if there's again the ct driver in it and it's stability has increased because I don't know if ct driver got patches between the last and this release.
I installed the new version on my Archer C7 v2.
Default drivers are:
The stability seems to be not better than with .4
Seems to be the same version numbers that I have in 19.07.4. I believe I had changed things for ct-smallbuffers as an experiment, version numbers seem the same. Bummer, I was hoping for a bump in the new stable. I know there was a bump in master some weeks back, guess we have to run a snapshot for that...
Hi there, I was following along with you since topic opened on September. I had to struggle a little bit with the hardware, but know I got it working properly with the old driver set provided by @Catfriend1 firmware build - thanks a lot for compiling the custom image. Nevertheless I can stand, that the newly integrated firmware is still unstable and will cause my network performance to drain from 20MB/s to 1MB/s. (checked on V2 and V5 router)
In the end I am currently at around 20MB/s on a MacBook and around 30-35MB/s on my Fedora workstation. Peaks will go up to 50-75MB/s. The only worse thing I noticed, that voip will make troubles. (not topic of this thread will do another one later on)
Follow up to my post above with 19.07.5 build including mesh, batman-adv, bash and non-ct ath10k driver.
@Catfriend1 So, to try this out, I'd just download the file from your Google Drive and upload the firmware to my current 19.07.05 install of OpenWRT?