Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

I wanted to test something aswell would you mind sharing the sysupgrade file for the wrt1900acs in a private message. Would appreciate it!

I am asking because I have a weird anomaly doing a:

wget -O /dev/null http://de.download.nvidia.com/Windows/452.06/452.06-desktop-win10-64bit-international-dch-whql.exe

On the wrt1200 itself, capping always regardless what source I use at around 86MB/s. htop just shows cpu usage of 40% (one core) so there is no bottleneck of the CPU.

Using the same command from a client behind the router, I reach my cable max speed of around 111MB/s.

First off thank you for the great work you have accomplished for these devices. The speed improvements on this firmware vs the stock openwrt are just night and day. Too much packet loss and issues on openwrt. The only issue I have is that I cannot run wireguard. Error.. Required dependency package kmod-wireguard is not available in any repository. When you go though the UI and you try to install wireguard this is the error seen. Any advise here?

Once more, thank you, you have made this device usable again.

It’s listed in David’s package repository. Try ‘update lists’.

Downloading ttps://dc502wrt.org/snapshots/r13342/targets/mvebu/cortexa9/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading ttps://dc502wrt.org/snapshots/r13342/targets/mvebu/cortexa9/packages/Packages.sig
Signature check passed.
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/base/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_base
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/base/Packages.sig
Signature check passed.
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/darkmatter/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_darkmatter
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/darkmatter/Packages.sig
Signature check passed.
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_luci
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/luci/Packages.sig
Signature check passed.
Downloading ttps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/opentomato/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_opentomato
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/opentomato/Packages.sig
Signature check passed.
Downloading htts://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/packages/Packages.sig
Signature check passed.
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_routing
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/routing/Packages.sig
Signature check passed.
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_telephony
Downloading htps://dc502wrt.org/snapshots/r13342/packages/arm_cortex-a9_vfpv3-d16/telephony/Packages.sig
Signature check passed.

Details for package wireguard

Version: 1.0.20200520-1
Size: ~105 B installed
Dependencies:
    wireguard-tools (26.7 KB) Not installed
        ip-full (193.2 KB) Not installed | ip-tiny (135.9 KB) Not installed
            libnl-tiny Installed
            libelf1 Installed
                libintl-full8 Installed
                zlib Installed
            libmnl0 Installed
    kmod-wireguard Not available

Description

WireGuard is a novel VPN that runs inside the Linux Kernel and utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPSec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. It uses UDP.

Required dependency package kmod-wireguard is not available in any repository.

this is via commad line

