I'm sure this would be a pain with the documents mostly being in Korean, but considering it's a minions themed I felt a need to ask the community. While initially a meme it has been shown to be a capable device on its own
There is another device with 6E DVW-632(Kevin).
What is the question you want to ask?
While there's no explicit question in the body of that message, the implied question is: is it possible to add support for these two devices?
I believe the Wi-Fi 6E model (Kevin) has 512MB of RAM, and the Wi-Fi 6 model (Bob) has only 256MB.
I fear that'll be too little RAM for the ath11k drivers, as discussed in other threads I've seen about ath11k devices.
Any information on the chip it contains?
The FCC filings don't (yet?) have Internal Photos available, probably due to short-term confidentiality request, this may take a few more months...
There is only one additional device, VoIP Gateway there, but that one is not based on any popular Wireless SoC.
https://fccid.io/RZE
So, does anyone have a picture of the opened case, or even a bootlog? 
Someone on reddit just asked Davolink support about the chips 
https://www.reddit.com/r/HomeNetworking/comments/19bku93/comment/kitdu0x/
So Bob is based on Realtek, while Kevin is supposed to be IPQ508, i.e. the Qualcomm Max target. Waiting for mine to arrive, scheduled by Amazon to come mid March
The hardware is nice, but the stock firmware is garbage. It doesn't allow VLAN-to-SSID mapping, but it also doesn't even bother filter out VLAN-tagged packets, it just throws them all on the wifi regardless of VLAN tag. And lately, switching it into bridged mode makes the web UI fail (connection refused).
I'd love to see OpenWRT on it even if it can only ever support AP mode and has little RAM left to run software on the device itself.
I got some debugging info by opening the browser dev tools and going to the Log page, then selecting "edit and resend" on the log?type=5 query and changing the type value to 6, then clicking send.
It takes a while, but then it will ask to save a file. It'll be one long single line of JSON. If you run it through jq, it's a bit more readable.
The log is huge and full of mac address and SSID and passphrases, so it's probably safest for me not to paste it, but here's a bit from the top of the log:
================================================================================================================================
===== DV SNAPSHOT START ======================================================================================================
================================================================================================================================
Modules ==> info system process led dvmgmt dhcp dhcpc acs wireless wireless_stats easymesh ethernet network rstp ratelimit igmp HA smart_nat capwap poe radio_schedule captive_portal station_acl station_qos uci log aqphy conntrack mon5g kernel_dumpstack net_state basic_info,
Date ==> Mon Feb 24 15:10:14 PST 2025,
Uptime ==> 15:10:14 up 9 min, load average: 0.00, 0.36, 0.32,
========================================================================================================================
===== BASE INFO ======================================================================================================
========================================================================================================================
F/W Info ==> DVW-632X 1.00.16 r7739 (jenkins) 2024-09-25 09:22:14,
Project ==> current proejct is ENT 5018,
Board Model ==> Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1,
SOC Version ==> 1.1,
Kernel Version ==> Linux version 5.4.164 (jenkins@6bea0dd174a2) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 unknown)) #0 SMP PREEMPT Wed Sep 25 00:18:56 2024,
Kernel Command line ==> console=ttyMSM0,115200n8 ubi.mtd=rootfs root=mtd:ubi_rootfs rootfstype=squashfs rootwait loglevel=0 boot_version=00.00.01 boot_revision=2016.01-svn6050 swiotlb=1 coherent_pool=2M cnss2.bdf_integrated=0x24 cnss2.bdf_pci0=0x60 cnss2.bdf_pci1=0xb0,
Boot Version ==> CRM-BOOT.BF.3.3.1.1-00075,
Tz Version ==> CRM-TZ.WNS.4.0-00118,
NHSS Version ==> 0,
WCSS Version ==> WLAN.HK.2.8-01492-QCAHKSWPL_SILICONZ-1 v1,
=====================================================================================================================
===== SYSTEM ======================================================================================================
=====================================================================================================================
CPU info
--------
CPU Cores Online ==> 0,1,
CPU Scaling Governor: 0 ==> userspace,
CPU Current Frequency: 0 ==> 1008000,
CPU Available frequencies: 0 ==> 800000 1008000 1300000 ,
CPU Utilization stats
---------------------
Getting CPU utilization...
CPU Utilization: all ==> Used: 2.60% Idle: 96.80%,
CPU Utilization: 0 ==> Used: 3.42% Idle: 96.58%,
CPU Utilization: 1 ==> Used: 1.79% Idle: 97.01%,
NSS Current frequency ==> 1000000000,
NSS Available frequencies ==> ,
Memory Info
-----------
Total Memory ==> 406380 kB,
Free Memory ==> 136852 kB,
Available Memory ==> 165968 kB,
Free Memory (drop caches) ==> 202656 kB,
Available Memory ==> 184540 kB,
Reserved Memory: ==> Start 0x4A800000; End 0x4fd00000; Size 0x5500000,
APSS Watchdog Info
------------------
APSS Wdog status ==> "running",,
APSS Wdog timeout ==> 30,,
Interface details
-----------------
Lan Interface ==> ,
Lan device IP ==> 127.0.0.1,10.0.0.2,192.168.1.241,10.0.0.253,
Lan device MAC ==> 60:29:d5:xx:yy:z0,60:29:d5:xx:yy:z2,32:a9:a2:98:53:da,3e:fb:4a:c8:fd:ec,00:00:00:00:00:00,00:00:00:00:00:00,60:29:d5:xx:yy:z0,0a:29:d5:xx:yy:z0,0e:29:d5:xx:yy:z0,
Wan Interface ==> ,
Wan device IP ==> 127.0.0.1,10.0.0.2,192.168.1.241,10.0.0.253,
Wan device MAC ==> 60:29:D5:xx:yy:z0,60:29:D5:xx:yy:z2,32:a9:a2:98:53:da,3e:fb:4a:c8:fd:ec,00:00:00:00:00:00,00:00:00:00:00:00,60:29:D5:xx:yy:z0,0a:29:D5:xx:yy:z0,0e:29:D5:xx:yy:z0,
TZ Info
-------
OTHERS
------
JTAG ID ==> 0x101540E1,
Crash magic ==> 0x00000010,
tmpfs Size ==> tmpfs 198.4M 1.9M 196.5M 1% /tmp,
uboot env
---------
2nd_serial_num=0000000000000000
baudrate=115200
bootargs=console=ttyMSM0,115200n8
bootcmd=bootipq; bootswap
bootdelay=1
bootdelay_=0
eth1addr=00:11:22:33:44:56
eth2addr=00:11:22:33:44:55
eth3addr=00:11:22:33:44:56
ethact=eth0
fdt_high=0x4A400000
fdtcontroladdr=4a9d4004
fileaddr=441b3c48
filesize=22a0000
flash_type=11
ipaddr=172.20.1.1
loglevel=loglevel=0
machid=8040004
mtddevname=fs
mtddevnum=0
mtdids=nand0=nand0
mtdparts=mtdparts=nand0:0x2a00000@0x900000(fs),
partition=nand0,0
qpstserverip=172.20.1.99
serverip=172.20.1.99
soc_hw_version=20180101
soc_version_major=1
soc_version_minor=1
stderr=serial@78AF000
stdin=serial@78AF000
stdout=serial
lang_cc=US
ethaddr=60:29:D5:XX:YY:Z0
serial_num=DVW632ID<REDACTED>
I wonder how I could edit their config to enable dropbear?
package dropbear
config dropbear
option enable '0'
option Port '6022'
option PasswordAuth 'on'
option RootPasswordAuth 'on'
option IdleTimeout '600'