Xiaomi Mi Router 4A Gigabit Edition (R4AG/R4A Gigabit) -- fully supported and flashable with OpenWRTInvasion

boliva · October 22, 2020, 11:43pm

Hi everyone,

I received a Mi Router 4A Gigabit (global edition) a couple of days ago and first thing I tried was to put OpenWRT in it. By using the OpenWRTInvasion exploit I managed to gain shell access, but after flashing the firmware the router was bricked. I then unbricked it via bootp/tftp and installed the original firmware (in Chinese), and tried to reflash it again with the same result (I tried a few different releases). Following the @araujorm notes I was able to flash the initramfs version of the firmware successfully, however after booting up the router I see no kernel partition on the mtd device.

Below is a portion of dmesg with the relevant info:

[    7.081689] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys error
[    7.089085] spi-mt7621 1e000b00.spi: sys_freq: 220000000
[    7.104118] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    7.109003] 8 fixed-partitions partitions found on MTD device spi0.0
[    7.115326] Creating 8 MTD partitions on "spi0.0":
[    7.120118] 0x000000000000-0x000000030000 : "u-boot"
[    7.126259] 0x000000030000-0x000000040000 : "u-boot-env"
[    7.132564] 0x000000040000-0x000000050000 : "Bdata"
[    7.138390] 0x000000050000-0x000000060000 : "factory"
[    7.144314] 0x000000060000-0x000000070000 : "crash"
[    7.150177] 0x000000070000-0x000000080000 : "cfg_bak"
[    7.156130] 0x000000080000-0x000000180000 : "overlay"
[    7.162168] 0x000000180000-0x000001000000 : "firmware"

The output from cat /proc/mtd:

root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "Bdata"
mtd3: 00010000 00010000 "factory"
mtd4: 00010000 00010000 "crash"
mtd5: 00010000 00010000 "cfg_bak"
mtd6: 00100000 00010000 "overlay"
mtd7: 00e80000 00010000 "firmware"

It's worth noting that, when accessing the original firmware via the exploit the mtd device lists 11 different partitions, with the one labeled OS1 being mtd8, which is not listed when booting into OpenWRT initramfs (I don't have the output in a text format but I can post a picture if needed).

Any help would be greatly appreciated.

araujorm · October 23, 2020, 12:30am

You mean the default IP? It's 192.168.1.1

For a tutorial on setting up try this @hoddy video:

araujorm · October 23, 2020, 12:51am

@boliva,

Looks like some flash chips are picky with the alignments, and that should be your router's situation. Or it could be something on certain devices bootloader, I'm not sure.

Please revert to the original firmware and try my latest build, the one that was released a few hours ago. It has a new setting that should hopefully solve the issue. I never had that issue, but a few have had and I really hope this finally solves it...

If it doesn't, try going to @db260179 thread see a few posts above and see if his builds work with you. He's been working on a solution and he was the one that suggested that the blocksize parameter I applied on the build released tonight can be the solution, and since he could reproduce the problem on his hardware, he has been working on it. His insight on this matter is better than mine.

Worst case, try a snapshot build, is not as stable but many people say it works for them...

Edit: meanwhile I'm going to add a warning on those notes you mentioned that it was an experimental solution, but at this point it doesn't seem to be of much help

boliva · October 23, 2020, 1:00am

Hi @araujorm, thank you for your quick response. I did try your latest build a few hours ago and the same thing happened. I will try the one you mention from @db260179 and will keep you updated.

Best,

Carlos.

araujorm · October 23, 2020, 1:45am

@boliva

I took a look at my router's mtd table and I think I may have been misunderstanding it.

dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "Bdata"
mtd3: 00010000 00010000 "factory"
mtd4: 00010000 00010000 "crash"
mtd5: 00010000 00010000 "cfg_bak"
mtd6: 00100000 00010000 "overlay"
mtd7: 00e80000 00010000 "firmware"
mtd8: 001de405 00010000 "kernel"
mtd9: 00ca1bfb 00010000 "rootfs"
mtd10: 00950000 00010000 "rootfs_data"