root@RT1:/usr/bin# opkg list |grep wireguard
kmod-wireguard - 5.4.42+1.0.20200520-1 - WireGuard is a novel VPN that runs inside the Linux Kernel and utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPSec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN.  WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. It uses UDP.  This package provides the kernel module for WireGuard.
luci-app-wireguard - git-20.144.63033-62ed4e6 - WireGuard Status
luci-i18n-wireguard-ar - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - العربية (Arabic)
luci-i18n-wireguard-bg - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - български (Bulgarian)
luci-i18n-wireguard-bn - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - বাংলা (Bengali)
luci-i18n-wireguard-ca - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Català (Catalan)
luci-i18n-wireguard-cs - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Čeština (Czech)
luci-i18n-wireguard-de - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Deutsch (German)
luci-i18n-wireguard-el - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Ελληνικά (Greek)
luci-i18n-wireguard-en - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - English
luci-i18n-wireguard-es - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Español (Spanish)
luci-i18n-wireguard-fi - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Suomi (Finnish)
luci-i18n-wireguard-fr - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Français (French)
luci-i18n-wireguard-he - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - עִבְרִית (Hebrew)
luci-i18n-wireguard-hi - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - हिंदी (Hindi)
luci-i18n-wireguard-hu - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Magyar (Hungarian)
luci-i18n-wireguard-it - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Italiano (Italian)
luci-i18n-wireguard-ja - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - 日本語 (Japanese)
luci-i18n-wireguard-ko - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - 한국어 (Korean)
luci-i18n-wireguard-mr - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Marāṭhī (Marathi)
luci-i18n-wireguard-ms - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Bahasa Melayu (Malay)
luci-i18n-wireguard-no - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Norsk (Norwegian)
luci-i18n-wireguard-pl - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Polski (Polish)
luci-i18n-wireguard-pt - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Português (Portuguese)
luci-i18n-wireguard-pt-br - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Português do Brasil (Brazilian Portuguese)
luci-i18n-wireguard-ro - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Română (Romanian)
luci-i18n-wireguard-ru - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Русский (Russian)
luci-i18n-wireguard-sk - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Slovenčina (Slovak)
luci-i18n-wireguard-sv - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Svenska (Swedish)
luci-i18n-wireguard-tr - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Türkçe (Turkish)
luci-i18n-wireguard-uk - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Українська (Ukrainian)
luci-i18n-wireguard-vi - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - Tiếng Việt (Vietnamese)
luci-i18n-wireguard-zh-cn - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - 简体中文 (Chinese Simplified)
luci-i18n-wireguard-zh-tw - git-20.144.63033-62ed4e6 - Translation for luci-app-wireguard - 繁體中文 (Chinese Traditional)
luci-proto-wireguard - git-20.144.63033-62ed4e6 - Support for WireGuard VPN
wireguard - 1.0.20200520-1 - WireGuard is a novel VPN that runs inside the Linux Kernel and utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPSec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN.  WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. It uses UDP.
wireguard-tools - 1.0.20200513-1 - This package provides the userspace control program for WireGuard, `wg(8)`, a netifd protocol helper, and a re-resolve watchdog script.

So even after updating lists it still has the issue, however, via cmd line i can clearly see the package there so it seems the issue is on the UI. This is a fresh install of openwrt-mvebu-cortexa9-linksys_wrt1900acs-squashfs-factory.img 2020-05-24 00:20. I am going to go via cmd line and get it done. I would be willing to help debug if or anyone maintainer need output of cmd ran or logs. It is just odd on a fresh install.

it depends on your internet connection, so would vary for all users. would be good if we could use the simple linksys prioritization which is on the
original firmware

question about LAN/WAN MAC addresses:
hardware: wrt32x

i've been using davidc builds for my wrt devices for years - and recently stumbled upon an oddity which is mentioned in this thread back in march 2020 but not discussed much: the swap of LAN and WAN addresses by certain builds.

my device has MAC 60:38:E0:XX:XX:XX on label.
is this supposed to be the LAN or WAN address?

on davidc 12000+ builds:
LAN in 60:38:E0...
WAN is 62:38:E0....

on 19.07.4:
LAN is 62:38:E0..
WAN is 60:38:E0...

on either build, fw_printenv shows
ethaddr 60:38:E0:XX:XX:XX
eth1addr ""
eth2addr ""
eth3addr ""

so the questions:

  1. what does the device label MAC refer to: LAN or WAN?
  2. presumably this would be the 'correct' MAC for openwrt
  3. what algorithm is used to genreate MAC for other interfaces in openwrt? i am used to seeing changes in last digits on MAC address, not the first, for subsequence interfaces on a device.
  4. when did this get swapped in the openwrt development process?

for me, this became more relevant when I moved from cable to ATT fiber; the fiber modem looks for a specific MAC address to pass-through to the router. so the undesired changes to the WAN MAC has required chainging the fiber modem config also.

of course htis wouldnot be a problem if i stopped experimenting with different builds my router - but that is why this forum exists.

i understand that this question reveals my basic lack of knowledge of u-boot, openwrt, and these devices despite years of reading, tinkering, some modding and flashing. thank you all in advance.

Hello everyone.

