And doing these on dozens of different platforms with many different software versions and whatnot requires a significant amount of work.
Some vendors like ASUS actually integrate all their devices in the same firmware builder, similar to OpenWrt, so they can fix things ONCE and the fix will propagate on all the devices they still support.
But even that becomes too heavy after a few years, as the modern versions of the software with the fixed bugs are more and more different from the older versions you must copy the fix on.
That's why even with OpenWrt you must do a major version upgrade every few years if you want to use supported firmware that is receiving bug fixes.
If it was so easy to just port the bug fixes forever everyone would have done it in OpenWrt.
check if this firmware still has opkg package manager and the feed configuration.
can you try the following commands? Opkg is in /bin folder by default, and the other is the default feeds list file, where the links to download packages are.
ls /bin
cat /etc/opkg/distfeeds.conf
It is possible that you can download some packages from the same (old) OpenWrt version
Probably not the packages called kmod-something-something because this device is 99% not using a compatible kernel version, but if you do that Opkg will just show an error and stop, it should not break the router.
That should be good, but things you install will not appear in the interface you show in the screenshots from your phone since that is not the standard OpenWrt web interface.
I know how to install packages from console, but I don't know how to configure UPnP, I don't use it at home. So it is better to wait and ask to other people that know UPnP before proceding.
I edited the thread title so other people can come and help.
I copied both minidlna_1.1.5-3_mipsel_24kc.ipk and miniupnpc_1.9-1_mipsel_24kc.ipk to the routes tmp folder then tried opkg install and it did not work.
RX1800-2F17 login: root
Password:
BusyBox v1.25.1 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (17.01-SNAPSHOT, unknown)
\________\/ -----------------------------------------------------------
root@RX1800-2F17:~# cd /tmp
root@RX1800-2F17:/tmp# ls
TZ minidlna_1.1.5-3_mipsel_24kc.ipk
board.json miniupnpc_1.9-1_mipsel_24kc.ipk
cache mtk
dbg.log opkg-lists
dhcp.leases overlay
dnsmasq.d ping_result.log
etc resolv.conf
etc_ro resolv.conf.auto
extroot resolv.conf.ppp
hosts run
l1profile.sh shm
lib spool
lock state
locks sysinfo
log tmp
login_succ.flg upgrade.txt
login_user usr
luci-indexcache wan_connected
luci-modulecache
root@RX1800-2F17:/tmp# opkg install miniupnpc_1.9-1_mipsel_24kc.ipk
Installing miniupnpc (1.9-1) to root...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for miniupnpc:
* libminiupnpc *
* opkg_install_cmd: Cannot install package miniupnpc.
root@RX1800-2F17:/tmp# opkg install minidlna_1.1.5-3_mipsel_24kc.ipk
Installing minidlna (1.1.5-3) to root...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for minidlna:
* libexif * libjpeg * libsqlite3 * libffmpeg * libid3tag * libflac * libvorbis *
* opkg_install_cmd: Cannot install package minidlna.
root@RX1800-2F17:/tmp#
Given the effort you've already spent on this device, it would probably be easier to get this device ported to OpenWrt-proper, than trying to shoehorn OpenWrt packages into an incompatible proprietary environment. Especially for mt7621a+mt7915 that should be relatively straight forward.
My sense of this market segment is that a Chinese manufacturer is providing devices for re-branding and that there are 2 companies selling almost identical devices. Victure and Cudy.
The path to OpenWRT on a Cudy router entails installing Cudy's OpenWRT version and then upgrading it to a proper OpenWRT build.
What I wonder is if someone has compared the hex code dumps of the Cudy and Victure with the same hardware and whether Cudy's OpenWrt firmware could be used to flash a Victure device? Before attempting this I would have a backup of Victure's firmware and double check the hardware.
I'd also be more inclined to get a Cudy device outright, The slight increase in cost over Victure devices is worth the OpenWrt support and there should be some incentives for Cudy to continue support.
