Add support for D-Link COVR-X1860

@RolandoMagico thanks for your work. I flashed your latest build (2023-08-06) to my new devices from the recovery. Worked flawlessly.

I need vlan for my network setup and I realized there is no swconfig in the cli. A short hint how to enable it would be awesome. I need vlan tagging for my ISP.

Hi @Ultrazauberer, can you install it in LuCI via System -> Software?

Not sure if kmod-swconfig is reqired as well, this cannot be installed via LuCI

1 Like

The branch:
The images:

I hope I didn't miss anything. I just did a short test with the sysupgrade image

I will test it right away.
Cheers mate!.

PS: what beast of a computer you have that compiles that fast? :smile:

You are right. I hooked up the COVR device on my old router and downloaded all packages. Thanks.

I'm getting errors when I try to install wire guard. It says "packages for kmod-wireguard found, but incompatible with the architecture configured". I guess I have to build my own image with wire guard included?

Everything is configured and working:

  • 802.11s
  • 802.11r
  • VLAN over mesh

I will check the stability of the device during the following weeks.
Thanks a lot for your effort @RolandoMagico .

1 Like

Right, kernel modules cannot be installed in the unofficial images, it only works when building an image.

Maybe somebody has more information regarding this topic. Theoretically it should be possible to build all packages when I build an image and then provide it as a big archive.

Alternatively, I can include commonly used kernel modules in the images I build.

1 Like

Technically, it should be possible to use the OpenWrt ImageBuilder from the donwloads section of the last stable release, but it would require patching support for the device into the ImageBuilder tree. The kernel would not be recompiled, but use the same one as the corresponding release did, which results in using an outdated mt76 (and maybe some regressions in terms of wifi / stability :thinking: ).

Unfortunately, the easiest way is still to build a custom image along with all the desired packages.
Or just build with all available packages and host the complete output somewhere public, then the opkg repositories in the image need to be changed somehow to point to that package collection (no idea where to set this), but then users could technically download further packages for that exact build... but usually nobody will put so much (mostly useless) effort in providing images that are just meant for temporary use.

1 Like

How did you configured your VLANs?

"swconfig list" doesn't show anything. :-/ Via Luci it's an unknown architecture and I have to guess or try the VLANs.

At the moment I just added my desired VLANs in the network config. I can't try the settings at the moment because the better half is watching streams. :slight_smile:

Hey everyone, new to the forum (but not OpenWrt). I've spent the better portion of my day setting up two COVR-X1860 - one as my main router (doing PPPoE for German Telekom fibre as well as WiFi) and then one as a "dumb AP", as the wiki calls it.

I ended up compiling my own image based on the patches provided by @RolandoMagico and it worked out like a charm. Thanks a bunch for this!

I was also considering maintaining a fork of OpenWrt until the device is included in the official OpenWrt repository, maybe even providing builds and packages (as I ran into the exact same issue described in the last couple of replies).

Would people be interested in this? If not, I'd just keep compiling images for myself and wouldn't bother with providing the packages anywhere.


I think there is just not any realistic time frame to expect regarding the official inclusion of this device (mainly due to the inclusion of a quite complex factory image generation tool), so when considering the cheap availability of this device and the apparently high interest this caused (judging by the length of this thread), it is probably a good idea to provide users which a ready-to-use intermediate solution for now :slightly_smiling_face:.


Hi Ultrazauberer!

If you need some guidance regarding VLAN configuration over mesh, you can check out this youtube video from the great OneMarcFifty. Really instructive.

If you have any specific question after the video, don't hesitate to ask.

1 Like

I am pretty sure your contribution would be highly appreciate!.

@s_2 given that you seems to be a knowledgeable person regarding OpenWRT, you may be able to answer a question.

I am sick and tired of the stock firmware of my D-Link Covr-X1860. I have been able to configure everything that I need in OpenWRT, so I am seriously considering moving my home network to OpenWRT now instead of waiting for the official firmware release. However, I am wondering if using snapshot firmware is safe enough from a security point-of-view.

I understand nothing (not even official releases) is 100% bulletproof and things are subject to fail, but I would like to know your opinion.

Thanks in advance for your time!

From a security point of view, snapshot firmware is always the first to receive any new fixes, even before they (at least the most severe ones) are being backported to previous releases. On the other hand, new security issues might have sneaked in of course, but there might just as well be (or let's say: there definitely are) remaining security issues in stable releases as well, that just weren't found (or at least reported) by anyone so far.

Additionally, when your choice is between a snapshot OpenWrt and leaving the device running on stock firmware, it should be noted that stock firmware contains loads of proprietary stuff written by the manufacturer, e.g. for mesh steering between the devices, or HNAP for management of the device via the D-Link configuration app etc., that most probably aren't subject to the same level of security precautions during development...

OpenWrt comes with very limited functionality (i.e. services running on the device) by default, anything else you need has to be explicitly enabled, e.g. by installing packages, which drastically reduces the attack surface especially for someone who already gained access to some part of your network.

I think I will move to OpenWRT right away.

Thanks for your time!

Hi, I registered to the forum for this thread :slight_smile:
Tried RolandoMagico compiled ROM on my X1860. It works fine in brief testing.
Maybe someone can point me to a tutorial how to "build" my own ROM with needed packages? Or maybe RolandoMagico can make one with

  • wpad-mesh-openssl
  • mesh11sd
  • luci-proto-batman-adv

But also I need openvpn server support. To remote into my network via secure tunnel. Is this possible? I think so. But openwrt is very new to me. So I'm struggling a bit. The learning curve is very steep with this (for now at least)

Sounds basically like this one:

So maybe this is a good start:

Tutorial for building images:

For OpenVPN, kmod-tun is required. Let me check
Update: I build, also have all kmods for this build on disk. I already included kmod-tun_5.15.123-1_mipsel_24kc.ipk in the release, you should be able to download it and install it via LuCI/opkg when using this image.

@Ultrazauberer : I also included kmod-wireguard_5.15.123-1_mipsel_24kc.ipk if it still required.

Seems there is no upload limit in GitHub releases, so all-kmods.tar.gz is now also included. It contains all kmods I built.


I've set up a cron job (and run a couple of manual test builds) which creates nightly builds and makes the bin/target folder available on my server:

The source code can be found here:

The firmware images can be found in the targets folder. The firmware is set up to automatically fetch the core packages (aka. kmods) from my server and I'll make sure to keep each build around for at least 14 days, meaning installation of kernel modules will be possible for at least 14 days.

The base image contains a few extra packages that I wanted for my system and didn't want to install manually (especially after firmware upgrades), namely miniupnpd and its LuCi module, DAWN + LuCi, batman-adv + LuCi, etherwake + LuCi, vnstat2 + LuCi, the Material theme for LuCi, and wpad-mesh-mbedtls instead of the basic package. If this is too many default packages, let me know and I'll get rid of a few. Alternatively you can also disable the unused services after flashing.

Let me know if anything goes wrong.


I can ask any1 have decrypt stock firmware, all time tried but all time sha512 failed...