I really liked David's builds and would like to continue having them somehow. I have WRT3200ACM and WRT1200AC. Questions:

  • What is the current most stable build or distribution of OpenWRT I should be running on my devices if the goal is to have the most stable WiFi coverage?
  • How do I reproduce David's builds and most importantly, how do I choose the right snapshot commit to build?

FWIW. On June 20, @davidc502 posted:

“ Just checked the config and kmod-wireguard is set to build however it is not in the repository. This means it failed to build. Generally these don't last too long, so if you want to check the next build it should be there.“

Given the date, it appears it relates to the last build released.

I am having a problem been using DnsCrypt 2.0 for a bit now and have notice that all my device lose network connection multiple times during the day and it looks like every time dnscrypt cycle to find a dns server with the the shortest ping time all my devices renew there ip static ip address. I run a lot of home automation and its causing them to not work till everything comes back. Any ideas

What I did a while back was delete all of the dnscrypt2 servers you don't want to use from the file that lists all available dnscrypt 2 servers, keeping only those that you want. This helped me, because it would only pick from the two servers from opendns that I kept on the list. So my config never changed for my server and clients, since it would only ping these two servers, and always use them because they were the fastest two servers(and only two servers) in the list.

Sorry, I don't remember the file name or location. I stopped using dnscrypt 2 a while ago...I think it was something like /var/etc/dnscrypt-proxy-resolvers

1 Like

Well first of all not to be rude to all of Davids work, you can just compile OpenWRT from source using.

The https://github.com/openwrt/openwrt/tree/master is the "snapshot / Development builds" that you can find on https://downloads.openwrt.org/snapshots/targets/. You can also git clone the stable branch and compile OpenWRT from there. You can just flash a David build on of your devices and inspect the included software and also include them to your builds by using "make menuconfig". the /etc/configs folder contains configuration files, also those you can adjust and add them to your build by adding them to the custom files section. The Wi-Fi of this device is something I rather not comment on I have 3 Archer C7's in action to take care of that, because the Wi-Fi was always behind. The Qualcomm chips are better supported in OpenWRT and never let me down.

I mostly build from the master branch nothing is stopping you from making the build you so desire.

1 Like

I'm trying that today hope that helps
Thanks for the advise.

In fact, simple QoS already included in this firmware, and yes - i use it instead of SQM for better traffic control.

But i'm also use QoS-over-NfTables as a shaper for my guest wifi network.

I recommend using the final davidc502 build. Yea it's a few months old, but it's rock solid and comes with kernel 5.4. I have 100+ day uptime on my WRT32X with 5GHz wifi, SQM cake, software offloading, adblock, USB 3.0 network storage, samba4, etc. all running great. Whenever OpenWrt finally releases a full update in 2020 or 2021 with the new features then that'll be time to move away from davidc502, unless he does a new build.

3 Likes

totally not true, it has the broken dnscrypt-proxy version with memory leak in it, also wifi is not working for me with a intel card having 100-200ms pings to the device with another AP no problems.

There is never going to be any wifi improvement for the mvebu platform. Mwlwifi project has been dead for over a year with no further development from Marvell. Avoid their products in the future, and stick with qca based routers like the R7800 if you want wifi improvements. Pretty much all open source wifi is bad in general.

Overall this runs great for me like I said and my wifi is 'good enough', you sound like a better candidate for sticking with the OEM firmware you won't have those issues.

1 Like

Hi! @phinn what router would you recommend for best compatibility for OpenWRT and DDWRT? I have an WRT3200ACM and the WiFi is really unstable! Thanks!

I just got here. I was thinking of updating my wrt1200ac to the latest firmware from 18.06.04. Should I not do this, and is everyone saying in these 5621 posts that this router is dead as far as support? If so, no wonder I found a bargain on it.

Not near term IMHO. 20.0 is on the horizon, and the buildbots are still cranking out snapshots. Wireless is, has been, and will remain the one bane on this platform. If you consider you got it at a ‘bargain’, that’s a good thing. Still plenty of life in them ATM.

David stopped building with the kernel adopting DSA and dropping swconfig.