Someone correct me if I'm wrong, but the kernel, rootfs and rootfs_data are contained in the firmware (mtd7) partition, being the kernel at offset 0 of it. I copied to my machine and ran binwalk, looks like so:

[rod@zoo tmp]$ ls -l mtd*
-rw-r--r-- 1 rod rod 15204352 Oct 23 02:27 mtd7
-rw-r--r-- 1 rod rod  1958917 Oct 23 02:27 mtd8
-rw-r--r-- 1 rod rod 13245435 Oct 23 02:27 mtd9
[rod@zoo tmp]$ binwalk mtd7

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             uImage header, header size: 64 bytes, header CRC: 0x445AAE3E, created: 2020-09-06 16:19:39, image size: 1958853 bytes, Data Address: 0x80001000, Entry Point: 0x80001000, data CRC: 0x17A6FC50, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS OpenWrt Linux-4.14.195"
64            0x40            LZMA compressed data, properties: 0x6D, dictionary size: 2097152 bytes, uncompressed size: 6270088 bytes
1958917       0x1DE405        Squashfs filesystem, little endian, version 4.0, compression:xz, size: 3425314 bytes, 1643 inodes, blocksize: 262144 bytes, created: 2020-09-06 16:19:39
5439488       0x530000        JFFS2 filesystem, little endian

[rod@zoo tmp]$ binwalk mtd8

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             uImage header, header size: 64 bytes, header CRC: 0x445AAE3E, created: 2020-09-06 16:19:39, image size: 1958853 bytes, Data Address: 0x80001000, Entry Point: 0x80001000, data CRC: 0x17A6FC50, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS OpenWrt Linux-4.14.195"
64            0x40            LZMA compressed data, properties: 0x6D, dictionary size: 2097152 bytes, uncompressed size: 6270088 bytes

[rod@zoo tmp]$ binwalk mtd9

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             Squashfs filesystem, little endian, version 4.0, compression:xz, size: 3425314 bytes, 1643 inodes, blocksize: 262144 bytes, created: 2020-09-06 16:19:39
3480571       0x351BFB        JFFS2 filesystem, little endian

Also, take a look at when the router boots, taken from dmesg:

[    2.504973] Creating 8 MTD partitions on "spi0.0":
[    2.509749] 0x000000000000-0x000000030000 : "u-boot"
[    2.515688] 0x000000030000-0x000000040000 : "u-boot-env"
[    2.521789] 0x000000040000-0x000000050000 : "Bdata"
[    2.527561] 0x000000050000-0x000000060000 : "factory"
[    2.533478] 0x000000060000-0x000000070000 : "crash"
[    2.539278] 0x000000070000-0x000000080000 : "cfg_bak"
[    2.545309] 0x000000080000-0x000000180000 : "overlay"
[    2.551212] 0x000000180000-0x000001000000 : "firmware"
[    2.557481] 2 uimage-fw partitions found on MTD device firmware
[    2.563384] Creating 2 MTD partitions on "firmware":
[    2.568404] 0x000000000000-0x0000001de405 : "kernel"
[    2.574298] 0x0000001de405-0x000000e80000 : "rootfs"
[    2.580117] mtd: device 9 (rootfs) set to be root filesystem
[    2.585898] 1 squashfs-split partitions found on MTD device rootfs
[    2.592072] 0x000000530000-0x000000e80000 : "rootfs_data"

So if I'm interpreting this correctly, the notes on my mir4ag-19.07-20200722 release were almost correct... except that since it doesn't identify the flashed initramfs image on the "firmware" partition as a "multiple sub-partition" one (since it is not a squashfs sysupgrade image yet), we should flash the sysupgrade image on that "firmware" mtd partition. I now think that the correct command on the last part of the notes should be:

mtd -e firmware -r write openwrt-ramips-mt7621-xiaomi_mir3g-v2-squashfs-sysupgrade.bin firmware

However I don't want to brick your router permanently, so I won't really ask you to try it without a big fat warning: although I think you'll still be able to reflash original firmware with TFTP method if it doesn't work, I can't be 100% sure so be warned

