Hello,
Recently encountered new CN router - Victure WR1200 (AC1200). From the look of luci web interface in PR video (https://www.youtube.com/watch?v=hRPpbwen4Ek) it's probably already using custom version of OpenWrt.
It would be nice to add official support for this router. It looks promising.
These look remarkably similar to the Cudy WR1300.
https://www.cudytech.com/productinfo/90088.html
Here's the development thread:
https://forum.openwrt.org/t/cudy-wr1300-support/67593/146
If you have one in your possession you may want to get in touch with @pyckle. He submitted the Cudy WR1300 build
The older versions have a CVE:
https://www.cvedetails.com/cve/CVE-2021-43284 that should be mitigated by an OpenWRT build.
Just be aware that this would be a betting game, until anyone has it on their desk, opened up and starts identifying SOC/ RAM/ flash/ wireless and starts working on it. If you want to be sure, go with an already supported device.
+1
You can zoom into the FCC id pdf's to ID some of the chips if you are considering risking purchase to investigate:
https://fccid.io/2AREL-WR1200/Internal-Photos/Internal-photos-4783102
If you want a sure thing, the Cudy WR1300 can probably be had for roughly the same amount of money.
Essentially I got this device for free (still waiting for delivery). And for obvious reasons I don't really want to use it with default firmware. I will post FCC ID and disassemble it as soon as i receive it. If it's actually Cudy inside then probably it shouldn't be hard to port OpenWrt. Thank you for information.
@Reese How did you get on?
I've got the same device and am concerned about the multiple CVE: https://research.nccgroup.com/2021/11/12/technical-advisory-multiple-vulnerabilities-in-victure-wr1200-wifi-router-cve-2021-43282-cve-2021-43283-cve-2021-43284/
this is quite promising, tried it ?
root:admin credentials, and despite the user best efforts to change the default admin account password from the web interface, the password for the root account will not be changed at the same time.2 out of 3 of these CVEs assumes the attacker have access to your LAN, if that's the case, those CVEs are the least of your problems. The 3rd is the default wifi password, which you should have changed already.
Hey, many thanks for your help!
I was able to SSH into it and change the root password in the usual way.
I'm still interested in getting a newer version of OpenWRT on there though for obvious reasons.
For reference for those googling this, here's both how I logged in from macOS and also what I saw when I did (firmware version 1.0.1):
ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -c 3des-cbc root@192.168.0.1
root@192.168.0.1's password:
BusyBox v1.23.2 (2020-10-29 16:05:21 CST) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
CHAOS CALMER (Chaos Calmer, unknown)
-----------------------------------------------------
* 1 1/2 oz Gin Shake with a glassful
* 1/4 oz Triple Sec of broken ice and pour
* 3/4 oz Lime Juice unstrained into a goblet.
* 1 1/2 oz Orange Juice
* 1 tsp. Grenadine Syrup
------------------------------------------------—--
root@WR1200-XXXX:~# passwd
Changing password for root
New password:
Retype password:
Password for root changed by root
start by posting dmesg, cat /proc/mtd, and if available, printenv.
for the fun of it, try doing an opkg update, too.
Not sure about posting the entire output of dmesg for fear of giving away potentially compromising info but the other two are below.
I'm unfamiliar with opkg but is there an equivalent of apt-get upgrade, and if there is, should I try it? 
root@WR1200-XXX:~# cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00010000 "ALL"
mtd1: 00030000 00010000 "Bootloader"
mtd2: 00010000 00010000 "Config"
mtd3: 00010000 00010000 "Factory"
mtd4: 00750000 00010000 "firmware"
mtd5: 005f11b1 00010000 "rootfs"
mtd6: 00110000 00010000 "rootfs_data"
mtd7: 00750000 00010000 "firmware2"
mtd8: 005f11b1 00010000 "rootfs2"
root@WR1200-XXXX:~# printenv
-ash: printenv: not found
root@WR1200-XXXX:~# opkg update
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7621/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_base.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7621/packages/base/Packages.sig.
Signature check passed.
there's nothing like that in dmesg, it gets posted all the time.
try opkg install uboot-envtools, that should give you printenv, assuming the package exists, and is installable.
root@WR1200-XXXX:~# opkg install uboot-envtools
Package agetty version 2.25.2-4 has no valid architecture, ignoring.
Package ar version 2.24-3 has no valid architecture, ignoring.
Package arptables version 0.0.4-1 has no valid architecture, ignoring.
Package atm-aread version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmaddr version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmdiag version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmdump version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmloop version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmsigd version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmswitch version 2.5.2-5 has no valid architecture, ignoring.
Package atm-atmtcp version 2.5.2-5 has no valid architecture, ignoring.
Package atm-awrite version 2.5.2-5 has no valid architecture, ignoring.
Package atm-bus version 2.5.2-5 has no valid architecture, ignoring.
Package atm-debug-tools version 2.5.2-5 has no valid architecture, ignoring.
Package atm-diagnostics version 2.5.2-5 has no valid architecture, ignoring.
Package atm-esi version 2.5.2-5 has no valid architecture, ignoring.
Package atm-ilmid version 2.5.2-5 has no valid architecture, ignoring.
Package atm-ilmidiag version 2.5.2-5 has no valid architecture, ignoring.
Package atm-lecs version 2.5.2-5 has no valid architecture, ignoring.
Package atm-les version 2.5.2-5 has no valid architecture, ignoring.
Package atm-mpcd version 2.5.2-5 has no valid architecture, ignoring.
Package atm-saaldump version 2.5.2-5 has no valid architecture, ignoring.
Package atm-sonetdiag version 2.5.2-5 has no valid architecture, ignoring.
Package atm-svc_recv version 2.5.2-5 has no valid architecture, ignoring.
Package atm-svc_send version 2.5.2-5 has no valid architecture, ignoring.
Package atm-tools version 2.5.2-5 has no valid architecture, ignoring.
Package atm-ttcp_atm version 2.5.2-5 has no valid architecture, ignoring.
Package atm-zeppelin version 2.5.2-5 has no valid architecture, ignoring.
Package authsae version 2014-06-09-8531ab158910a525d4bcbb3ad02c08342f6987f2 has no valid architecture, ignoring.
Package badblocks version 1.42.12-1 has no valid architecture, ignoring.
Package base-files version 157.2-r48532 has no valid architecture, ignoring.
Package binutils version 2.24-3 has no valid architecture, ignoring.
Package blkid version 2.25.2-4 has no valid architecture, ignoring.
Package block-mount version 2016-01-10-96415afecef35766332067f4205ef3b2c7561d21 has no valid architecture, ignoring.
Package br2684ctl version 2.5.2-5 has no valid architecture, ignoring.
Package busybox version 1.23.2-1 has no valid architecture, ignoring.
Package bzip2 version 1.0.6-2 has no valid architecture, ignoring.
Package ca-certificates version 20150426 has no valid architecture, ignoring.
Package cal version 2.25.2-4 has no valid architecture, ignoring.
Package cfdisk version 2.25.2-4 has no valid architecture, ignoring.
Package chat version 2.4.7-6 has no valid architecture, ignoring.
Package comgt-directip version 0.32-25 has no valid architecture, ignoring.
Package comgt-ncm version 0.32-25 has no valid architecture, ignoring.
Package comgt version 0.32-25 has no valid architecture, ignoring.
Package conntrack-tools version 1.4.2-1 has no valid architecture, ignoring.
Package curl version 7.40.0-3 has no valid architecture, ignoring.
Package debugfs version 1.42.12-1 has no valid architecture, ignoring.
Package dmesg version 2.25.2-4 has no valid architecture, ignoring.
Package dnsmasq-dhcpv6 version 2.73-1 has no valid architecture, ignoring.
Package dnsmasq-full version 2.73-1 has no valid architecture, ignoring.
Package dnsmasq version 2.73-1 has no valid architecture, ignoring.
Package dropbear version 2015.67-1 has no valid architecture, ignoring.
Package dropbearconvert version 2015.67-1 has no valid architecture, ignoring.
Package dumpe2fs version 1.42.12-1 has no valid architecture, ignoring.
Package e2freefrag version 1.42.12-1 has no valid architecture, ignoring.
Package e2fsprogs version 1.42.12-1 has no valid architecture, ignoring.
Package ead version 1 has no valid architecture, ignoring.
Package eapol-test version 2015-03-25-1 has no valid architecture, ignoring.
Package ebtables-utils version 2.0.10-4-3 has no valid architecture, ignoring.
Package ebtables version 2.0.10-4-3 has no valid architecture, ignoring.
Package fconfig version 20080329-1 has no valid architecture, ignoring.
Package fdisk version 2.25.2-4 has no valid architecture, ignoring.
Package filefrag version 1.42.12-1 has no valid architecture, ignoring.
Package findfs version 2.25.2-4 has no valid architecture, ignoring.
Package firewall version 2015-07-27 has no valid architecture, ignoring.
Package flock version 2.25.2-4 has no valid architecture, ignoring.
Package fstools version 2016-01-10-96415afecef35766332067f4205ef3b2c7561d21 has no valid architecture, ignoring.
Package fuse-utils version 2.9.3-2 has no valid architecture, ignoring.
Package gdb version 7.8-2 has no valid architecture, ignoring.
Package gdbserver version 7.8-2 has no valid architecture, ignoring.
Package genl version 4.0.0-1 has no valid architecture, ignoring.
Package getopt version 2.25.2-4 has no valid architecture, ignoring.
Package gre version 1-3 has no valid architecture, ignoring.
Package hostap-utils version 0.4.7-1 has no valid architecture, ignoring.
Package hostapd-common-old version 2015-03-25-1 has no valid architecture, ignoring.
Package hostapd-common version 2015-03-25-1 has no valid architecture, ignoring.
Package hostapd-mini version 2015-03-25-1 has no valid architecture, ignoring.
Package hostapd-utils version 2015-03-25-1 has no valid architecture, ignoring.
Package hostapd version 2015-03-25-1 has no valid architecture, ignoring.
Package hwclock version 2.25.2-4 has no valid architecture, ignoring.
Package iconv version 1.11.1-1 has no valid architecture, ignoring.
Package iftop version 1.0pre2-1 has no valid architecture, ignoring.
Package igmpproxy version 0.1-8 has no valid architecture, ignoring.
Package ip-bridge version 4.0.0-1 has no valid architecture, ignoring.
Package ip-full version 4.0.0-1 has no valid architecture, ignoring.
Package ip6tables-extra version 1.4.21-1 has no valid architecture, ignoring.
Package ip6tables-mod-nat version 1.4.21-1 has no valid architecture, ignoring.
Package ip6tables version 1.4.21-1 has no valid architecture, ignoring.
Package ip version 4.0.0-1 has no valid architecture, ignoring.
Package iperf-mt version 2.0.5-1 has no valid architecture, ignoring.
Package iperf3 version 3.0.11-1 has no valid architecture, ignoring.
Package iperf version 2.0.5-1 has no valid architecture, ignoring.
Package ipip version 1-1 has no valid architecture, ignoring.
Package ipset-dns version 2013-05-03-6be3afd819a86136b51c5ae722ab48266187155b has no valid architecture, ignoring.
Package ipset version 6.24-1 has no valid architecture, ignoring.
Package iptables-mod-account version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-chaos version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-cluster version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-clusterip version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-condition version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-conntrack-extra version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-delude version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-dhcpmac version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-dnetmap version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-extra version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-filter version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-fuzzy version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-geoip version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-hashlimit version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-iface version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-ipmark version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-ipopt version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-ipp2p version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-iprange version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-ipsec version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-ipv4options version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-led version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-length2 version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-logmark version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-lscan version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-lua version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-nat-extra version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-nflog version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-nfqueue version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-psd version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-quota2 version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-sysrq version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-tarpit version 2.5-1 has no valid architecture, ignoring.
Package iptables-mod-tee version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-tproxy version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-u32 version 1.4.21-1 has no valid architecture, ignoring.
Package iptables-mod-ulog version 1.4.21-1 has no valid architecture, ignoring.
Package iptables version 1.4.21-1 has no valid architecture, ignoring.
Package iptaccount version 2.5-1 has no valid architecture, ignoring.
Package iputils-arping version 20101006-1 has no valid architecture, ignoring.
Package iputils-clockdiff version 20101006-1 has no valid architecture, ignoring.
Package iputils-ping6 version 20101006-1 has no valid architecture, ignoring.
Package iputils-ping version 20101006-1 has no valid architecture, ignoring.
Package iputils-tftpd version 20101006-1 has no valid architecture, ignoring.
Package iputils-tracepath6 version 20101006-1 has no valid architecture, ignoring.
Package iputils-tracepath version 20101006-1 has no valid architecture, ignoring.
Package kmod-ide-aec62xx version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ide-core version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ide-generic-old version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ide-generic version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ide-it821x version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ide-pdc202xx version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ifb version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-igb version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iio-ad799x version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iio-core version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iio-dht11 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ikconfig version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-core version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-evdev version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-gpio-encoder version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-gpio-keys-polled version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-gpio-keys version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-joydev version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-matrixkmap version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-polldev version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-input-uinput version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ip6-tunnel version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ip6tables-extra version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ip6tables version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipip version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipoa version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipsec4 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipsec6 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipsec version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-account version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-chaos version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-cluster version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-clusterip version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-compat-xtables version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-condition version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-conntrack-extra version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-conntrack version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-core version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-delude version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-dhcpmac version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-dnetmap version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-extra version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-filter version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-fuzzy version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-geoip version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-hashlimit version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-iface version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-ipmark version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-ipopt version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-ipp2p version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-iprange version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-ipsec version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-ipset version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-ipv4options version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-led version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-length2 version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-logmark version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-lscan version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-lua version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-nat-extra version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-nat6 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-nat version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-nathelper-rtsp version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-nflog version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-nfqueue version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-psd version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-quota2 version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-sysrq version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-tarpit version 3.18.23+2.5-1 has no valid architecture, ignoring.
Package kmod-ipt-tee version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-tproxy version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-u32 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipt-ulog version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iptunnel4 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iptunnel6 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iptunnel version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipv6 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ipvti version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-isdn4linux version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-iwl-legacy version 3.18.23+2015-03-09-3 has no valid architecture, ignoring.
Package kmod-iwl3945 version 3.18.23+2015-03-09-3 has no valid architecture, ignoring.
Package kmod-iwl4965 version 3.18.23+2015-03-09-3 has no valid architecture, ignoring.
Package kmod-iwlagn version 3.18.23+2015-03-09-3 has no valid architecture, ignoring.
Package kmod-l2tp-eth version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-l2tp-ip version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-l2tp version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-leds-gpio version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-leds-pca963x version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-default-on version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-gpio version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-heartbeat version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-morse version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-netdev version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-netfilter version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-oneshot version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-timer version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-transient version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-ledtrig-usbdev version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-cordic version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc-ccitt version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc-itu-t version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc16 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc32c version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc7 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-crc8 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-lz4 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-lzo version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-raid6 version 3.18.23-1 has no valid architecture, ignoring.
Package kmod-lib-textsearch version 3.18.23-1 has no valid architecture, ignoring.
– cutting some stuff out to make it fit in a reply --
Package usbutils version 007-1 has no valid architecture, ignoring.
Package usign version 2015-05-08-cf8dcdb8a4e874c77f3e9a8e9b643e8c17b19131 has no valid architecture, ignoring.
Package uuidd version 2.25.2-4 has no valid architecture, ignoring.
Package uuidgen version 2.25.2-4 has no valid architecture, ignoring.
Package valgrind-cachegrind version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind-callgrind version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind-drd version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind-helgrind version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind-massif version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind-vgdb version 3.10.0-1 has no valid architecture, ignoring.
Package valgrind version 3.10.0-1 has no valid architecture, ignoring.
Package wall version 2.25.2-4 has no valid architecture, ignoring.
Package whereis version 2.25.2-4 has no valid architecture, ignoring.
Package wipefs version 2.25.2-4 has no valid architecture, ignoring.
Package wireless-tools version 29-5 has no valid architecture, ignoring.
Package wpa-cli version 2015-03-25-1 has no valid architecture, ignoring.
Package wpa-supplicant-mini version 2015-03-25-1 has no valid architecture, ignoring.
Package wpa-supplicant-p2p version 2015-03-25-1 has no valid architecture, ignoring.
Package wpa-supplicant version 2015-03-25-1 has no valid architecture, ignoring.
Package wpad-mesh version 2015-03-25-1 has no valid architecture, ignoring.
Package wpad-mini version 2015-03-25-1 has no valid architecture, ignoring.
Package wpad version 2015-03-25-1 has no valid architecture, ignoring.
Package wpan-tools version 0.4 has no valid architecture, ignoring.
Package wwan version 2014-07-17-1 has no valid architecture, ignoring.
Package xfs-fsck version 3.1.7-1 has no valid architecture, ignoring.
Package xfs-growfs version 3.1.7-1 has no valid architecture, ignoring.
Package xfs-mkfs version 3.1.7-1 has no valid architecture, ignoring.
Package zlib version 1.2.8-1 has no valid architecture, ignoring.
Unknown package 'uboot-envtools'.
Collected errors:
* opkg_install_cmd: Cannot install package uboot-envtools.
I will get my hands on this device today or tomorrow. I'm planning on trying to build OpenWrt for this router as soon as i have time. But it looks like it is already running OpenWrt, isn't it? The result of "opkg update" was successful in your case. So it should make the work easier, i think.
Regardless, i will look more into this in a few days. Nice to know that there is someone here with the same router.
Most home routers use it as base, or LEDE.
The identified cpu is identical to the Cudy WR1300.
Cudy WR1300 radios: MediaTek MT7603E, MediaTek MT7612E
Victure WR1200 radios MediaTek MT7603E, MediaTek MT7613E
I think the MT7612E uses the same firmware as the MT7613E.
My web search did not find the flash/ram sizes but they should be in the dmesg. The Cudy WR1300 uses 16mb/128bm.
Photos of each show 11 green LED on the front case. I think these are so close if the stock Cudy WR1300 /proc/mtd matches the Victure WR1200, you could probably use the OpenWRT Cudy WR1300 build as a template.
I looked and the parent company does not have firmware updates in spite of the CVE's that were referenced in an earlier post in this thread. In light of the poor support and CVE's, I would be hesitant to use unless I was able to flash OpenWRT. If you contact Victure (govicture.com) for any reason, I would put this front and center - their device will sell to knowledgeable users if they provide the same type of OpenWRT support that Cudy does.
Edit: Found the Cudy WR1300 dmesg:
https://pastebin.com/KucMuTL7
[ 2.516483] Creating 7 MTD partitions on "spi32766.0":
[ 2.521604] 0x000000000000-0x000000030000 : "u-boot"
[ 2.527835] 0x000000030000-0x000000040000 : "u-boot-env"
[ 2.534236] 0x000000040000-0x000000050000 : "factory"
[ 2.540253] 0x000000fd0000-0x000000fe0000 : "debug"
[ 2.546210] 0x000000fe0000-0x000000ff0000 : "backup"
[ 2.552139] 0x000000ff0000-0x000001000000 : "bdinfo"
[ 2.558102] 0x000000050000-0x000000fd0000 : "firmware"
[ 2.587157] 2 uimage-fw partitions found on MTD device firmware
[ 2.593085] 0x000000050000-0x0000001fbfec : "kernel"
[ 2.599061] 0x0000001fbfec-0x000000fd0000 : "rootfs"
Got the device. In addition to provided information earlier here is the result of "dmesg" (log)
So, the chip is different from what Cudy WR1300 uses. Or am i missing something? But it looks like hardware is supported. And information about 16/128 MB appears to be correct as well. I will try to build firmware in a few days
[38.572000] cut_through_token_list_init(): TokenList inited done!id_head/tail=0/4096
[38.588000] cut_through_token_list_init(): 84df9288,84df9288
[38.600000] cut_through_token_list_init(): TokenList inited done!id_head/tail=0/4096
[38.616000] cut_through_token_list_init(): 84df9298,84df9298
[38.628000] Hif Init Done!
[38.632000] ctl->txq = c17a5d98
[38.640000] ctl->rxq = c17a5da4
[38.644000] ctl->ackq = c17a5db0
[38.652000] ctl->kickq = c17a5dbc
[38.660000] ctl->tx_doneq = c17a5dc8
[38.664000] ctl->rx_doneq = c17a5dd4
[38.672000] mt7663_fw_prepare():using E2 ROM patch
[38.684000] mt7663_fw_prepare():using E2 firmware
[38.692000] Parsing patch header
[38.696000] Built date: 19050210037058b
[38.708000] Platform: 7663
[38.716000] HW/SW version: 0x6d702d31
[38.720000] Patch version: 0x3830328a
[38.728000] Target address: 0xdc000, length: 204032
[38.740000] patch is not ready && get semaphore success
[38.748000] Start address = 0xdc000, DL length = 204032, Data mode = 0x80000000
[38.764000] EventGenericEventHandler: CMD Success
[38.772000] MtCmdAddressLenReq:(ret = 0)
[38.784000] MtCmdPatchFinishReq
[38.792000] EventGenericEventHandler: CMD Success
[38.800000] release patch semaphore
[38.808000] WfMcuHwInit: Before NICLoadFirmware, check ICapMode = 0
[38.820000] Parsing CPU 0 fw tailer
[38.828000] Chip ID: 0x08
[38.832000] Eco version: 0x01
[38.840000] Region number: 0x03
[38.844000] Format version: 0x02
[38.852000] Format flag: 0x01
[38.856000] Ram version: 7663mp1827
[38.864000] Built date: 20190502100431
[38.872000] Common crc: 0x803140b2
[38.880000] Parsing tailer region 0
[38.888000] Decomp crc: 0x0
[38.892000] Decomp size: 0x0
[38.900000] Decomp block size: 0x0
[38.904000] Target address: 0x112c00
[38.912000] Download size: 276368
[38.920000] Feature set: 0x27
[38.924000] Parsing tailer region 1
[38.932000] Decomp crc: 0x0
[38.936000] Decomp size: 0x0
[38.944000] Decomp block size: 0x0
[38.952000] Target address: 0x2018400
[38.960000] Download size: 70656
[38.964000] Feature set: 0x07
[38.972000] Parsing tailer region 2
[38.976000] Decomp crc: 0x0
[38.984000] Decomp size: 0x0
[38.988000] Decomp block size: 0x0
[38.996000] Target address: 0x40100000
[39.004000] Download size: 14720
[39.012000] Feature set: 0x07
[39.016000] Release info: header tag = 0, total length = 72
[39.028000] tag 1, padding length = 2, tag length = 66
[39.040000] payload: t-neptune-main-mt7663-mt7626-1828-JEDI_7621_7613_AP-20190502100224
[39.056000] Start address = 0x112c00, DL length = 276368, Data mode = 0x8000000f
[39.068000] EventGenericEventHandler: CMD Success
[39.080000] MtCmdAddressLenReq:(ret = 0)
[39.088000] Start address = 0x2018400, DL length = 70656, Data mode = 0x8000000f
[39.104000] EventGenericEventHandler: CMD Success
[39.112000] MtCmdAddressLenReq:(ret = 0)
[39.124000] Start address = 0x40100000, DL length = 14720, Data mode = 0x8000000f
[39.136000] EventGenericEventHandler: CMD Success
[39.148000] MtCmdAddressLenReq:(ret = 0)
[39.156000] MtCmdFwStartReq: override = 0x1, address = 0x112c00
[39.208000] EventGenericEventHandler: CMD Success
[39.220000] MCU Init Done!
[39.224000] efuse_probe: efuse = 511161
[39.232000] RtmpChipOpsEepromHook::e2p_type=2, inf_Type=5
[39.240000] RtmpEepromGetDefault::e2p_dafault=1
[39.252000] RtmpChipOpsEepromHook: E2P type(2), E2pAccessMode = 2, E2P default = 1
[39.268000] NVM is FLASH mode. dev_idx [1] FLASH OFFSET [0x8000]
[39.284000] validFlashEepromID(): eeFlashId=7663, pAd->ChipID=7663
[40.892000] Country Region from e2p = 0
[40.900000] mt7663_antenna_default_reset() todo
[40.908000] RTMPReadTxPwrPerRate(444): Don't Support this now!
[40.920000] RcRadioInit(): DbdcMode=0, ConcurrentBand=1
[40.932000] RcRadioInit(): pRadioCtrl=858b6e38,Band=0,rfcap=3,channel=1,PhyMode=2 extCha=0xf
[40.948000] AntCfgInit(2930): Not support for HIF_MT yet!
[40.960000] MtReadPwrLimitTable: RF_LOCKDOWN Feature OFF !!!
[41.004000] MtReadPwrLimitTable: RF_LOCKDOWN Feature OFF !!!
[41.020000] EEPROM Init Done!
[41.024000] mt_mac_init()-->
[41.032000] mt_mac_pse_init(2963): Don't Support this now!
[41.040000] mt7663_init_mac_cr()-->
[41.048000] mt7663_init_mac_cr(): TMAC_TRCR0=0x82783c92
[41.060000] MtAsicSetMacMaxLen(1073): Not support for HIF_MT yet!
[41.072000] <--mt_mac_init()
[41.080000] CmdRxHdrTransBLUpdateRsp::EventExtCmdResult.u4Status = 0x0
[41.096000] CmdRxHdrTransBLUpdateRsp::EventExtCmdResult.u4Status = 0x0
[41.112000] CmdRxHdrTransBLUpdateRsp::EventExtCmdResult.u4Status = 0x0
[41.124000] MAC Init Done!
[41.128000] MT7663BBPInit():BBP Initialization.....
[41.140000] Band 0: valid=1, isDBDC=0, Band=2, CBW=1, CentCh/PrimCh=1/1, prim_ch_idx=0, txStream=2
[41.156000] Band 1: valid=0, isDBDC=0, Band=0, CBW=0, CentCh/PrimCh=0/0, prim_ch_idx=0, txStream=0
[41.176000] MT7663BBPInit() todo
[41.180000] PHY Init Done!
[41.188000] RtmpOSFileOpen(): Error 2 opening /etc/Wireless/iNIC/iNIC_ap_2G.dat
[41.200000] Open file "/etc/Wireless/iNIC/iNIC_ap_2G.dat" failed!
[41.216000] E2pAccessMode=2
[41.220000] SSID[0]=Victure-00A5-5G, EdcaIdx=0
[41.228000] SSID[1]=Victure-5G-Guest, EdcaIdx=0
[41.240000] SSID[2]=Victure-00A5-5G-va1, EdcaIdx=0
[41.248000] SSID[3]=Victure-00A5-5G-va2, EdcaIdx=0
[41.260000] cfg_mode=14
[41.264000] cfg_mode=14
[41.268000] cfg_mode=14
[41.272000] wmode_band_equal(): Band Equal!
[41.284000] [TxPower] BAND0: 100
[41.292000] profile: FragThreshold[0]=2346
[41.300000] APEdca0
[41.304000] APEdca1
[41.308000] APEdca2
[41.312000] APEdca3
[41.320000] APSDCapable[0]=0
[41.324000] APSDCapable[1]=0
[41.332000] APSDCapable[2]=0
[41.336000] APSDCapable[3]=0
[41.344000] APSDCapable[4]=0
[41.348000] APSDCapable[5]=0
[41.356000] APSDCapable[6]=0
[41.360000] APSDCapable[7]=0
[41.364000] APSDCapable[8]=0
[41.372000] APSDCapable[9]=0
[41.376000] APSDCapable[10]=0
[41.384000] APSDCapable[11]=0
[41.388000] APSDCapable[12]=0
[41.396000] APSDCapable[13]=0
[41.400000] APSDCapable[14]=0
[41.408000] APSDCapable[15]=0
[41.412000] default ApCliAPSDCapable[0]=0
[41.424000] read_itxbf: ITxBfEn = 1
[41.428000] read_itxbf: BSSID[0]
[41.436000] read_itxbf: MBSS[0] ITxBfEn = 1
[41.444000] read_itxbf: More BSSID[1]
[41.452000] read_itxbf: More MBSS[1] ITxBfEn = 1
[41.460000] read_itxbf: More BSSID[2]
[41.468000] read_itxbf: More MBSS[2] ITxBfEn = 1
[41.476000] read_itxbf: More BSSID[3]
[41.484000] read_itxbf: More MBSS[3] ITxBfEn = 1
[41.492000] read_itxbf: Common.ITxBfEn = 1
[41.500000] read_etxbf: ETxBfEnCond = 1
[41.508000] read_etxbf: BSSID[0]
[41.516000] read_etxbf: MBSS[0] ETxBfEnCond = 1
[41.524000] read_etxbf: More BSSID[1]
[41.532000] read_etxbf: More MBSS[1] ETxBfEnCond = 1
[41.540000] read_etxbf: More BSSID[2]
[41.548000] read_etxbf: More MBSS[2] ETxBfEnCond = 1
[41.560000] read_etxbf: More BSSID[3]
[41.568000] read_etxbf: More MBSS[3] ETxBfEnCond = 1
[41.604000] HT: WDEV[0] Ext Channel = ABOVE
[41.628000] LedConfigMethod = 1
[41.640000] tx_pwr_comp_init():NotSupportYet!
[41.648000] MtCmdSetMacTxRx:(ret = 0)
[41.656000] asic_bss_beacon_init(): NotSupportedFunc for this arch(HIF_MT)!
[41.668000] MtAsicSetChBusyStat(646): Not support for HIF_MT yet!
[41.684000] AsicDisableSync(): NotSupportedFunc for this arch(HIF_MT)!
[41.696000] MtAsicSetRalinkBurstMode(2219): Not support for HIF_MT yet!
[41.708000] MtAsicSetPiggyBack(590): Not support for HIF_MT yet!
[41.720000] WifiFwdSet::disabled=0
[41.728000] AsicSetPreTbtt(): NotSupportedFunc for this arch(HIF_MT)!
[41.740000] Main bssid = 00:00:00:00:00:00
[41.748000] AsicSetRxFilter(): NotSupportedFunc for this arch(HIF_MT)!
[41.760000] MtCmdSetMacTxRx:(ret = 0)
[41.768000] AsicSetRxFilter(): NotSupportedFunc for this arch(HIF_MT)!
[41.780000] MtCmdSetMacTxRx:(ret = 0)
[41.788000] INIT REDUCE TCP ACK, rai0
[41.796000] <==== mt_wifi_init, Status=0
[41.804000] TxBfModuleEnCtrl:It's not DBDC mode
[41.812000] MtCmdEDCCACtrl: BandIdx: 0, EDCCACtrl: 1
[41.828000] MSTA_Init (1) ---> ApCli
[41.836000] Register MSTA IF (apclii0) , pAd->MSTANum = 1
[41.848000] Caller: SetCommonHT+0xd8/0x198 [mt7663e]
[41.860000]
[41.860000] phy_mode=49, ch=0, wdev_type=2
[41.872000] ht_cap: ht_cap->HtCapInfo,
[41.876000] ldpc=1,ch_width=1,gf=0,sgi20=1,sgi40=1,tx_stbc=1,rx_stbc=1,amsdu_size=0
[41.892000] ht_cap: ht_cap->HtCapParm,
[41.900000] mdpu_density=0, ampdu_factor=3
[41.912000] WtcSetMaxStaNum: MaxStaNum:104, BssidNum:4, WdsNum:0, ApcliNum:1, MaxNumChipRept:24, MinMcastWcid:130
[41.932000] cp_support_is_enabled: set Driver CP_SUPPORT to Mode 2.
[41.944000] RTMP_COM_IoctlHandle -> CMD_RTPRIV_IOCTL_VIRTUAL_INF_UP
[41.956000] wifi_sys_open(), wdev idx = 0
[41.964000] wdev_attr_update(): wdevId0 =
[41.976000] [RcGetHdevByPhyMode]-- channel 0 fix for rdev fetching
[41.988000] [BuildChannelList] BandIdx = 0, PhyMode = 49, ChListNum = 9:
[42.004000] [RadarStateCheck] RD_NORMAL_MODE
[42.012000] phy_freq_adjust : no prim_ch value for adjust!
[42.024000] Caller: wlan_operate_init+0x108/0x178 [mt7663e]
[42.036000]
[42.036000] phy_mode=49, ch=0, wdev_type=1
[42.048000] ht_cap: ht_cap->HtCapInfo,
[42.056000] ldpc=1,ch_width=1,gf=0,sgi20=1,sgi40=1,tx_stbc=1,rx_stbc=1,amsdu_size=0
[42.072000] ht_cap: ht_cap->HtCapParm,
[42.080000] mdpu_density=5, ampdu_factor=3
[42.088000] AP inf up for ra_0(func_idx) OmacIdx=0
[42.096000] AsicRadioOnOffCtrl(): DbdcIdx=0 RadioOn
[42.108000] ApAutoChannelAtBootUp----------------->
[42.116000] ApAutoChannelAtBootUp: AutoChannelBootup[0] = 1
[42.128000] AsicSetRxFilter(): NotSupportedFunc for this arch(HIF_MT)!
[42.140000] MtCmdSetMacTxRx:(ret = 0)
[42.148000] [AutoChSelBuildChannelListFor5G] ChListNum5G = 9
[42.160000] AsicSwitchChannel(): 5G Channel:36, then must be Channel_Band:1 !!
[42.412000] AsicSwitchChannel(): 5G Channel:40, then must be Channel_Band:1 !!
[42.660000] AsicSwitchChannel(): 5G Channel:44, then must be Channel_Band:1 !!
[42.908000] AsicSwitchChannel(): 5G Channel:48, then must be Channel_Band:1 !!
[42.956000] rxNBDS Dect Pkts : 0 .
[42.960000] rxNBDS Drop Pkts : 0 .
[42.968000] TxSch:1
[43.172000] AsicSwitchChannel(): 5G Channel:149, then must be Channel_Band:1 !!
[43.420000] AsicSwitchChannel(): 5G Channel:153, then must be Channel_Band:1 !!
[43.668000] AsicSwitchChannel(): 5G Channel:157, then must be Channel_Band:1 !!
[43.916000] AsicSwitchChannel(): 5G Channel:161, then must be Channel_Band:1 !!
[44.164000] ApAutoChannelAtBootUp : Auto channel selection: Selected channel = 149, IsAband = 1
[44.180000] AutoChSelUpdateChannel(): Update channel for wdev for this band PhyMode = 49, Channel = 149
[44.200000] [RadarStateCheck] RD_NORMAL_MODE
[44.212000] AsicSwitchChannel(): 5G Channel:155, then must be Channel_Band:1 !!
[44.264000] ApAutoChannelAtBootUp<-----------------
[44.276000] [PMF]APPMFInit:: apidx=0, MFPC=0, MFPR=0, SHA256=0
[44.288000] Caller: SetCommonHT+0xd8/0x198 [mt7663e]
[44.296000]
[44.296000] phy_mode=49, ch=149, wdev_type=1
[44.308000] ht_cap: ht_cap->HtCapInfo,
[44.316000] ldpc=1,ch_width=1,gf=0,sgi20=1,sgi40=1,tx_stbc=1,rx_stbc=1,amsdu_size=0
[44.332000] ht_cap: ht_cap->HtCapParm,
[44.340000] mdpu_density=5, ampdu_factor=3
[44.348000] Enable 20/40 BSSCoex Channel Scan(BssCoex=1)
[44.356000] wifi_sys_linkup(), wdev idx = 0
[44.364000] wtc_acquire_groupkey_wcid: Found a non-occupied wtbl_idx:135 for WDEV_TYPE:1
[44.364000] LinkToOmacIdx = 0, LinkToWdevType = 1
[44.512000] bssUpdateBmcMngRate (BSS_INFO_BROADCAST_INFO), CmdBssInfoBmcRate.u2BcTransmit= 8192, CmdBssInfoBmcRate.u2McTransmit = 8192
[44.544000] UpdateBeaconHandler, BCN_UPDATE_INIT, OmacIdx = 0
[44.552000] MtCmdTxPowerSKUCtrl: fgTxPowerSKUEn: 0, BandIdx: 0
[44.564000] MtCmdTxBfBackoffCtrl: fgTxBFBackoffEn: 0, BandIdx: 0
[44.576000] MtCmdTxPowerPercentCtrl: fgTxPowerPercentEn: 0, BandIdx: 0
[44.592000] AsicSetTxStream(): NotSupportedFunc for this arch(HIF_MT)!
[44.604000] AsicSetRxStream(): NotSupportedFunc for this arch(HIF_MT)!
[44.616000] apidx 0 for WscUUIDInit
[44.624000] Generate UUID for apidx(0)
[44.956000] device rai0 entered promiscuous mode
[44.964000] br-lan: port 6(rai0) entered listening state
[44.976000] br-lan: port 6(rai0) entered listening state
[46.980000] br-lan: port 6(rai0) entered learning state
[48.984000] br-lan: topology change detected, propagating
[48.992000] br-lan: port 6(rai0) entered forwarding state
[49.016000] ESW: Link Status Changed - Port2 Link Down
[49.024000] ethernet: port2 linkdown(interrupt)
[49.040000] ESW: Link Status Changed - Port3 Link Down
[49.048000] ethernet: port3 linkdown(interrupt)
[52.200000] ESW: Link Status Changed - Port2 Link UP
[52.208000] ethernet: port2 linkup(interrupt)
[53.128000] ESW: Link Status Changed - Port3 Link UP
[53.140000] ethernet: port3 linkup(interrupt)
[92.744000] Device Instance
[92.748000] WDEV 00:
[92.748000] Name:ra0
[92.756000] Wdev(list) Idx:0
[92.764000] Idx:6
[92.768000] WDEV 01:
[92.768000] Name:ra1
[92.772000] Wdev(list) Idx:1
[92.780000] Idx:9
[92.784000] WDEV 02:
[92.784000] Name:ra2
[92.792000] Wdev(list) Idx:2
[92.796000] Idx:10
[92.800000] WDEV 03:
[92.800000] Name:ra3
[92.808000] Wdev(list) Idx:3
[92.812000] Idx:11
[92.820000] WDEV 04:
[92.820000] Name:apcli0
[92.824000] Wdev(list) Idx:4
[92.832000] Idx:12
[92.836000] WDEV 05:
[92.840000] WDEV 06:
[92.844000] WDEV 07:
[92.848000] WDEV 08:
[92.852000] WDEV 09:
[92.860000] WDEV 10:
[92.864000] WDEV 11:
[92.868000] WDEV 12:
[92.872000] WDEV 13:
[92.876000] WDEV 14:
[92.880000] WDEV 15:
[92.884000] WDEV 16:
[92.896000] Device Instance
[92.900000] WDEV 00:
[92.900000] Name:rai0
[92.908000] Wdev(list) Idx:0
[92.912000] Idx:7
[92.916000] WDEV 01:
[92.916000] Name:rai1
[92.924000] Wdev(list) Idx:1
[92.932000] Idx:13
[92.936000] WDEV 02:
[92.936000] Name:rai2
[92.940000] Wdev(list) Idx:2
[92.948000] Idx:14
[92.952000] WDEV 03:
[92.952000] Name:rai3
[92.960000] Wdev(list) Idx:3
[92.964000] Idx:15
[92.968000] WDEV 04:
[92.968000] Name:apclii0
[92.976000] Wdev(list) Idx:4
[92.984000] Idx:16
[92.988000] WDEV 05:
[92.992000] WDEV 06:
[92.996000] WDEV 07:
[93.000000] WDEV 08:
[93.004000] WDEV 09:
[93.008000] WDEV 10:
[93.016000] WDEV 11:
[93.020000] WDEV 12:
[93.024000] WDEV 13:
[93.028000] WDEV 14:
[93.032000] WDEV 15:
[93.036000] WDEV 16:
[93.040000] WDEV 17:
Here is more info about the device. By the way, is it possible to increase dmesg buffer size without sources of current firmware? Or maybe there is a way to log it to remote server so i could get all data (i know it works for regular syslog but not sure about this kernel log).
cat /proc/version
Linux version 3.10.108 (openwrt@blink.openwrt) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 unknown) ) #19 SMP Wed Oct 28 18:38:39 CST 2020
cat /proc/cpuinfo
system type : MT7621
machine : Unknown
processor : 0
cpu model : MIPS 1004Kc V2.15
BogoMIPS : 577.53
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
shadow register sets : 1
kscratch registers : 0
core : 0
VPE : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 1
cpu model : MIPS 1004Kc V2.15
BogoMIPS : 577.53
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
shadow register sets : 1
kscratch registers : 0
core : 0
VPE : 1
VCED exceptions : not available
VCEI exceptions : not available
processor : 2
cpu model : MIPS 1004Kc V2.15
BogoMIPS : 577.53
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
shadow register sets : 1
kscratch registers : 0
core : 1
VPE : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 3
cpu model : MIPS 1004Kc V2.15
BogoMIPS : 577.53
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented : mips16 dsp mt
shadow register sets : 1
kscratch registers : 0
core : 1
VPE : 1
VCED exceptions : not available
VCEI exceptions : not available
cat /proc/meminfo
MemTotal: 125748 kB
MemFree: 66952 kB
Buffers: 4956 kB
Cached: 14680 kB
SwapCached: 0 kB
Active: 8124 kB
Inactive: 13804 kB
Active(anon): 2408 kB
Inactive(anon): 84 kB
Active(file): 5716 kB
Inactive(file): 13720 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 2276 kB
Mapped: 1712 kB
Shmem: 200 kB
Slab: 18140 kB
SReclaimable: 2004 kB
SUnreclaim: 16136 kB
KernelStack: 584 kB
PageTables: 348 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 62872 kB
Committed_AS: 6136 kB
VmallocTotal: 1048372 kB
VmallocUsed: 16812 kB
VmallocChunk: 1020744 kB
cat /proc/mtd
dev: size erasesize name
mtd0: 01000000 00010000 "ALL"
mtd1: 00030000 00010000 "Bootloader"
mtd2: 00010000 00010000 "Config"
mtd3: 00010000 00010000 "Factory"
mtd4: 00750000 00010000 "firmware"
mtd5: 005f10e2 00010000 "rootfs"
mtd6: 00110000 00010000 "rootfs_data"
mtd7: 00750000 00010000 "firmware2"
mtd8: 005f10e2 00010000 "rootfs2"
cat /proc/partitions
major minor #blocks name
31 0 16384 mtdblock0
31 1 192 mtdblock1
31 2 64 mtdblock2
31 3 64 mtdblock3
31 4 7488 mtdblock4
31 5 6084 mtdblock5
31 6 1088 mtdblock6
31 7 7488 mtdblock7
31 8 6084 mtdblock8
cat /proc/cmdline
console=ttyS1,57600n8 root=/dev/mtdblock5 rootfstype=squashfs,jffs2
I built the image for this device. However i have no idea how to safely test it via ssh without flashing (i assume that for normal testing serial port access is required to load initramfs image via tftp).
Is there any way to test it without access to serial port?
No, the MT7613 is a bit of a red-headed step brother of the MT7615 Wave 2 802.11ac radio. So newer than the MT7612 (which is first wave), but with its own set of problems (like no DFS, and connection issues.
You'll need serial unfortunately. I'm not aware of MT7621 being able to accept initramfs images without boot loader access.
Thank you for information. This is unfortunate. I don't have TTL cable but even if i order one it's still really tricky to disassemble this router without breaking anything. All components are hidden behind the heat sink (plate) and it appears to be connected using single use plastic clamps.
And I'm not sure where serial port pins are located. There are some pictures of internal components on FCC website - https://fccid.io/2AREL-WR1200/Internal-Photos/Internal-photos-4783102.pdf
My best guess is this - https://imgur.com/ijCOvXw
Maybe someone with experience could check it out.