At first I tried to find SQM settings on the router but seen there is no "System > Software" menu.
Can I get some help?
There's only one router in the world, or should we start guessing which one you've got ?
Try looking in the network menu tree instead.
If you actually have installed the sqm luci package.
Likely because you have no luci-app-package-manager included in the image.
Install that from SSH console, and you should get the menu item.
My apologies, I have filled the router make & model into the signup field and thought it is being displayed on my profile by default.
My router is TP-Link TD-W8969 V4.
Please forgive me.
I have tried it in console to install via opkg, but I failed to find the url.
Can you please guide me where to find the necessary package urls?
This device appears to be supported only as far as 19.07.10... so that's very EOL and unsupported. It also represents a serious security risk as there are many unpatched vulnerabilities.
You should really be getting a newer device, as this one is no longer supported.
That said, if you really want to use this device, first let's understand what firmware is actually on there.
Please connect via ssh and issue this command, then paste the output of that into the forum.
ubus call system board
below is the installed package list
root@OpenWrt:~# opkg list-installed
base-files - 1559-r24012-d8dd03c46f
bcm63xx-cfe - 2021-06-22-e5050f37-1
busybox - 1.36.1-1
ca-bundle - 20230311-1
cgi-io - 2022-08-10-901b0f04-21
dnsmasq - 2.90-2
dropbear - 2022.82-6
firewall4 - 2023-09-01-598d9fbb-1
fstools - 2023-02-28-bfe882d5-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2022-08-13-4c7b720b-2
hostapd-common - 2023-09-08-e5ccbfc6-7
iw - 5.19-1
iwinfo - 2023-07-01-ca79f641-1
jansson4 - 2.14-3
jshn - 2023-05-23-75a3b870-1
jsonfilter - 2024-01-23-594cfa86-1
kernel - 5.15.162-1-c5903f6150dc03188054f706688419b9
kmod-b43 - 5.15.162+6.1.97-1-1
kmod-bcma - 5.15.162-1
kmod-cfg80211 - 5.15.162+6.1.97-1-1
kmod-crypto-aead - 5.15.162-1
kmod-crypto-ccm - 5.15.162-1
kmod-crypto-cmac - 5.15.162-1
kmod-crypto-crc32c - 5.15.162-1
kmod-crypto-ctr - 5.15.162-1
kmod-crypto-gcm - 5.15.162-1
kmod-crypto-gf128 - 5.15.162-1
kmod-crypto-ghash - 5.15.162-1
kmod-crypto-hash - 5.15.162-1
kmod-crypto-hmac - 5.15.162-1
kmod-crypto-manager - 5.15.162-1
kmod-crypto-null - 5.15.162-1
kmod-crypto-rng - 5.15.162-1
kmod-crypto-seqiv - 5.15.162-1
kmod-crypto-sha512 - 5.15.162-1
kmod-gpio-button-hotplug - 5.15.162-3
kmod-lib-cordic - 5.15.162-1
kmod-lib-crc-ccitt - 5.15.162-1
kmod-lib-crc32c - 5.15.162-1
kmod-mac80211 - 5.15.162+6.1.97-1-1
kmod-nf-conntrack - 5.15.162-1
kmod-nf-conntrack6 - 5.15.162-1
kmod-nf-flow - 5.15.162-1
kmod-nf-log - 5.15.162-1
kmod-nf-log6 - 5.15.162-1
kmod-nf-nat - 5.15.162-1
kmod-nf-reject - 5.15.162-1
kmod-nf-reject6 - 5.15.162-1
kmod-nfnetlink - 5.15.162-1
kmod-nft-core - 5.15.162-1
kmod-nft-fib - 5.15.162-1
kmod-nft-nat - 5.15.162-1
kmod-nft-offload - 5.15.162-1
kmod-nls-base - 5.15.162-1
kmod-ppp - 5.15.162-1
kmod-pppoe - 5.15.162-1
kmod-pppox - 5.15.162-1
kmod-slhc - 5.15.162-1
kmod-usb-core - 5.15.162-1
kmod-usb-ehci - 5.15.162-1
kmod-usb-ledtrig-usbport - 5.15.162-1
kmod-usb-ohci - 5.15.162-1
kmod-usb2 - 5.15.162-1
libblobmsg-json20230523 - 2023-05-23-75a3b870-1
libc - 1.2.4-4
libgcc1 - 12.3.0-4
libiwinfo-data - 2023-07-01-ca79f641-1
libiwinfo20230701 - 2023-07-01-ca79f641-1
libjson-c5 - 0.16-3
libjson-script20230523 - 2023-05-23-75a3b870-1
liblucihttp-ucode - 2023-03-15-9b5b683f-1
liblucihttp0 - 2023-03-15-9b5b683f-1
libmbedtls12 - 2.28.8-1
libmnl0 - 1.0.5-1
libnftnl11 - 1.2.6-1
libnl-tiny1 - 2023-07-27-bc92a280-1
libpthread - 1.2.4-4
libubox20230523 - 2023-05-23-75a3b870-1
libubus20230605 - 2023-06-05-f787c97b-1
libuci20130104 - 2023-08-10-5781664d-1
libuclient20201210 - 2023-04-13-007d9454-1
libucode20230711 - 2024-07-11-1a8a0bcf-1
libustream-mbedtls20201210 - 2023-02-25-498f6e26-1
logd - 2022-08-13-4c7b720b-2
luci-app-firewall - git-24.067.01746-69867db
luci-base - git-24.086.45142-09d5a38
luci-light - git-23.024.33244-34dee82
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-24.111.76511-ff6b275
luci-mod-status - git-24.141.29354-5cfe7a7
luci-mod-system - git-24.067.01860-7a82b2f
luci-proto-ipv6 - git-24.086.45108-51aee90
luci-proto-ppp - git-24.135.44542-f1ec9c2
luci-theme-bootstrap - git-24.086.46634-1ffe078
mtd - 26
netifd - 2024-01-04-c18cc79d-2
nftables-json - 1.0.8-1
odhcp6c - 2023-05-12-bcd28363-20
odhcpd-ipv6only - 2023-10-24-d8118f6e-1
openwrt-keyring - 2022-03-25-62471e69-2
opkg - 2022-02-24-d038e5b6-2
ppp - 2.4.9.git-2021-01-04-4
ppp-mod-pppoe - 2.4.9.git-2021-01-04-4
procd - 2023-06-25-2db83655-2
procd-seccomp - 2023-06-25-2db83655-2
procd-ujail - 2023-06-25-2db83655-2
rpcd - 2023-07-01-c07ab2f9-1
rpcd-mod-file - 2023-07-01-c07ab2f9-1
rpcd-mod-iwinfo - 2023-07-01-c07ab2f9-1
rpcd-mod-luci - 20240305-1
rpcd-mod-rrdns - 20170710
rpcd-mod-ucode - 2023-07-01-c07ab2f9-1
swconfig - 12
ubox - 2022-08-13-4c7b720b-2
ubus - 2023-06-05-f787c97b-1
ubusd - 2023-06-05-f787c97b-1
uci - 2023-08-10-5781664d-1
uclient-fetch - 2023-04-13-007d9454-1
ucode - 2024-07-11-1a8a0bcf-1
ucode-mod-fs - 2024-07-11-1a8a0bcf-1
ucode-mod-html - 1
ucode-mod-math - 2024-07-11-1a8a0bcf-1
ucode-mod-nl80211 - 2024-07-11-1a8a0bcf-1
ucode-mod-rtnl - 2024-07-11-1a8a0bcf-1
ucode-mod-ubus - 2024-07-11-1a8a0bcf-1
ucode-mod-uci - 2024-07-11-1a8a0bcf-1
ucode-mod-uloop - 2024-07-11-1a8a0bcf-1
uhttpd - 2023-06-25-34a8a74d-2
uhttpd-mod-ubus - 2023-06-25-34a8a74d-2
urandom-seed - 3
urngd - 2023-11-01-44365eb1-1
usign - 2020-05-23-f1f65026-1
wireless-regdb - 2024.07.04-1
wpad-basic-mbedtls - 2023-09-08-e5ccbfc6-7
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.162",
"hostname": "OpenWrt",
"system": "bcm63xx/TD-W8968 (0x6318/0xB0)",
"model": "TP-Link TD-W8968 v3",
"board_name": "tplink,td-w8968-v3",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.4",
"revision": "r24012-d8dd03c46f",
"target": "bcm63xx/generic",
"description": "OpenWrt 23.05.4 r24012-d8dd03c46f"
}
}
The earlier statement appears to be incorrect...
That said, I'm not seeing your device as supported in 23.05, so I'm guessing the firmware did not come from the official project.
It is supported, though, in 24.10 (currently at RC7)
https://firmware-selector.openwrt.org/?version=24.10.0-rc7&target=bmips%2Fbcm6318&id=tp-link_td-w8968-v3
Keep in mind, though, that your device uses a broadcom chipset, which means that the DSL will not work at all and the wifi will be severely limited.. So, if you currently rely on either of those features, do not install official OpenWrt and instead stick with the firmware that is on there (presumably something from TP-Link).
See the info/warnings here:
https://openwrt.org/toh/tp-link/td-w8960n_v5?s[]=tp&s[]=link&s[]=td&s[]=w8968&s[]=v3
Thanks for the info and links, specially for the newest firmware.
For me, DSL is as dead and Wifi is ok as long it gives connectivity and isn't my source of connection to anything.
Will try upgrading sysimage via web interface.
Just to be clear, expect ~25Mbps max out of the wifi if you do install OpenWrt...
What is printed on the physical label of the device?
Well, in theory, it should work if you force it (do not keep settings). But there is a reasonable chance that it could brick the unit... so it depends on your risk tolerance and if this device has any use to you if you keep it as-is.
If you look at the sysupgrade error message in the screenshot, the error seems to be only be about changed tplink vs. tp-link in the device id. The router detail name seems to be the same.
Quite possible that forcing sysupgrade succeeds.
Running Successfully!
Thank you @psherman
Great!
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.