I currently don't have my flasher (a friend borrowed it some months ago and it may take some days to ask it back) or I would try it myself knowing I would be able to recover...

Is anyone here with a flasher able to try this in the meanwhile (having made a backup of the full flash first of course)? Or if someone can confirm that what I wrote above is harmless and will work...

Edit: corrected the mtd command, it's getting late and I should be sleeping now

boliva · October 23, 2020, 2:02am

Thank you @araujorm. I tried your suggestion of writing your latest image to the firmware partition and it bricked the router. But good news: the build from @db260179's thread worked when flashing it from stock (Chinese).

Brett · October 23, 2020, 9:18pm

Hi @boliva,

Is this the text version you are referring to?

root@XiaoQiang:/tmp/mtd_backup# bootinfo                                                                                                                                                                                                                                                                                                                                                                                                                          ROM    ver: config core 'version'                                                                                                                                                                                                        # ROM ver                                                                                                                                                                                                                        option ROM '3.0.9'                                                                                                                                                                                                               # channel                                                                                                                                                                                                                        option CHANNEL 'release'                                                                                                                                                                                                         # hardware platform R1AC or R1N etc.                                                                                                                                                                                             option HARDWARE 'R4A'                                                                                                                                                                                                            # CFE ver                                                                                                                                                                                                                        option UBOOT '1.0.2'                                                                                                                                                                                                             # Linux Kernel ver                                                                                                                                                                                                               option LINUX '0.0.1'                                                                                                                                                                                                             # RAMFS ver                                                                                                                                                                                                                      option RAMFS '0.0.1'                                                                                                                                                                                                             # SQUASHFS ver                                                                                                                                                                                                                   option SQAFS '0.0.1'                                                                                                                                                                                                             # ROOTFS ver                                                                                                                                                                                                                     option ROOTFS '0.0.1'                                                                                                                                                                                                            #build time                                                                                                                                                                                                                      option BUILDTIME 'Mon, 11 May 2020 10:39:54 +0000'                                                                                                                                                                               #build timestamp                                                                                                                                                                                                                 option BUILDTS '1589193594'                                                                                                                                                                                                      #build git tag                                                                                                                                                                                                                   option GTAG 'commit 85beb510fa8e9350b41c1cdef4f2083488887348'                                                                                                                                                            Hardware  : Ver. A                                                                                                                                                                                                               ROM    sum:                                                                                                                                                                                                                      System    : Dual - 1                                                                                                                                                                                                             KERNEL    : console=ttyS1,115200n8 uart_en=0 factory_mode=0 mem=128m root=/dev/mtdblock9                                                                                                                                                                                                                                                                                                                                                                          MTD  table:                                                                                                                                                                                                                      dev:    size   erasesize  name                                                                                                                                                                                                   mtd0: 01000000 00010000 "ALL"                                                                                                                                                                                                    mtd1: 00030000 00010000 "Bootloader"                                                                                                                                                                                             mtd2: 00010000 00010000 "Config"                                                                                                                                                                                                 mtd3: 00010000 00010000 "Bdata"                                                                                                                                                                                                  mtd4: 00010000 00010000 "Factory"                                                                                                                                                                                                mtd5: 00010000 00010000 "crash"                                                                                                                                                                                                  mtd6: 00010000 00010000 "cfg_bak"                                                                                                                                                                                                mtd7: 00100000 00010000 "overlay"                                                                                                                                                                                                mtd8: 00e80000 00010000 "OS1"                                                                                                                                                                                                    mtd9: 00cb0000 00010000 "rootfs"                                                                                                                                                                                                                                                                                                                                                                                                                                  root@XiaoQiang:/tmp/mtd_backup#

If so, after flashing OpenWrt the MTD layout is expected to be different, detailed below:

