Hi, sorry to bother but there is a way to maintain some files after sysupgrade? I've placed my ddns script on root but it's get deleted each sysupgrade. Where should i put it?
Go to System -> Backup/Flash Firmware and click the configuration tab. There you can add custom files and directories to be included in the backup. Clicking 'Open List' will show you a list of all files and directories that will get backed up to make sure you specified it properly.
Thank you for the new update. Much appreciated.
I’m new user and I’m not sure how and where to find ‘openview’ snapshots.
I wanted Statistics/Graphs but in previous version I saw
~# /etc/init.d/luci_statistics restart /usr/bin/lua: /usr/bin/stat-genconfig:20: module 'luci.sys.iptparser' not found: […]
Could you share some pointers about that OpenView?
As a quick way to do this just remove the current distribution feeds, and copy them to a text file, and add the following list in its place.
Once you are finished downloading what you want from OpenWrt add the original feeds back. Reminder to everyone This trick only lasts for a short time because the daily snapshots change "daily", and soon there will be kernel bump, and once that happens this trick stops working until the next release.
src/gz lede_core https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/packages/ src/gz lede_base https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/base/ src/gz lede_luci https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/luci src/gz lede_packages https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/packages/ src/gz lede_routing https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/routing src/gz lede_telephony https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/telephony
Please let me know if the OpenWrt packages for Statistics works correctly or not. The Distribution feeds are in LuCi > Software > Configuration.
I have followed your instructions and worked fine at first time, but after a reboot stops working!
This might be a good information for you for the next users complaining:
The linksys stock firmware showed the same reboot issues, reproducable with heavy load on Wifi.
Now i did my second RMA for my 1900acs v2 and today (on a bank holiday!) Linksys called me and admitted that there are series of devices with defective chipsets built into devices in September (RAM?). Many other customers complained about the same issue and now i will get another replacement. This sucks. Really sucks. Took me a lot of work to figure out that i'm not insane
Thanks again for your good firmware, i am looking forward to a new device and using your firmware again!
Hi everyone. Just to drop the information that r8391 together with the statistics' packages from OpenWrt, work just fine on wrt1900acs v2. I did multiple reboots and things kept on working.
Wow! Great information!
Well, sorry it took so long to figure out, but on the good side Linksys is stepping up and taking care of business.
When you get the new hardware, the firmware will be ready for you :)
Is Shortcut Forwarding Engine (SFE) available in this build? If yes how can I enable it?
Unknown. I can't find anything in the repository called SFE or with the description of Shortcut Forwarding.
Is this package available in the stable or daily OpenWrt builds?
The mvebu platform should be fast enough to route at close to 1 GBit/s line speed without additional help.
SFE has never been merged into OpenWrt to begin with - and it most probably won't be (OpenWrt uses flow-offloading starting with kernel 4.14 instead); it's a very intrusive kernel patchset similar in behaviour to flow-offloading, but with much less testing.
After following your instructions graphs look good. ‘/etc/init.d/luci_statistics restart’ shows no errors this time.
Thank you so much!
I unfortunately don't understand these instructions on how I'd temporarily remove distribution feeds and use others to get the statistics packages back.. Given the snapshots are daily, I may have already missed my chance. However, for the sake of learning would you give me a few sentences on how I would do what you asked?
Simply copy the list of feeds from my previous post, and past them in the distribution feeds box like shown below and submit. Then install the package(s) you want.
I installed luci-app-statistics and it seems I have working statistics. Now, I am also running a recursive DNS server with getdns-stubby-unbound, and I'd like to figure out a way to get graphs of some unbound statistics. I haven't yet found a way to do that, so if anyone here has some advice I am all ears.
I just figured out that I've arrived late to install correct version of luci-app-statistics!!! This is why isn't working fine for me in my WPA3200ACM.
Hello - Answer -
You can check logs under Services > Recursive DNS > Status > Log - you will see that you have a caching encrypted DNS Resolver !!!
Also you can check CACHING and several other items under Services > Recursive DNS > Status
I see that you still have not carefully read any bit of : https://torguard.net/forums/index.php?/topic/1374-from-the-dns-privacy-project-dns-over-tls-on-openwrtlede-featuring-unbound-getdns-and-stubby/
You really might learn some very important information regarding your questions and understanding of running DNS OVER TLS with UNBOUND.
You can lead a horse to water but you can't make them drink - I guess.
PS - You might want to check out my new revised tutorial STUBBY DNS OVER TLS USING DNSMASQ-FULL FOR DNSSEC & CACHING here :
here: Stubby dns over tls using dnsmasq-full for dnssec & caching
Yes, I've already looked at the unbound logs and the status. However I want graphs of the statistics as well because the NLnet Labs Documentation shows the graphs (https://nlnetlabs.nl/documentation/unbound/howto-statistics/). I've read the link you provided ( https://torguard.net/forums/index.php?/topic/1374-from-the-dns-privacy-project-dns-over-tls-on-openwrtlede-featuring-unbound-getdns-and-stubby/) but this does not show how to integrate the plots into the statistics page.
Using Munin (MuninLite as node software on OpenWrt)
Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?" problems. It is designed to be very plug and play. A default installation provides a lot of graphs with almost no work.
On OpenWRT you can use MuninLite which is a single Bourne Shell script that implements the Munin protocoll as well as some Linux specific plugins. (The motivation for developing MuninLite was to provide a simple Munin Node, using inetd on systems without a full featured Perl.):
opkg update opkg install muninlite ethtool
A howto for Munin (on a Debian PC) can be found on http://www.howtoforge.org/server_monitoring_monit_munin.
Minidlna 'should' be good to go on the next build. I've been given the suggestion of including ffmpeg-mini which has the dependency minidlna has. This change should allow minidlna to complete.