I could be wrong here, but does that do anything for Wrt AC series? The Solidrun Clearfog GT 8k is a "board" -- https://www.solid-run.com/product-tag/clearfog-gt-8k/
BTW - Still ticks me off 10Gbe isn't standard for switched Ethernet. At least this has 1 SFP+ capable of 10Gb, but it is just 1 interface that you could connect to a NAS, for example.
What leads you to believe it has been signed off, at least for me there is this issue.
And yes, it is for all mvebu targets, with the introduction of a new one.
Thanks for bringing it to attention < V1 issues. Who knows what other issues in the rest of the series.
Yea false alarm, I saw at the top of that thread "Signed-off-by" but that's just to worked on kernel 4.19 for mvebu, not that it's complete.
That looks like a neat little device - it would help push away from having to troubleshoot and associate odd wireless issues that come up from the Marvell chipset as well. 10GbE would be a nice get as well.
As much as the Marvell chipset has been problematic, I am still thankful for having any sort of open source functionality no matter if there are improvements that could be made.
SD Card on that device would make upgrading a breeze, you wouldn't need to use a devices proprietary upgrade system and would make de-bricking a heck of a lot simpler.
A bit off topic- but I wonder if this device would ever get supported ever.
@directnupe
No, sadly I did not find yours. Looks pretty good. However the whole thing made me become decent at configuring OpenWRT, so I guess that is a good thing! Thanks for your write-up. I do appreciate people who do such things. It helps a lot. Thanks!!!
To close my initial thread. With David's latest build on my WRT1200ac, and using Private Internet Access as my VPN provider, I get much better throughput then what I was getting with a similar setup with dd-wrt. Very happy with the result. Also thank you @davidc502 for the builds. Glad I found you all.
Regarding kernel 4.19, I've been running it for almost 3 months now on my Rango's without any issues at all. Currently I'm on 4.19.30.
nitroshift
Currently just seems to be the usual problem child(mamba) has an issue with 4.19, although it would be nice to see another data-point on this device.
I have been using 4.19 for more than a month and there are no problems.
From the positive, it seems changed the thermal profile of the processor, it has become less hot.
Is this in reference to use of the 4,19PR specifically on a mamba device, so you are not experiencing this issue? If so, I guess mine has reached EOL.
Edit: forget that ^^^, I couldn't remember what kind of device you had, but me thinks it is a mamba, thanks, and I will go check over there.
@davidc502
Switched from dnscrypt-proxy v1 to v2. Thanks to your script it was very easy.
I'm just not happy with the default config and I would like to use my old dns servers (+1 for ipv6).
How would I do that?
In the config (dnscrypt-proxy.toml) I changed ipv6_servers = true and block_ipv6 = false as my device is also reachable through ipv6 via Dynamic DNS service.
After /etc/init.d/dnscrypt-proxy restart I'm able to resolve IPv6 sites over cloudflares dns server but I don't know how to get my old servers back (they are both listed at: https://dnscrypt.info/public-servers/).
Any advice?
I'm not sitting behind the router to check this... but in the .toml file you will see a line with the current Cloudflare servers. You should be able to replace cloudflare with your servers and restart the service. From that point forward it should use the DNS servers you want.
A follow up on SSL_VERSION_INTERFERENCE.
Getting this error when I generate my cert using this command: ''openssl req -x509 -nodes -days 730 -newkey rsa:2048 -keyout uhttpd.key -out uhttpd.crt -config myconfig.conf''.
If I use LUCI / UHTTPD, the error dissappear.
Weird but I can live with it 
Thanks for your help. I still haven't figured out on how to add a second dnscrypt proxy instance, like i had with v1...
edit: I figured it out. So if you want to add multiple DNS servers, it should look like this:
server_names = ['server1', 'server2', 'server3']
Happy to be on the v2 track for now, everything is working pretty well right now. Hopefully there will be a Luci-app for v2 one day. 
Why there is no nmbd (netbios name server) in the samba4-server package?
Will take a look at the build packages tonight and see if it is a case of just not being selected.
Comparing:
https://git.openwrt.org/?p=openwrt%2Fopenwrt.git&a=search&h=HEAD&st=commit&s=mwlwifi
and: https://github.com/kaloz/mwlwifi/commits/master
Looks like there were a couple minor changes to mwlwifi, hopefully OpenWrt updates there's before 19.03 release hits.
I've never gone in and tried, but bet anyone can commit that change. Would have to be approved, but if it is standard stuff would probably be no problem.