root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "Bdata"
mtd3: 00010000 00010000 "factory"
mtd4: 00010000 00010000 "crash"
mtd5: 00010000 00010000 "cfg_bak"
mtd6: 00100000 00010000 "overlay"
mtd7: 00e80000 00010000 "firmware"
mtd8: 001de405 00010000 "kernel"
mtd9: 00ca1bfb 00010000 "rootfs"
mtd10: 00970000 00010000 "rootfs_data"
root@OpenWrt:~#

Brett · October 24, 2020, 12:19am

Have just installed this build on the device that was previous running your v19.07.4-xiaomi-miwifi-3gv2-mt76updated-2020-09-18-fix_mtk_eth_timeout-generic_config firmware release

mitza97 · October 24, 2020, 12:50pm

Hello, somebody can give me please an MD5 hash of the latest @araujorm build from 22.10?
Thanks!

bagus02 · October 24, 2020, 1:11pm

how to limit bandwidth per mac addrs or ip?

araujorm · October 24, 2020, 1:22pm

@mitza97 here you go:

fe468d86816b1abff0b5c0fb80a1e838  openwrt-ramips-mt7621-xiaomi_mir3g-v2-squashfs-sysupgrade.bin

File size: 5440264

araujorm · October 24, 2020, 1:35pm

@bagus02 Sorry, never used openwrt for that. But take note that on local LAN you probably won't be able to do it without putting each port in a separate VLAN/interface and creating a software bridge or placing them on a different network. For limiting external WAN IP addresses you won't need that because that's already former the case. Then you should be able to install one of the QoS packages that come with openwrt, like sqm, nft-qos, qos-scripts and so on (also install the corresponding Luci app to configure using the web interface more convinently), but I can't help much further on that matter. Maybe search the forum for similar threads, as that will be a general openwrt question out of scope of this thread.

If however you have problems when installing packages let me know, I tried to put all necessary kmod packages on the custom repo I included in the /etc/opkg/zzz-araujorm.conf file (the zzz prefix is to ensure that's the last repo processed when doing opkg update, either via SSH or using Luci web interface's equivalent function, and so that package takes priority and the correct kmod packages for this image's kernel build are used instead of the official incompatible ones). It's a new feature in my latest build.

Brett · October 24, 2020, 2:18pm

Hi @araujorm,

I'm currently running your OpenWRT 19.07.04 for Mi 4A Gigabit with mt76 backports (generic edition) - 2020-10-22 build and hoping to use NFS mount to store router statistics, but have hit the following issue trying to install nfs-utils:

Details for package nfs-utils

    Version: 2.3.4-3
    Size: ~44.2 KB installed
    Dependencies:
        libwrap (10.1 KB) Not installed
        libblkid1 (118.7 KB) Not installed
            libuuid1 (12.4 KB) Not installed
                librt (126 B) Not installed
                    libpthread Installed
                        libgcc1 Installed
        libtirpc (51.3 KB) Not installed
        libkeyutils1 (4.2 KB) Not installed
        libdevmapper (135.1 KB) Not installed
            kmod-dm (90.3 KB) Not installed
                kernel Version incompatible
                kmod-crypto-manager (244 B) Not installed
                    kmod-crypto-aead (234 B) Not installed
                        kmod-crypto-null (196 B) Not installed
                            kmod-crypto-hash (240 B) Not installed
                    kmod-crypto-pcompress (105 B) Not installed
                kmod-dax (4.3 KB) Not installed

Description

Updated mount.nfs command - allows mounting nfs4 volumes

    The installed version of package kernel is not compatible, require 4.14.195-1-2e88863c… while 4.14.195-1-27395c84… is installed.

Would this also require packages in your custom repo?

Further feedback, I've also just experienced the following running this release (which I'm pretty sure was during a heavy file copy over the 5G WiFi connection. I currently have software flow offloading enabled if it has any relevance to this issue):

