I've found my graphs are all empty. The reason of that is the .rrd files was updated with wrong timestamp (future):

root@LINKSYS:/mnt/sda3/rrd#  rrdtool info ./LINKSYS_bak/interface-br-lan/if_octets.rrd | grep last_update
last_update = 2147352849

so I have to remove all *.rrd and strart from scratch. So i've lost a history...

Hello David,

Sounds advice. I was going to get an older router and play with that first so if it gets bricked it's not a real loss.

Many thanks,

Hi David!! Long time no talk! Hey, I just got my first AC device ( brand new notebook ) , and when connecting to the 1900ACS, i cannot get more than the following speed by sitting right next to the router:

ASUS (192.168.1.166) -53 / -90 dBm    866.7 Mbit/s, 80MHz, VHT-MCS 9, VHT-NSS 2, Short GI
[  4]   0.00-10.00  sec   322 MBytes   270 Mbits/sec                  sender
[  4]   0.00-10.00  sec   322 MBytes   270 Mbits/sec                  receiver

Any parameters that I can twear in /etc/config/wireless that would help me bump this up a little? It is too far away from the theoretical limit of 1900 megabits per second... just getting 270! I've read in reviews of my Notebook that it should get to 650 megabits/sec ...

Some more diagnostic information:

Sat Jan 20 18:45:08 2018 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Sat Jan 20 18:45:08 2018 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sat Jan 20 18:45:08 2018 kern.debug kernel: [ 1558.892205] ieee80211 phy0: change: 0x40
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1558.932294] device wlan0 left promiscuous mode
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1558.936824] br-lan: port 3(wlan0) entered disabled state
Sat Jan 20 18:45:08 2018 kern.debug kernel: [ 1558.998365] ieee80211 phy0: change: 0x100
Sat Jan 20 18:45:08 2018 daemon.notice hostapd: ELOOP: remaining socket: sock=21 eloop_data=0xb6ff9740 user_data=0 handler=0x36c28
Sat Jan 20 18:45:08 2018 daemon.notice netifd: radio0 (27486): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
Sat Jan 20 18:45:08 2018 daemon.notice netifd: radio0 (27486): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process  path ()
Sat Jan 20 18:45:08 2018 daemon.notice netifd: radio0 (27486): Command failed: Invalid argument
Sat Jan 20 18:45:08 2018 kern.debug kernel: [ 1559.160217] ieee80211 phy0: change: 0xffffffff
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1559.276262] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1559.299356] br-lan: port 3(wlan0) entered blocking state
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1559.304723] br-lan: port 3(wlan0) entered disabled state
Sat Jan 20 18:45:08 2018 kern.info kernel: [ 1559.310210] device wlan0 entered promiscuous mode

@beginner67890 I just had another reboot, it happened the second, I entered a URL and hit enter on one of my clients (I know because the router stands just next to me). The free command always shows the same range, there is never a higher usage of higher than about 60mb. It may have happened because the browser used tinyproxy...

root@wrtarm:~# free
             total       used       free     shared    buffers     cached
Mem:        513032      86596     426436        228       6788      18388
-/+ buffers/cache:      61420     451612
Swap:            0          0          0

I wonder if there was some kind of stress test script which might stress RAM usage and could trigger a reboot maybe faster. I made this script actually to fill some RAM and CPU usage, it may help to let it run over night maybe if you want this to do, and see if it triggers something:

#!/bin/sh
while true; do
  sleep 5
  yes | tr \\n x | head -c $((1024*1024*64)) | grep n
done
exit 0

(Last edited by makedir on 21 Jan 2018, 00:44)

makedir-

My WRT1200ACv1 is still running the last test.sh script. That seems fine so far. A strange thing is the test.sh now has a higher process number than the sleep 5. I imagine that is temporary.

My memory usage is still normal the same as yours. The swap file problem is still mysterious. I expect that should only happen when the memory is completely used so testing that response could give some good clues. I have been working on other projects recently so don't have a solution for the bad swap.

Maybe somebody else has experience with the tiny proxy. The crash because of a URL entry might be related to your complicated networking setup and that is way beyond my simplification oriented experience. Or maybe the URL was a really bad web page running some malicious or inefficient script. There are too many of those in my opinion.

EDIT: I have never had a spontaneous reboot with this setup that I know about. The router typically just gets a manual reboot when the ISP is having problems to make sure the ISP is the cause. That hasn't happened recently.

My super simple setup is doing fine:

BusyBox v1.27.2 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (SNAPSHOT, r4901-ab26fc6c8d)
    \________\/    -----------------------------------------------------------

