Do you have a list of the packages you do have installed and the build you are using?
Sure, here you go:
base-files - 1500-r21100-ffe91ca478
batctl-default - 2022.3-1
busybox - 1.35.0-4
ca-bundle - 20211016-1
ca-certificates - 20211016-1
curl - 7.86.0-3
dnsmasq-full - 2.87-15
dropbear - 2022.82-2
firewall4 - 2022-10-18-7ae5e14b-1
fstools - 2022-10-18-ee54c6bc-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2022-08-13-4c7b720b-1
hostapd-common - 2022-07-29-b704dc72-5.1
iw - 5.19-1
iwinfo - 2022-10-14-0496c722-1
jansson4 - 2.14-3
jshn - 2022-09-27-ea560134-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 5.10.149-1-e1f532bfbb52961ac0344ce95caf71f9
kmod-batman-adv - 5.10.149+2022.3-1
kmod-cfg80211 - 5.10.149+5.15.74-1-1
kmod-crypto-acompress - 5.10.149-1
kmod-crypto-aead - 5.10.149-1
kmod-crypto-ccm - 5.10.149-1
kmod-crypto-cmac - 5.10.149-1
kmod-crypto-crc32c - 5.10.149-1
kmod-crypto-ctr - 5.10.149-1
kmod-crypto-gcm - 5.10.149-1
kmod-crypto-gf128 - 5.10.149-1
kmod-crypto-ghash - 5.10.149-1
kmod-crypto-hash - 5.10.149-1
kmod-crypto-hmac - 5.10.149-1
kmod-crypto-lib-chacha20 - 5.10.149-1
kmod-crypto-lib-chacha20poly1305 - 5.10.149-1
kmod-crypto-lib-curve25519 - 5.10.149-1
kmod-crypto-lib-poly1305 - 5.10.149-1
kmod-crypto-manager - 5.10.149-1
kmod-crypto-null - 5.10.149-1
kmod-crypto-rng - 5.10.149-1
kmod-crypto-seqiv - 5.10.149-1
kmod-crypto-sha256 - 5.10.149-1
kmod-gpio-button-hotplug - 5.10.149-3
kmod-hwmon-core - 5.10.149-1
kmod-leds-gpio - 5.10.149-1
kmod-lib-crc-ccitt - 5.10.149-1
kmod-lib-crc16 - 5.10.149-1
kmod-lib-crc32c - 5.10.149-1
kmod-lib-lzo - 5.10.149-1
kmod-mac80211 - 5.10.149+5.15.74-1-1
kmod-mt76-connac - 5.10.149+2022-10-01-72b87836-4
kmod-mt76-core - 5.10.149+2022-10-01-72b87836-4
kmod-mt7603 - 5.10.149+2022-10-01-72b87836-4
kmod-mt7615-common - 5.10.149+2022-10-01-72b87836-4
kmod-mt7615-firmware - 5.10.149+2022-10-01-72b87836-4
kmod-mt7615e - 5.10.149+2022-10-01-72b87836-4
kmod-mt7663-firmware-ap - 5.10.149+2022-10-01-72b87836-4
kmod-nf-conntrack - 5.10.149-1
kmod-nf-conntrack-netlink - 5.10.149-1
kmod-nf-conntrack6 - 5.10.149-1
kmod-nf-flow - 5.10.149-1
kmod-nf-ipt - 5.10.149-1
kmod-nf-log - 5.10.149-1
kmod-nf-log6 - 5.10.149-1
kmod-nf-nat - 5.10.149-1
kmod-nf-reject - 5.10.149-1
kmod-nf-reject6 - 5.10.149-1
kmod-nfnetlink - 5.10.149-1
kmod-nft-compat - 5.10.149-1
kmod-nft-core - 5.10.149-1
kmod-nft-fib - 5.10.149-1
kmod-nft-nat - 5.10.149-1
kmod-nft-offload - 5.10.149-1
kmod-ppp - 5.10.149-1
kmod-pppoe - 5.10.149-1
kmod-pppox - 5.10.149-1
kmod-slhc - 5.10.149-1
kmod-udptunnel4 - 5.10.149-1
kmod-udptunnel6 - 5.10.149-1
kmod-wireguard - 5.10.149-1
libblobmsg-json20220927 - 2022-09-27-ea560134-1
libc - 1.2.3-4
libcurl4 - 7.86.0-3
libgcc1 - 11.3.0-4
libgmp10 - 6.2.1-1
libiptext-nft0 - 1.8.8-1
libiptext0 - 1.8.8-1
libiptext6-0 - 1.8.8-1
libiwinfo-data - 2022-10-14-0496c722-1
libiwinfo20210430 - 2022-10-14-0496c722-1
libjson-c5 - 0.16-2
libjson-script20220927 - 2022-09-27-ea560134-1
liblua5.1.5 - 5.1.5-10
libmbedtls12 - 2.28.1-1
libmicrohttpd-no-ssl - 0.9.75-1
libmnl0 - 1.0.5-1
libnetfilter-conntrack3 - 1.0.9-2
libnettle8 - 3.8.1-2
libnfnetlink0 - 1.0.2-1
libnftnl11 - 1.2.3-2
libnghttp2-14 - 1.44.0-1
libnl-tiny2022-05-23 - 2022-05-23-28c44ca9-1
libopenssl1.1 - 1.1.1q-1
libpcre2 - 10.37-2
libpthread - 1.2.3-4
librt - 1.2.3-4
libubox-lua - 2022-09-27-ea560134-1
libubox20220927 - 2022-09-27-ea560134-1
libubus20220601 - 2022-06-01-2bebf93c-1
libuci-lua - 2021-10-22-f84f49f0-6
libuci20130104 - 2021-10-22-f84f49f0-6
libuclient20201210 - 2021-05-14-6a6011df-1
libucode20220812 - 2022-10-18-00af0650-1
libustream-openssl20201210 - 2022-01-16-868fd881-2
libxtables12 - 1.8.8-1
logd - 2022-08-13-4c7b720b-1
mtd - 26
netifd - 2022-08-25-76d2d41b-1
nftables-json - 1.0.5-2
openwrt-keyring - 2022-03-25-62471e69-2
opkg - 2022-02-24-d038e5b6-1
ppp - 2.4.9.git-2021-01-04-4
ppp-mod-pppoe - 2.4.9.git-2021-01-04-4
procd - 2022-07-17-ef5d3e36-1
procd-seccomp - 2022-07-17-ef5d3e36-1
procd-ujail - 2022-07-17-ef5d3e36-1
rpcd - 2022-09-21-8c852b65-1
rpcd-mod-file - 2022-09-21-8c852b65-1
rpcd-mod-iwinfo - 2022-09-21-8c852b65-1
ubi-utils - 2.1.5-1
ubox - 2022-08-13-4c7b720b-1
ubus - 2022-06-01-2bebf93c-1
ubusd - 2022-06-01-2bebf93c-1
uci - 2021-10-22-f84f49f0-6
uclient-fetch - 2021-05-14-6a6011df-1
ucode - 2022-10-18-00af0650-1
ucode-mod-fs - 2022-10-18-00af0650-1
ucode-mod-ubus - 2022-10-18-00af0650-1
ucode-mod-uci - 2022-10-18-00af0650-1
uhttpd - 2022-08-12-e3395cd9-2
urandom-seed - 3
urngd - 2020-01-21-c7f7b6b6-1
usign - 2020-05-23-f1f65026-1
wireguard-networking-wifi-custompackage - 3
wireguard-tools - 1.0.20210914-1
wireless-regdb - 2022.08.12-1
wpad-mesh-openssl - 2022-07-29-b704dc72-5.1
xtables-nft - 1.8.8-1
zlib - 1.2.12-4
Git branch used is Master, latest image build around 3 weeks ago. Dnsmasq 2.87 was self-added to be able to use nftset.
Device is connected via WAN and all traffic is routed via a wireguard tunnel with some exceptions for streaming services. wpad-mesh-openssl is installed alongside batman and batctl but I haven't used this router model in a mesh network as of yet.
1 Like
Thanks - I will try to build a similar setup and see how I get on.
I have just generated a snapshot build and flashed it and will see if that helps things at all.
I see that 22.03.3 has just been released and one of the fixes describes a “reboot loop” on some hardware (e.g. https://github.com/openwrt/openwrt/commit/1af58a2d39c4834bc84b853c2978d47572135af4). Is it possible that’s what we’re seeing with the LEDs?
It's possible, it looks like it's a specific fix for certain devices however - the build I put on yesterday was yesterday's snapshot so will be slightly more ahead of the 22.03.3 release and will likely have all the fixes of the release build. I am going to keep an eye on things over the week and will report back.
I haven't installed any add-ons, always factory. Simple router or bridge mode with WAN bridging. The devices always hung up after a few days, a problem with connecting to wifi or poor wifi coverage or passing packets through the copper port. The problem was bigger when more than 5 wifi devices were connected. Only physical reboot helped. Maybe Openwrt works stable on other routers I don't know. But on Archer C6U and C6 v3 it works tragically. Openwrt is misleading users by releasing STABLE software. In fact, the software is very unstable.
If the C6 in question is version 3, using MediaTek MT7621DAT; LAN loss/soft reboots? appears to be common with snapshots as of around January 2023.
May want to give the recent stable 22.03.3 a try.
Thanks - I am on Snapshot r21728-fc33c41c21 which is a little bit after 22.03.3's release. I'm at 2.5 days right now, had to reboot for an unrelated reason the other day so am currently monitoring it.
I tested today's snapshot r21775 a few minutes ago.
Encountered LAN loss/soft reboot twice within minutes, so reverted to 22.03.3
22.03.2 is stable for me on 25+ Archer C6v3 devices. Some with a handful wifi connections, others with a dozen or more. Some with RPs/APs connected, some without. If there were frequent connectivity issues I would have known one or two months ago. So I think there is something else wrong with your device or configurations. Can you post your wireless and network config with redacted information so I can compare those with what I am running?
I have been an Internet provider for 22 years. Standard to factory configuration without unnecessary magic. Earlier, I made a lot of identical configurations on the TL-WR841n, which worked great on LEDE BOOT for 200 days without power off, to this day, a lot still works on the network with the same configuration. The problem with the 841n may be low on memory because it would work even better with more WIFI users. .. With Archer C6 v3 with Openwrt I had a lot of negative feedback from customers so I stopped installing. I leave it on the factory TPLINK - I can't help it
I can confirm that I have the same issue with 22.03.3 as before.
Can I check, is everyone else using HW offload?
Yeah, totally understandable and it's really strange - there must be some differences that cause that behaviour. @timothyjward You have to enable it manually, right? If so, then no.
I’ve switched to SW acceleration. I should know whether things have improved in a week or so…
i think the problem is the mt7613 5ghz radio. it freeze the device, no dhcp, no static address no lan, sometime nothing work,only a reboot, i observed that on another device.
Hmm, interesting, I just noticed that I have kmod-mt7615 packages installed instead of kmod-mt7613. I didn't even check that since those packages were chosen by default when building my images. Maybe this is the difference between the devices in question here and leads to the top/flop behaviour.
no mt7613, look ,you have mt7663
Hi Guys, I see that you have a big problem to solve. I just wonder if you could spare few minutes for me and let me know how did you get openwrt 22.03.3 factory image loaded and boot up on Archer C6 v3.2? I found many instructions for version 2 but they don't work 
I see, so I can remove the 7615 packages I guess. Do you have info on the differences between the drivers for 5GHz (7613 vs 7663)? I wonder if this is the culprit and if in general the 7613 is preferable once these issues are fixed.
@MarekSuski
Did you install OpenWrt already on the device or does it still hold the TP-Link original software? If the latter, just connect your Laptop or PC to one of the LAN ports of the router. Then open 192.168.0.1 in your browser and set a login password. Afterwards you can log in with that password.
In the "Advanced" tab you will find a menu on the left where one entry says "system tools" (maybe I got those two entries switched). There is another entry "firmware upgrade/backup". Finally, you'll find the option to browse your Laptop or PC for a custom file to upload. Now choose your factory.bin and say "yes" when prompted by the overlay. The flash and reboot process takes roughly 3 minutes.
Afterwards, your router should have its on/off led and LAN led on, the wifi leds should be off. Your router now has the IP address 192.168.1.1 and you can connect to it via ssh. If you flash an image with LuCI as selected package, you will also be able to open the webinterface by typing 192.168.1.1 into your browser.