Sat Oct 24 13:13:10 2020 daemon.info dnsmasq[5279]: read /etc/hosts - 4 addresses
Sat Oct 24 13:13:10 2020 daemon.info dnsmasq[5279]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Sat Oct 24 14:44:04 2020 daemon.err uhttpd[1143]: luci: accepted login on / for root from REDACTED
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.171908] ------------[ cut here ]------------
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.176666] WARNING: CPU: 3 PID: 24 at /home/rod/r4ag/openwrt/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7621/mt76-2020-09-18-adb427d0/mt7603/mac.c:205 mt7603_filter_tx+0x100/0x164 [mt7603e]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.194127] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun leds_gpio gpio_button_hotplug
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.261222] CPU: 3 PID: 24 Comm: ksoftirqd/3 Not tainted 4.14.195 #0
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.267572] Stack : 00000000 00000001 86f495e8 8007271c 805c0000 80562bf4 00000000 00000000
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.275934]         8052e4b0 87c93be4 87c7a9bc 8059c967 805292a0 00000001 87c93b88 1cc28223
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.284297]         00000000 00000000 80700000 00005570 00000000 00000114 00000008 00000000
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.292701]         00000000 805a0000 0003fc66 00000000 00000000 805c0000 00000000 86928c34
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.301100]         86924304 000000cd 86930000 00000001 00000003 80299cf8 0000000c 8070000c
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.309502]         ...
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.311992] Call Trace:
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.314507] [<8000c7b0>] show_stack+0x58/0x100
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.318978] [<80469d54>] dump_stack+0xa4/0xe0
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.323363] [<8002f608>] __warn+0xe0/0x138
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.327502] [<8002f6f0>] warn_slowpath_null+0x1c/0x2c
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.332623] [<86924304>] mt7603_filter_tx+0x100/0x164 [mt7603e]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.338612] [<8692446c>] mt7603_wtbl_set_ps+0xa0/0x12c [mt7603e]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.344683] [<86921904>] mt7603_sta_ps+0x38/0x3b4 [mt7603e]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.350335] [<86993ba0>] mt76_rx_poll_complete+0x44c/0x510 [mt76]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.356492] [<86990de4>] mt76_dma_attach+0x84c/0xf08 [mt76]
Sat Oct 24 14:44:06 2020 kern.warn kernel: [48640.362308] ---[ end trace 02fdbb42cd0fd02e ]---

Pretty sure the blips in these graphs align to this time too:

Thanks,
Brett

beitabeet · October 24, 2020, 2:27pm

Hey folks, playing around with SQM on the latest stable (OpenWrt 19.07.4) and encountering Ethernet throttling with SQM enabled. Seems to be the case that with SQM enabled (on the 100mbps R4AC global) my speeds on Ethernet (cabled) go wayyyyy down to sub-megabit on both download and upload tested with iperf3. As soon as I disable it, it goes right back to the 100mbps connection limit.... I've tested it both on my phone and on my laptop and with different devices (to confirm 100mbps potential) so it's not a cable or device problem, v strange. Is this what your build addresses @araujorm?

araujorm · October 24, 2020, 5:05pm

@Brett,

I now compiled those missing packages, but they came out requiring a kernel with different signature. The kernel/openwrt build systems are picky on these matters...

So in order to anyone be able to use them, I had to publish another new build:

To people on 2020-10-22 release: if you don't have the need for any of the new packages you don't need to update because otherwise it's exactly the same. You can of course do it, but remember the router's flash doesn't have infinite rewrites (although it should have a few thousands, I'd hope).

araujorm · October 24, 2020, 5:09pm

@Brett regarding the warning on the mt76 driver: openwrt 19.07.4 doesn't use the latest version of the mt76 driver, it's impossible to have that since the master version uses stuff that the 4.14 kernel doesn't support. I tried to backport some of the fixes on my build, but there should be a lot missing unfortunately. Perhaps opening an issue on mt76 github will help, but I doubt they'll support this older driver version any more. I guess most of these issues will only go away on openwrt 20.x stable version when it comes out

araujorm · October 24, 2020, 5:14pm

No. My build only enables the installation of packages without having broken dependencies caused by none of the official v19.07.4 builds supporting this device - it's only supported in master version, from where the unstable snapshots are built, will be supported when openwrt 20.x comes out (I pray it's until the end of the year but I'm just a simple user trying to guess that).

