Topic: davidc502 1900ac 3200acm builds

The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Page 183 of 229

Post #4551

adri

24 Jan 2018, 11:46

davidc502 wrote:

adri wrote:
davidc502 wrote:
Added flock to system utilities -- Thanks for the heads up.
@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.

No problem, I'll try the next build when it is available.

Post #4552

dreary_ennui

24 Jan 2018, 13:22

adri wrote:

davidc502 wrote:
adri wrote:
@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.
No problem, I'll try the next build when it is available.

FWIW, you can install flock from the software repo to resolve in the mean time, if you’d like.

Post #4553

farchord

24 Jan 2018, 14:10

Hey guys,

So I noticed that I had to uninstall mwifiex-sdio-firmware from this release. I thought we weren't supposed to install those?

Oh and for some reason my 5ghz AP still refuses to come online, anyone would have an idea why?

Post #4554

Icipher

24 Jan 2018, 19:59

ambrosa wrote:

WRT1900ACS , Lede SNAPSHOT r5621-1064e76e4e

It was running fine for about 4 days. Tomorrow a strange problem:
- ethernet connections ok
- wifi (2.4 GHZ) link connection ok but no internet access

I open system log and it's full of:

Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy Refetching server certificates
Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy Server certificate with serial #1496061161 received
Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy This certificate is valid
Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy Chosen certificate #1496061161 is valid from [2017-05-29] to [2027-05-27]
Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy The key rotation period for this server may exceed the recommended value. This is bad for forward secrecy.
Wed Jan 10 07:44:22 2018 daemon.info dnscrypt-proxy[2222]: dnscrypt-proxy Server key fingerprint is E737:6400:D646:0720:7D9D:29AB:A4C9:070C:4546:CEF7:0CFE:D62F:41E9:FEAA:C58F:6376
Wed Jan 10 07:44:34 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:44:34 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:44:34 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:44:34 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:44:34 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
Wed Jan 10 07:44:34 2018 daemon.info dnsmasq-dhcp[4087]: DHCPOFFER(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:44:34 2018 daemon.info dnsmasq-dhcp[4087]: DHCPREQUEST(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:44:34 2018 daemon.info dnsmasq-dhcp[4087]: DHCPACK(br-lan) 192.168.1.85 84:c7:ea:20:1f:29 XperiaXZ
Wed Jan 10 07:44:37 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:44:37 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: disassociated
Wed Jan 10 07:44:38 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan 10 07:44:42 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:44:42 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:44:42 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:44:42 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:44:42 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
Wed Jan 10 07:44:42 2018 daemon.info dnsmasq-dhcp[4087]: DHCPOFFER(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:44:42 2018 daemon.info dnsmasq-dhcp[4087]: DHCPREQUEST(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:44:42 2018 daemon.info dnsmasq-dhcp[4087]: DHCPACK(br-lan) 192.168.1.85 84:c7:ea:20:1f:29 XperiaXZ
Wed Jan 10 07:44:45 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:44:45 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: disassociated
Wed Jan 10 07:44:46 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan 10 07:44:59 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:44:59 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:44:59 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:44:59 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:45:00 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
Wed Jan 10 07:45:00 2018 daemon.info dnsmasq-dhcp[4087]: DHCPOFFER(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:45:00 2018 daemon.info dnsmasq-dhcp[4087]: DHCPREQUEST(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:45:00 2018 daemon.info dnsmasq-dhcp[4087]: DHCPACK(br-lan) 192.168.1.85 84:c7:ea:20:1f:29 XperiaXZ
Wed Jan 10 07:45:00 2018 cron.info crond[1761]: USER root pid 14264 cmd /sbin/fan_ctrl.sh
Wed Jan 10 07:45:03 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:45:03 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: disassociated
Wed Jan 10 07:45:04 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan 10 07:45:08 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:45:08 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:45:08 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:45:08 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:45:08 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
Wed Jan 10 07:45:08 2018 daemon.info dnsmasq-dhcp[4087]: DHCPOFFER(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:45:08 2018 daemon.info dnsmasq-dhcp[4087]: DHCPREQUEST(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:45:08 2018 daemon.info dnsmasq-dhcp[4087]: DHCPACK(br-lan) 192.168.1.85 84:c7:ea:20:1f:29 XperiaXZ
Wed Jan 10 07:45:10 2018 user.warn igmpproxy[4195]: MRT_DEL_MFC; Errno(2): No such file or directory
Wed Jan 10 07:45:11 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:45:11 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: disassociated
Wed Jan 10 07:45:12 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan 10 07:46:21 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:46:21 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:46:21 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:46:21 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:46:22 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
Wed Jan 10 07:46:22 2018 daemon.info dnsmasq-dhcp[4087]: DHCPOFFER(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:46:22 2018 daemon.info dnsmasq-dhcp[4087]: DHCPREQUEST(br-lan) 192.168.1.85 84:c7:ea:20:1f:29
Wed Jan 10 07:46:22 2018 daemon.info dnsmasq-dhcp[4087]: DHCPACK(br-lan) 192.168.1.85 84:c7:ea:20:1f:29 XperiaXZ
Wed Jan 10 07:46:24 2018 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:46:24 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: disassociated
Wed Jan 10 07:46:25 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Jan 10 07:46:30 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: authenticated
Wed Jan 10 07:46:30 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 IEEE 802.11: associated (aid 1)
Wed Jan 10 07:46:30 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:c7:ea:20:1f:29
Wed Jan 10 07:46:30 2018 daemon.info hostapd: wlan1: STA 84:c7:ea:20:1f:29 WPA: pairwise key handshake completed (RSN)
Wed Jan 10 07:46:30 2018 daemon.info dnsmasq-dhcp[4087]: DHCPDISCOVER(br-lan) 84:c7:ea:20:1f:29
(...omissis...)

After a reboot , it runs fine as usual.
Any idea ?

I also have this kind of issues with my wrt3200acm.
I don't know what is causing this..

Post #4555

makedir

25 Jan 2018, 01:21

@beginner67890 Do you know, if there is a way to restore the router to its default state with the Linksys firmware, so revert back 100%, with no trace, is this even possible? So remove the Lede and make Linksys the default boot partition again? I want to know, because I am thinking of shipping the router back to Amazon and request a new one. Maybe, which I highly doubt I am totally sure this is a firmware issue, my router has some hardware issue (maybe faulty ram).

Post #4556

farchord

25 Jan 2018, 01:52

makedir wrote:

@beginner67890 Do you know, if there is a way to restore the router to its default state with the Linksys firmware, so revert back 100%, with no trace, is this even possible? So remove the Lede and make Linksys the default boot partition again? I want to know, because I am thinking of shipping the router back to Amazon and request a new one. Maybe, which I highly doubt I am totally sure this is a firmware issue, my router has some hardware issue (maybe faulty ram).

Is it still on one of your partitions? If yes, do an advanced reboot and reboot onto the other partition.

If not, you can simply reflash the linksys firmware. Here's the OpenWRT article: https://wiki.openwrt.org/toh/linksys/wr … penwrt_oem

Post #4557

AddRemover

25 Jan 2018, 10:53

where we stay on RTC issue?
Mine Lede Reboot SNAPSHOT r5422-9fe59abef8 on 3200ACM set clock to 2038 thus all collectd's rrd files are updated with wrong timestamp, thus I have to wipe all rrd files after each reboot...

Post #4558

beginner67890

25 Jan 2018, 15:53

makedir wrote:

...some hardware issue (maybe faulty ram).

I just googled and found this program called 'stress' for testing the cpu/memory. That can be installed from the Luci System/Software tab. I haven't tried this and am still running the test.sh without problems. I have the V1 so set the radios to transmit less than full power. I think that keeps the router cooler because overheating can cause crashes just not ordinarily in January.

https://www.mankier.com/1/stress

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

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

root@LEDE:~# date
Thu Jan 25 06:38:03 PST 2018

root@LEDE:~# uptime
 06:38:06 up 49 days, 31 min,  load average: 0.00, 0.00, 0.00

root@LEDE:~# ps ax | tail -30
 1296 ?        S      0:05 /sbin/rpcd
 1302 ?        S     16:23 /usr/sbin/haveged -w 1024 -d 32 -i 32 -v 1
 1366 ?        S      3:17 /sbin/netifd
 1440 ?        S      2:01 /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 -K 300 -T 3
 2570 ?        Ss     0:00 /usr/sbin/smbd -F
 2571 ?        Ss     0:47 /usr/sbin/nmbd -F
 2841 ?        S      0:09 /usr/sbin/igmpproxy /var/etc/igmpproxy.conf
 7558 ?        S      1:06 /bin/sh ./test.sh
 8499 ?        Ss     5:03 /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]
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.pool.ntp.org -p 1.pool.ntp.org
16356 ?        S      1:54 /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg02411c -k -x /var/run/dnsmasq/dnsmasq.cfg02411c.pid
17763 ?        S      0:01 [kworker/u4:0]
20010 ?        S      0:12 /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 -R -p 0.0.0.0:80 -p [::]:80 -C /etc/uhttpd.crt -K /etc/uhttpd.key -s 0.0.0.0:443 -s [::]:443
22618 ?        S     31:01 /usr/sbin/snmpd -Lf /dev/null -f
23261 ?        S      0:00 [kworker/u4:2]
24229 ?        S      0:00 [kworker/1:0]
24717 ?        S      0:00 [kworker/1:1]
25977 ?        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 -K 300 -T 3
26118 ?        SL     0:10 /usr/sbin/dnscrypt-proxy /var/etc/dnscrypt-proxy-ns1.conf
26124 pts/1    Ss     0:00 -ash
27156 ?        S      0:00 sleep 5
27157 pts/1    R+     0:00 ps ax
27158 pts/1    S+     0:00 tail -30
27262 ?        S      3:17 [kworker/0:0]
27315 ?        Ss    11:26 /usr/sbin/hostapd -s -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf
28285 ?        S      0:02 [kworker/1:2]

root@LEDE:~# free
             total       used       free     shared    buffers     cached
Mem:        513080      83096     429984       1932       6260      22916
-/+ buffers/cache:      53920     459160
Swap:            0          0          0

root@LEDE:~# exit

Post #4559

anthonyclarka2

25 Jan 2018, 16:36

Wanted to say thank you for the latest build (2018-01-21) and the updated wifi driver for the WRT3200ACM.

The previous driver/build was plagued by the google wake-up bug and we'd have to disconnect and reconnect every time our phones would wake up, plus our chromecast would disconnect from our phones after a minute or two.

The updated driver/build is great, immediate connections upon waking our phones, and chromecast stays connected all the time. (disclaimer: so far and in our experience)

Post #4560

wasolk

25 Jan 2018, 17:00

davidc502 wrote:

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.

Hi David! Thank you for your new build. I have a WRT1900AC V1. With your previous build (r5621) the reboot issue was fixed (I got 17 days uptime)... I don't get any reboots with your current build (r5917), but I have a strange issue. Some of my PCs can't get more than 1 or 2 Mbps in download speed (I have a 120 Mbps Internet connection speed). Tablets and cellphones get full speed!

I rebooted the affected PCs, the router and the modem and the problem still exists. I reverted back to r5621 and everything is back to normal. (Getting full speed everywhere)

Do you think that there is a problem with the new wifi driver?

Thanks!

(Last edited by wasolk on 25 Jan 2018, 17:01)

Post #4561

davidc502

25 Jan 2018, 18:12

wasolk wrote:

davidc502 wrote:
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.
Hi David! Thank you for your new build. I have a WRT1900AC V1. With your previous build (r5621) the reboot issue was fixed (I got 17 days uptime)... I don't get any reboots with your current build (r5917), but I have a strange issue. Some of my PCs can't get more than 1 or 2 Mbps in download speed (I have a 120 Mbps Internet connection speed). Tablets and cellphones get full speed!
I rebooted the affected PCs, the router and the modem and the problem still exists. I reverted back to r5621 and everything is back to normal. (Getting full speed everywhere)
Do you think that there is a problem with the new wifi driver?
Thanks!

That would be an unknown. Since you are on the V1, I don't know what changes have been made that may or may not affect that version of hardware.

This weekend I'll be posting another driver version, so you may try r5917 again and install that driver and see if it improves.

Post #4562

davidc502

25 Jan 2018, 18:14

anthonyclarka2 wrote:

Wanted to say thank you for the latest build (2018-01-21) and the updated wifi driver for the WRT3200ACM.
The previous driver/build was plagued by the google wake-up bug and we'd have to disconnect and reconnect every time our phones would wake up, plus our chromecast would disconnect from our phones after a minute or two.
The updated driver/build is great, immediate connections upon waking our phones, and chromecast stays connected all the time. (disclaimer: so far and in our experience)

Just cross your fingers and knock on some wood. There are several outstanding issues with the 3200acm wifi driver being worked on, so hopefully we will have continuing improvement.

Post #4563

anymouse617

26 Jan 2018, 16:18

Is anyone here getting the issue of adblock not downloading lists successfully at boot since the most recent build? I seem to remember this happening before and the fix was to delay adblock from starting until later in the boot process. Does that sound familiar? Anyone having the same issue?

Stopping and starting adblock results in successful download of lists.

Finally, as a non-sequitur, for those of you who are in the Boston area and want to use a closer DNScrypt server than the ventricle one in NYC, you can use the MIT OpenNIC one located in Cambridge.

Address: 128.52.130.209:443
Name: 2.dnscrypt-cert.onic.csail.mit.edu
Public Key: 128D:B1BD:E10C:7CA1:D52B:091F:633E:99C1:937D:14F5:F812:B0CB:5B3C:F5CB:CC04:7272

(Last edited by anymouse617 on 26 Jan 2018, 16:22)

Post #4564

oldchip

27 Jan 2018, 18:44

Hi David, give mesome advise about this error.
I try r5917 for 1900acs v2 with this error, install some more pakages such as mwan3, tvheadend... stil the same error.
Sat Jan 20 22:42:20 2018 daemon.notice procd: /etc/init.d/dnsmasq: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for dnsmasq failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for adblock failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for adblock failed
Sat Jan 20 22:42:20 2018 daemon.notice procd: /etc/init.d/adblock: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for adblock failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for dnscrypt-proxy failed
Sat Jan 20 22:42:20 2018 daemon.notice procd: /etc/init.d/dnscrypt-proxy: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for dnscrypt-proxy failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for snmpd failed
Sat Jan 20 22:42:20 2018 user.info adblock-[3.4.3]: adblock is currently disabled, please set adb_enabled to '1' to use this service
Sat Jan 20 22:42:20 2018 daemon.notice procd: /etc/init.d/snmpd: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for snmpd failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for firewall failed
Sat Jan 20 22:42:20 2018 user.notice root: warning: procd flock for firewall failed
Sat Jan 20 22:42:32 2018 daemon.info dnscrypt-proxy[2752]: dnscrypt-proxy Refetching server certificates
Sat Jan 20 22:42:47 2018 daemon.err dnscrypt-proxy[2752]: dnscrypt-proxy Unable to retrieve server certificates
Sat Jan 27 17:25:28 2018 user.notice root: warning: procd flock for failed
Sat Jan 27 17:25:28 2018 daemon.info pppd[7602]: System time change detected.
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for adblock failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for collectd failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for cron failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for dnscrypt-proxy failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for dnsmasq failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for dropbear failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for firewall failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found
Sat Jan 27 17:25:59 2018 user.notice root: warning: procd flock for gpio_switch failed
Sat Jan 27 17:25:59 2018 daemon.err uhttpd[2803]: /etc/rc.common: /lib/functions/procd.sh: line 512: flock: not found

Post #4565

davidc502

27 Jan 2018, 18:55

@oldchip

flock will be added to the next build.

Post #4566

trohn_javolta

27 Jan 2018, 21:22

Just wanted to ask how to update these build real quick:
Can I use firmware update option?
Tick "keep configuration", download the <fw name>sysupgrade.bin file and update firmware?

Or do I have to switch partition and flash factory.img over current one and restore all config?

Post #4567

adri

27 Jan 2018, 22:31

@oldchip

In the meantime, you can install the 'flock' package.

Post #4568

davidc502

28 Jan 2018, 01:45

New wifi driver for those running r5917.

https://davidc502sis.dynamic-dns.net/re … _vfpv3.ipk

There have been 3 updates to this driver.

@yuhhaurlin
Separated broadcast and multicast packets. …
Assigned broadcast dhcpoffer to another queue. …
Corrected the way to get qos control. …

Post #4569

oldchip

28 Jan 2018, 08:08

Thanks @David and @adri.

Post #4570

makedir

28 Jan 2018, 08:50

thats the same driver as the one came with r5917.

(Last edited by makedir on 28 Jan 2018, 10:33)

Post #4571

floydburgermcdahm

28 Jan 2018, 12:17

davidc502 wrote:

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.

Same here, I am running r5917 on both 3200 and 1900ACS and it shows "Warning: This system does not have two partitions!"

Post #4572

davidc502

28 Jan 2018, 15:27

One thing I've noticed with the new driver is one amazon firetv (Android) can not connect to 5Ghz Wifi. There are 2 others I will check, and will do some more troubleshooting.

I've checked all the iphones and 1 Android S8, and they have no issues.

Post #4573

bill1228

28 Jan 2018, 20:42

Ok. I give. Have removed the wrt3200 from the network and replaced with a Netgear r8000 purchased off of Ebay. Currently running a Kong build. One thing of note is the wireless is faster in my tests then the wrt3200 has ever been and guessing will have much less in the way of issues, especially wireless.

@David
Thanks for all the support you provided during my 2 year trek into the Linksys wilderness.
--bill

Post #4574

davidc502

28 Jan 2018, 22:32

bill1228 wrote:

Ok. I give. Have removed the wrt3200 from the network and replaced with a Netgear r8000 purchased off of Ebay. Currently running a Kong build. One thing of note is the wireless is faster in my tests then the wrt3200 has ever been and guessing will have much less in the way of issues, especially wireless.
@David
Thanks for all the support you provided during my 2 year trek into the Linksys wilderness.
--bill

Enjoy that r8000!

I'll see you around.

David

Post #4575

Notsofast

29 Jan 2018, 00:21

Hi David!

Did my first install of your latest build for WRT1900AC/V2. Set it up and did some simple tests.

No difference with WIFI speeds for N on 5Ghz and 2.4Ghz, from Linksys latest firmware.

Was guessing the stock one may have issues with my Samsung tablet with a broadcom sdio chip.

Think my problem is the android driver, which only gives 1/2 of what it should get with the connections.

I did note, some higher than expected cpu usage. I assume it was setting up ad blocking after rebooting once i got everything setup for the AP.

Also a few wee bugs in in the interface, but managable.

It was a temp test run. Not ready to move on yet. Have other hardware to sort out, and get functioning first.

Page 183 of 229