root@LEDE:~# uptime
 18:31:14 up 44 days, 12:24,  load average: 0.00, 0.00, 0.00

root@LEDE:~# free
             total       used       free     shared    buffers     cached
Mem:        513080      81960     431120       1932       6260      22912
-/+ buffers/cache:      52788     460292
Swap:            0          0          0

root@LEDE:~# ps ax
  PID TTY      STAT   TIME COMMAND
 1287 ?        S      0:12 /sbin/logd -S 64
 1296 ?        S      0:05 /sbin/rpcd
 1302 ?        S     14:53 /usr/sbin/haveged -w 1024 -d 32 -i 32 -v 1
 1366 ?        S      2:57 /sbin/netifd
 1440 ?        S      1:52 /usr/sbin/odhcpd
 1500 ?        S      0:00 udhcpc -p /var/run/udhcpc-eth1.2.pid -s /lib/netifd/dhcp.script -f -t 0 -i eth1.2 -C -O 121
 1722 ?        S      0:00 /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 192.168.1.1:22 -p fded:3f9e:84c7::1:22 -
 2570 ?        Ss     0:00 /usr/sbin/smbd -F
 2571 ?        Ss     0:42 /usr/sbin/nmbd -F
 2841 ?        S      0:08 /usr/sbin/igmpproxy /var/etc/igmpproxy.conf
 6319 ?        S      0:00 [kworker/1:2]
 6808 ?        S      0:00 [kworker/1:0]
 6898 ?        Ss     0:00 /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 192.168.1.1:22 -p fded:3f9e:84c7::1:22 -
 6907 pts/1    Ss     0:00 -ash
 6948 ?        S      0:00 sleep 5
 6949 pts/1    R+     0:00 ps ax
 7558 ?        S      0:29 /bin/sh ./test.sh
 8499 ?        Ss     4:54 /usr/sbin/hostapd -s -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf
 9537 ?        S      0:01 /usr/sbin/collectd -f
 9692 ?        S      1:32 [kworker/0:1]
11489 ?        S      0:02 [kworker/1:1]
14017 ?        S<     0:00 /usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 131.216.7.120 -p 131.216.7.51 -p 1.lede.po
16356 ?        S      1:34 /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg02411c -k -x /var/run/dnsmasq/dnsmasq.cfg02411
20010 ?        S      0:09 /usr/sbin/uhttpd -f -h /www -r LEDE -x /cgi-bin -u /ubus -t 60 -T 30 -k 20 -A 1 -n 3 -N 100 
22618 ?        S     25:52 /usr/sbin/snmpd -Lf /dev/null -f
25212 ?        S      0:00 [kworker/u4:1]
25247 ?        S      0:03 [kworker/u4:2]
26118 ?        SL     0:07 /usr/sbin/dnscrypt-proxy /var/etc/dnscrypt-proxy-ns1.conf
27262 ?        S      2:39 [kworker/0:0]
27315 ?        Ss    10:29 /usr/sbin/hostapd -s -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf

root@LEDE:~# dmesg | tail
[989481.051522] ieee80211 phy0: change: 0x40
[989481.282934] ieee80211 phy0: change: 0x40
[989481.422962] br-lan: port 2(wlan0) entered disabled state
[989481.502941] ieee80211 phy0: change: 0x100
[989481.576731] ieee80211 phy0: change: 0x100
[989481.585751] ieee80211 phy0: change: 0x42
[989481.758941] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[989481.765489] br-lan: port 2(wlan0) entered blocking state
[989481.770917] br-lan: port 2(wlan0) entered forwarding state
[989481.867697] ieee80211 phy0: change: 0x20

root@LEDE:~# date
Sat Jan 20 18:32:35 PST 2018

root@LEDE:~# exit
Connection to 192.168.1.1 closed.

(Last edited by beginner67890 on 21 Jan 2018, 15:41)

r5917 has just been uploaded to the server.

Includes kernel bump to 4.9.77
Includes wifi driver to 10.3.4.0-20180118

V1 owners, be sure to change option check_signature 0 (This is for software -> Configuration)    Otherwise you will likely get the package mismatch messages.

Would like to get feedback but I noticed "Advanced Reboot" is showing only one partition available, but I've confirmed both partitions are there. I'm guessing there may be an issue with Advanced Reboot.

