I have two ั20 and they both have the same issue.If i choose wpad mesh openssl instead of wpad-basic-mbedtls when i customize installed packages(firmware-selector.openwrt.org) i get soft reset after reboot.I manage to connect to my mesh network and everything works fine.But after power loss or reboot i get default settings.What can i do to solve this problem?
Youโre likely out of space.
ubus call system board
df -h
Usually 1MB+ openssl does not fit in 1-2MB space on 8MB device. Try wpad-mbedtls (you need wpad package with both - supplicant and hostap in mesh) which works on top of pre-supplied crypto framework.
1 Like
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.167",
"hostname": "OpenWrt",
"system": "MediaTek MT7628AN ver:1 eco:2",
"model": "TP-Link Archer C20 v4",
"board_name": "tplink,archer-c20-v4",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.5",
"revision": "r24106-10cc5fcd00",
"target": "ramips/mt76x8",
"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
}
}
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 4.8M 4.8M 0 100% /rom
tmpfs 27.9M 88.0K 27.9M 0% /tmp
tmpfs 27.9M 60.0K 27.9M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock4 704.0K 228.0K 476.0K 32% /overlay
overlayfs:/overlay 704.0K 228.0K 476.0K 32% /
Thank you!I really ran out of space/ I had these additional packages in my firmware-customizer:
iptables-mod-extra iptables-mod-nfqueue iptables-mod-filter iptables-mod-ipopt iptables-mod-conntrack-extra ipset curl
After leaving only wpad mesh openssl i dont have the issue anymore.
Get rid of iptables, nft needs only kmods in addition to cli tool
-- https://wiki.nftables.org/wiki-nftables/index.php/Supported_features_compared_to_xtables
1 Like