Never worked with SQM but I think you need to configure the limits first, adjusting to your Internet speed, so that it's usable. Other than that, don't know about it.

beitabeet · October 24, 2020, 5:27pm

Ah ok, nah it's some bug with Ethernet specifically because my SQM limits are much higher than sub 1mbps. Wireless works just fine for example and sticks to the limits specified in the SQM interface.

db260179 · October 25, 2020, 2:31pm

Remember you can't use software or hardware offloading with sqm, it just wont work.

Brett · October 25, 2020, 11:32pm

@araujorm Thanks for the new compile, but sorry to report it shows the following:

Details for package **nfs-utils**

    Version: 2.3.4-3
    Size: ~44.2 KB installed
    Dependencies:
        libwrap (10.1 KB) Not installed
        libblkid1 (118.7 KB) Not installed
            libuuid1 (12.4 KB) Not installed
                librt (126 B) Not installed
                    libpthread Installed
                        libgcc1 Installed
        libtirpc (51.3 KB) Not installed
        libkeyutils1 (4.2 KB) Not installed
        libdevmapper (135.1 KB) Not installed
            kmod-dm (90.3 KB) Not installed
                kernel Version incompatible
                kmod-crypto-manager (244 B) Not installed
                    kmod-crypto-aead (234 B) Not installed
                        kmod-crypto-null (196 B) Not installed
                            kmod-crypto-hash (240 B) Not installed
                    kmod-crypto-pcompress (105 B) Not installed
                kmod-dax (4.3 KB) Not installed

Description

Updated mount.nfs command - allows mounting nfs4 volumes

    The installed version of package kernel is not compatible, require 4.14.195-1-2e88863c… while 4.14.195-1-dd24b383… is installed.

Overwrite files from other package(s)

I think it also requires:

Details for package nfs-kernel-server

Version: 2.3.4-3
Size: ~133.1 KB installed
Dependencies:
    libwrap (10.1 KB) Not installed
    libblkid1 (118.7 KB) Not installed
        libuuid1 (12.4 KB) Not installed
            librt (126 B) Not installed
                libpthread Installed
                    libgcc1 Installed
    libtirpc (51.3 KB) Not installed
    kmod-fs-nfsd (115.5 KB) Not installed
        kernel Version incompatible
        kmod-fs-nfs-common (120.3 KB) Not installed
        kmod-fs-exportfs (236 B) Not installed
        kmod-fs-nfs-common-rpcsec (38.7 KB) Not installed
            kmod-crypto-des (9.0 KB) Not installed
            kmod-crypto-cbc (2.2 KB) Not installed
                kmod-crypto-manager (244 B) Not installed
                    kmod-crypto-aead (234 B) Not installed
                        kmod-crypto-null (196 B) Not installed
                            kmod-crypto-hash (240 B) Not installed
                    kmod-crypto-pcompress (105 B) Not installed
            kmod-crypto-cts (2.9 KB) Not installed
            kmod-crypto-md5 (3.3 KB) Not installed
            kmod-crypto-sha1 (1.8 KB) Not installed
            kmod-crypto-hmac (2.3 KB) Not installed
            kmod-crypto-ecb (1.6 KB) Not installed
    kmod-fs-nfs (72.0 KB) Not installed
        kmod-dnsresolver (4.0 KB) Not installed
    kmod-fs-nfs-v4 (73.5 KB) Not installed
    rpcbind (22.5 KB) Not installed
    nfs-utils-libs (14.3 KB) Not installed
        libkeyutils1 (4.2 KB) Not installed
        libdevmapper (135.1 KB) Not installed
            kmod-dm (90.3 KB) Not installed
                kmod-dax (4.3 KB) Not installed

Description

Kernel NFS server support

The installed version of package kernel is not compatible, require 4.14.195-1-2e88863c… while 4.14.195-1-dd24b383… is installed.

Aside from this, I'm currently running your 2020-10-22+ builds to provide a WPS AP + WPS Client and so far are more stable than .04 WPS AP + SNAPSHOT based WPS Client.

Kind regards,

Brett