Getting the following in syslog regarding flock failures:

Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for dnsmasq failed
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for firewall failed
Sun Jan 21 21:04:07 2018 user.info adblock-[3.4.3]: adblock is currently disabled, please set adb_enabled to '1' to use this service
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for firewall failed
Sun Jan 21 21:04:07 2018 kern.debug kernel: [   24.131306] ieee80211 phy1: change: 0x40
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for sysntpd failed
Sun Jan 21 21:04:07 2018 daemon.notice procd: /etc/init.d/sysntpd: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for sysntpd failed
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for dnscrypt-proxy failed
Sun Jan 21 21:04:07 2018 daemon.notice procd: /etc/init.d/dnscrypt-proxy: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for dnscrypt-proxy failed
Sun Jan 21 21:04:07 2018 user.notice root: warning: procd flock for snmpd failed

(Last edited by dreary_ennui on 22 Jan 2018, 03:09)

Looks like 2 resolvers are being used?  I checked each with a single configuration and is working, so I'm thinking this has something to do with the config.

never seen "flock" failures all over the place like this. have had the same config for quite some time.

Sun Jan 21 21:04:00 2018 daemon.notice procd: /etc/rc.d/S30adblock: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found

adblock not even configured to do anything for me. am i missing a necessary part of the build?

David, maybe a fix in make menuconfig? - “I solved by 'make menuconfig' Base system→busybox→linux system utilities→flock Y”

https://bugs.openwrt.org/index.php?do=d … sk_id=1268

For some reason after this update, my 5ghz wireless refuses to start.... 2.4 works fine though.

Added flock to system utilities -- Thanks for the heads up.

No problem and thank you! Have installed flock from software repo, no more errors.

Thank you David for the builds, works great with my 1900ACS V2.
I've updated to the last version and noticed today the kernel version shows as 4.9.67 and not 4.9.77 as mentioned by David, and the driver version is 10.3.4.0-20171129.
Did I do something wrong during the updated? or missed a step?

System
Hostname    LEDE
Model    Linksys WRT1900ACS
Firmware Version    Lede SNAPSHOT r5501-30e18c8d64 / LuCI Master (git-17.343.27587-8e6b1a6)
Kernel Version    4.9.67
Local Time    Mon Jan 22 19:43:23 2018
Uptime    0h 6m 52s

There are two partitions so you can have two sets of firmware. I wonder if you have the version with 5.9.67 in one partition and 4.9.77 in the other partition.

Could you check in the System/AdvancedReboot tab of the router config web page?

(Last edited by beginner67890 on 23 Jan 2018, 03:33)

I have the following
Partition 1 - lede 4.9.65
Partition 2 - openwrt 4.9.67 - current and active

Should I install the original firmware from linksys?

Thx

Some people have the factory linksys on one and davidc502 LEDE REBOOT on the other and some people don't. Either way works.

Flashing from the current 4.9.67 partition should overwrite the firmware on the other partition and then reboot into that partition. You could try to re-download the firmware and re-flash and see what happens since you already overwrote the linksys firmware. There is little risk.

Did you download from davidc502 repo?
https://davidc502sis.dynamic-dns.net/releases/

EDIT1: The sha256 can be used to check if you are uploading the correct version to the router. The files don't reveal the version so that can be confusing.
I always use a local computer with an ethernet connection to the router for the upload.

(Last edited by beginner67890 on 23 Jan 2018, 04:10)

Just re-flashed to original Linksys firmware and back to David last build and the kernel version is showing the correct one 4.9.77 and driver 10.3.4.0-20180118. thank you for the help.

I'm getting this message when going to advaced reboot "Warning: This system does not have two partitions!"

Is this something to be concerned?

Hello,
Yesterday I flashed the latest firmware (I have got 3200), now Chromecast work better but multiple SSID on 2.4GHz doesn't work.
I can see the second WiFi but is impossible connect to it.

Any idea?

@davidc502,

Did you also update this in the latest firmware available for download?
Looking at the errors and fix, it seems this would affect a large number of users.

It was added to the .config for the next build.  I wasn't aware of the issue until this build was already out.

the latest davidc502 wrt1900ac build is the Lede Reboot SNAPSHOT r5113-2af10c30fe.  the latest stable lede release shows a r3560-79f57e422d.  just wondering if you have plan to build a r3560 for the wrt1900ac (v1)?

unless there is no difference between r5113 and r3560 as far as mvebu is concerned.

thank you

r5917 is patched for the V1. It doesn't guarantee not to have a reboot, but so far the reports have been good.

good to see an encouraging solution to the k4.9 reboot issue affecting wrt1900ac v1.  i've been quite satisfied with the r5113 k4.4 build hence will definitely give the r5917 k4.9 build a try when i get a chance.  thank you davidc502