@kirkgbr Once the image is built [compiled], and the image flashed, files that are 600 or 400 within <buildroot>/files end up with 664 or 644 permissions once flashed to the router.

• I only started noticing this in the past couple of months (I wanna say July-ish was around when I began noticing it), and wrote a firstboot script to resolve the permissions issue, but I was curious if anyone else has experienced this. I've recreated the build environment twice since then, with the issue re-occurring each time.  I'll create a thread specifically for this then if no one else has seen anything similar.

After double checking, shadow is showing as 600, but keys and p12s within /etc/ssl which have 600 permissions in the build environment are created with 644 permissions within the image.  These are my main concern, as I can always leave shadow out and simply set the root password at first boot, however it's critical keys and p12's are root accessible only.

build environment

[jw0914@uvm] ~/openwrt/dev/files/etc $ ls -lsaR ssl
ssl:
total 52
 4 drwxrwxr-x 6 jw0914 jw0914  4096 Oct  9 14:38 .
 4 drwxrwxr-x 8 jw0914 jw0914  4096 Oct  9 18:21 ..
 4 drwxrwxr-x 2 jw0914 jw0914  4096 Sep 19 09:41 ca
 4 drwxrwxr-x 2 jw0914 jw0914  4096 Oct  9 14:40 certs
28 -rw-r----- 1 jw0914 jw0914 25465 Sep 17 10:16 openssl.cnf
 4 drwxrwxr-x 3 jw0914 jw0914  4096 Oct  9 14:13 openvpn
 4 drwxrwxr-x 2 jw0914 jw0914  4096 Oct  9 14:13 uhttpd

ssl/ca:
total 20
4 drwxrwxr-x 2 jw0914 jw0914 4096 Sep 19 09:41 .
4 drwxrwxr-x 6 jw0914 jw0914 4096 Oct  9 14:38 ..
8 -rw-r--r-- 1 jw0914 jw0914 4558 Sep 13 13:08 WRT1200AC-ICA-Chain.crt.pem
4 -rw-r--r-- 1 jw0914 jw0914 2273 Sep 13 11:37 WRT1200AC-ICA.crt.pem

ssl/certs:
total 16
4 drwxrwxr-x 2 jw0914 jw0914 4096 Oct  9 14:40 .
4 drwxrwxr-x 6 jw0914 jw0914 4096 Oct  9 14:38 ..
4 -rw-r--r-- 1 jw0914 jw0914 1988 Sep 13 12:25 wrt1200ac-uhttpd.crt
4 -rw-r--r-- 1 jw0914 jw0914 1960 Sep 13 12:27 wrt1200ac-VPNserver.crt

ssl/openvpn:
total 12
4 drwxrwxr-x 3 jw0914 jw0914 4096 Oct  9 14:13 .
4 drwxrwxr-x 6 jw0914 jw0914 4096 Oct  9 14:38 ..
4 drwxrwxr-x 2 jw0914 jw0914 4096 Oct  9 14:15 VPNserver

ssl/openvpn/VPNserver:
total 28
4 drwxrwxr-x 2 jw0914 jw0914 4096 Oct  9 14:15 .
4 drwxrwxr-x 3 jw0914 jw0914 4096 Oct  9 14:13 ..
4 -rw------- 1 jw0914 jw0914  769 Sep 19 09:07 dh4096.pem
4 -rw------- 1 jw0914 jw0914  657 Sep 19 12:07 ta.key
4 -rw-r--r-- 1 jw0914 jw0914 1960 Sep 13 12:27 wrt1200ac-VPNserver.crt
8 -rw------- 1 jw0914 jw0914 6381 Sep 17 16:55 wrt1200ac-VPNserver.p12

ssl/uhttpd:
total 16
4 drwxrwxr-x 2 jw0914 jw0914 4096 Oct  9 14:13 .
4 drwxrwxr-x 6 jw0914 jw0914 4096 Oct  9 14:38 ..
4 -rw-r--r-- 1 jw0914 jw0914 1988 Sep 13 12:25 wrt1200ac-uhttpd.crt
4 -rw------- 1 jw0914 jw0914 1704 Sep 17 16:47 wrt1200ac-uhttpd.key

(Last edited by JW0914 on 10 Oct 2016, 03:08)

On the latest lede build with kernel 4.4.24 5Ghz wifi has died twice, and another person has confirmed the same issue.

I have not been able to collect logs yet.

Has anyone else heard of the issue?

I am in 4.4.24 and probably have the wlan0 off-line once while i am in it, but it recover by itself so I don't check it.
but now I see dmesg have below message, must be wlan0.

[ 6156.251023] ------------[ cut here ]------------
[ 6156.255728] WARNING: CPU: 0 PID: 1655 at compat-wireless-2016-06-20/net/mac80211/agg-tx.c:347 ___ieee80211_stop_tx_ba_session+0x134/0x1f8 [mac80211]()
[ 6156.269273] Modules linked in: fuse autofs4 sd_mod pppoe ppp_async iptable_nat pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt mwlwifi mac80211 cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables gpio_button_hotplug
[ 6156.329732] CPU: 0 PID: 1655 Comm: hostapd Not tainted 4.4.24 #0
[ 6156.335762] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 6156.341716] [<c0027d80>] (unwind_backtrace) from [<c0024500>] (show_stack+0x10/0x14)
[ 6156.349496] [<c0024500>] (show_stack) from [<c0217514>] (dump_stack+0x8c/0xa0)
[ 6156.356750] [<c0217514>] (dump_stack) from [<c0034e5c>] (warn_slowpath_common+0x94/0xb0)
[ 6156.364875] [<c0034e5c>] (warn_slowpath_common) from [<c0034f14>] (warn_slowpath_null+0x1c/0x24)
[ 6156.373716] [<c0034f14>] (warn_slowpath_null) from [<bf0826bc>] (___ieee80211_stop_tx_ba_session+0x134/0x1f8 [mac80211])
[ 6156.384671] [<bf0826bc>] (___ieee80211_stop_tx_ba_session [mac80211]) from [<bf082b6c>] (__ieee80211_stop_tx_ba_session+0x30/0x44 [mac80211])
[ 6156.397455] [<bf082b6c>] (__ieee80211_stop_tx_ba_session [mac80211]) from [<bf0817ec>] (ieee80211_sta_tear_down_BA_sessions+0x44/0x6c [mac80211])
[ 6156.410585] [<bf0817ec>] (ieee80211_sta_tear_down_BA_sessions [mac80211]) from [<bf078918>] (ieee80211_sta_eosp+0x1d8/0x54c [mac80211])
[ 6156.422843] [<bf078918>] (ieee80211_sta_eosp [mac80211]) from [<bf07b9b0>] (__sta_info_destroy+0xc/0x28 [mac80211])
[ 6156.433355] [<bf07b9b0>] (__sta_info_destroy [mac80211]) from [<bf07ba3c>] (sta_info_destroy_addr_bss+0x2c/0x44 [mac80211])
[ 6156.444564] [<bf07ba3c>] (sta_info_destroy_addr_bss [mac80211]) from [<bf0406fc>] (nl80211_del_station+0xe8/0xf8 [cfg80211])
[ 6156.455841] [<bf0406fc>] (nl80211_del_station [cfg80211]) from [<c03d0c1c>] (genl_rcv_msg+0x2dc/0x384)
[ 6156.465188] [<c03d0c1c>] (genl_rcv_msg) from [<c03cff3c>] (netlink_rcv_skb+0x54/0xb4)
[ 6156.473051] [<c03cff3c>] (netlink_rcv_skb) from [<c03d0934>] (genl_rcv+0x28/0x34)
[ 6156.480565] [<c03d0934>] (genl_rcv) from [<c03cf90c>] (netlink_unicast+0x13c/0x1f4)
[ 6156.488253] [<c03cf90c>] (netlink_unicast) from [<c03cfd4c>] (netlink_sendmsg+0x2cc/0x340)
[ 6156.496551] [<c03cfd4c>] (netlink_sendmsg) from [<c038d190>] (sock_sendmsg+0x14/0x24)
[ 6156.504413] [<c038d190>] (sock_sendmsg) from [<c038d7dc>] (___sys_sendmsg+0x20c/0x220)
[ 6156.512364] [<c038d7dc>] (___sys_sendmsg) from [<c038e5d4>] (__sys_sendmsg+0x3c/0x60)
[ 6156.520227] [<c038e5d4>] (__sys_sendmsg) from [<c0009c80>] (ret_fast_syscall+0x0/0x3c)
[ 6156.528184] ---[ end trace ab9352df66ffc771 ]---

I would like to thank all the chaos calmer developers for this firmware. Installed today and updated fine. Thanks guys good job!

Using WRT1900ACS v1

(Last edited by zenbarguy on 11 Oct 2016, 10:39)

I've got the same router as yours v1. The stock firmware version will indicate which one it is. In our case v1, I'm using the chaos calmer firmware 15.05.1

So far, everything is working well for me. Wifi 5G and 2.4G working really well, no drop outs. SSID hidden custom setup

(Last edited by zenbarguy on 11 Oct 2016, 10:46)

I've been able to confirm both 2.4Ghz and 5Ghz died when under some load, like streaming netflix or downloading a large file.

@davidc502

No issues here on 49953.

nitroshift

David-
I'm running your build from the 9th on a 1900ac v2, and I'm definitely seeing the WIFI go off line after moderate load.  The 5ghz SID is visible but not joinable and the 2.4ghz SID is just gone.  Here's what I've got out of dmesg, starting at the point where everything broke:

[ 6484.500754] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 6484.506180] ieee80211 phy1: return code: 0x1125
[ 6484.510728] ieee80211 phy1: timeout: 0x1125
[ 6484.514938] ieee80211 phy1: destroy ba failed execution
[ 6548.551059] ieee80211 phy1: cmd 0x8050=broadcast_ssid_enable timed out
[ 6548.557631] ieee80211 phy1: return code: 0x0050
[ 6548.562198] ieee80211 phy1: timeout: 0x0050
[ 6548.566399] ieee80211 phy1: failed execution
[ 6552.570955] ieee80211 phy1: cmd 0x8127=SetInformationElements timed out
[ 6552.577610] ieee80211 phy1: return code: 0x0127
[ 6552.582184] ieee80211 phy1: timeout: 0x0127
[ 6552.586383] ieee80211 phy1: failed execution
[ 6556.590716] ieee80211 phy1: cmd 0x801c=80211RadioControl timed out
[ 6556.596927] ieee80211 phy1: return code: 0x001c
[ 6556.601488] ieee80211 phy1: timeout: 0x001c
[ 6556.605687] ieee80211 phy1: failed execution
[ 6560.610747] ieee80211 phy1: cmd 0x8126=SetFixedRate timed out
[ 6560.616534] ieee80211 phy1: return code: 0x0126
[ 6560.621096] ieee80211 phy1: timeout: 0x0126
[ 6560.625304] ieee80211 phy1: failed execution
[ 6569.258523] ieee80211 phy0: cmd 0x9125=BAStream timed out
[ 6569.263948] ieee80211 phy0: return code: 0x1125
[ 6569.268495] ieee80211 phy0: timeout: 0x1125
[ 6569.272704] ieee80211 phy0: destroy ba failed execution
[ 6622.523209] ieee80211 phy0: cmd 0x9122=UpdateEncryption timed out
[ 6622.529340] ieee80211 phy0: return code: 0x1122
[ 6622.533888] ieee80211 phy0: timeout: 0x1122
[ 6622.538094] ieee80211 phy0: failed execution
[ 6622.542381] wlan0: failed to remove key (0, 40:33:1a:de:1f:aa) from hardware (-5)
[ 6626.551108] ieee80211 phy0: cmd 0x9122=UpdateEncryption timed out
[ 6626.557237] ieee80211 phy0: return code: 0x1122
[ 6626.561785] ieee80211 phy0: timeout: 0x1122
[ 6626.565984] ieee80211 phy0: failed execution

I have not yet witnessed the reported wifi outage on mamba, all reports so far I think are cobra/shelby. The issue appears to have manifested between release r1809-r1814 which included a kernel bump and a very large mac80211 push.

wifi just died, and this was in the log... Pretty much identical to above.

Reverted back to 4.4.23 for now.

[69722.338713] ieee80211 phy0: cmd 0x9125=BAStream timed out
[69722.344162] ieee80211 phy0: return code: 0x1125
[69722.348713] ieee80211 phy0: timeout: 0x1125
[69722.352927] ieee80211 phy0: destroy ba failed execution
[69726.390636] ieee80211 phy0: cmd 0x9125=BAStream timed out
[69726.396072] ieee80211 phy0: return code: 0x1125
[69726.400620] ieee80211 phy0: timeout: 0x1125
[69726.404830] ieee80211 phy0: destroy ba failed execution
[69730.446068] ieee80211 phy0: cmd 0x9125=BAStream timed out
[69730.451493] ieee80211 phy0: return code: 0x1125
[69730.456052] ieee80211 phy0: timeout: 0x1125
[69730.460251] ieee80211 phy0: destroy ba failed execution
[69734.506474] ieee80211 phy0: cmd 0x9125=BAStream timed out
[69734.511899] ieee80211 phy0: return code: 0x1125
[69734.516462] ieee80211 phy0: timeout: 0x1125
[69734.520662] ieee80211 phy0: destroy ba failed execution

(Last edited by davidc502 on 12 Oct 2016, 01:09)

@davidc502 and Villeneuve

WRT1900ACS running on r1811 for 4+ days, no problems.

Interfaces with a WRT1900AC that's now been up for ~29 days -- no slowdowns in file transfer or streaming.

Any vanilla kernel after 4.1 has a broken nand driver. CC isn't affected and openwrt and lede both pseudo fix it in master. The nand-patch you are talking about is an additional workaround on top and meaningless this days.

Running OpenWRT (CC 15.05.1) on WRT1900AC v1. I had the router configured for a scheduled reboot, every day. Setup was up & running for about a month now. This morning I woke up to a router that appears to have crashed & restored last known firmware (Linksys firmware). I understand that it is safe for me to do a fresh OpenWRT install now. But is there anything I can do to - avoid going back to a factory default setting in future?

Hi mate you can get your old install back. there is 2 partitions on the flash. to load your old set up swich off the router then swich it back on for 2.5 seconds and then off again 3 times after the therd time it mite boot back in to your old setup.

Thanks tapper! That's useful, will save some time for me. Will give it a try!

Heads up. New wireless driver/firmware is now up.

@thelakesclub
Did you get your hands on a WRT3200ACM?
I believe that is what the 88W8964.bin is for.
I could be wrong.

I've pushed support in for the Rango (WRT3200ACM) for both master and cc - binaries are available at the usual location

WRT3200ACM sale page went up earlier today on US linksys site.

What is the correct way to invoke a 160mhz channel? VHT160?
And 80+80? How do we specify both centre freqs?
Do we have any documentation on these anyone could please point me towards?

Also, I saw no mention of Bluetooth in the dts.

(Last edited by Lantis on 13 Oct 2016, 12:47)

for the WRT3200ACM I just don't know what to make of the following statement.
"DFS Certified with Dedicated Scanner Radio
The WRT3200ACM operates in a clear airspace denied to traditional routers thanks to Dynamic frequency selection (DFS) certification from the FCC. This certification makes Tri-Stream 160 possible, and also triples the number of channels available at 80MHz. A dedicated DFS scanning radio keeps watch to prevent interference with airport weather radar, allowing the WRT3200ACM to maintain maximum speeds on the 5GHz band."

Considering the 1900ac won't stay on any 1 particular DFS channel any more than a few hours, and it doesn't matter if you are 200 miles away from the closest airport. Maybe they are using different firmware? Because people are going to be really disappointed otherwise.

PPOE seems to be broken after an upgrade:

I run my WRT1900ACS on LEDE, If I run it from the partition using the kernel 4.4.12, PPOE works just fine and I cna authenticate:

RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0x0 length 4
dst ff:ff:ff:ff:ff:ff  src c2:56:27:ca:d7:d4
[service-name]
Recv PPPOE Discovery V1T1 PADO session 0x0 length 40
dst c2:56:27:ca:d7:d4  src a0:f3:e4:34:d8:21
[service-name] [AC-name acc-aln1.hac] [AC-cookie  75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Send PPPOE Discovery V1T1 PADR session 0x0 length 24
dst a0:f3:e4:34:d8:21  src c2:56:27:ca:d7:d4
[service-name] [AC-cookie  75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Recv PPPOE Discovery V1T1 PADS session 0x30b length 4
dst c2:56:27:ca:d7:d4  src a0:f3:e4:34:d8:21
[service-name]
PADS: Service-Name: ''
PPP session is 779
Connected to a0:f3:e4:34:d8:21 via interface eth0

After I upgraded to the latest LEDE runninng on Kenrel 4.4.24, it looks like that ppoe is broken or anyway not working for me, it just loop on this message:

RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0x0 length 4
dst ff:ff:ff:ff:ff:ff  src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0x0 length 4
dst ff:ff:ff:ff:ff:ff  src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0x0 length 4
dst ff:ff:ff:ff:ff:ff  src c2:56:27:ca:d7:d4
[service-name]
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery

any suggestion ? the 2 partitions have exactly the same configuration.

Hi,

@jw0914, @zenbarguy: thanks for your reply. I have installed CC 15.05.1 (WRT1900acs with a V2 in label, V1 in firmware) and is in observation. Currently I have only 2.4ghz wireless enabled and a pc running some torrents. Just for tests.

What I really want to debug is why I have a lot of UDP connections to ISP dns server using transmission bittorrent client. Anyway to catch the problem? I mean.... how to know which problem specifically is and how mitigate, using openwrt, doing some analysis in packets maybe... because with transmission with almost 200 connections with my old wrt54gl without firewall my ISP don't disconnect me after some minutes, currently transmission client have 80 connections max and praying to not disconnect me. Graphs in OpenWRT show sometimes almost 300 connections, most of them are UDP to ISP dns server, if keeping raising connections my ISP disconnect me.

this are my graphs:
paste.opensuse.org/54524462
paste.opensuse.org/2586785

Thanks in advance

@feathersanddown

Based on the information you provided, UDP, DNS and your connection screenshot, it looks like it's all DNS queries(udp port 53).  I have never used Transmission but just guessing the router is trying to "lookup" the DNS names possibly for clients connecting to you?  Why... Heck if I know.

just a guess

regarding the driver issue on lede kernel .24 and Marvell 802.11ac Wireless Network Driver version 10.3.0.18-20160823-1
http://marc.info/?l=linux-wireless& … 81&w=2

so what is the stabile version?

(Last edited by gsustek on 13 Oct 2016, 22:45)

No. Not yet. When it's released in Australia I'll buy it. But it's not released here yet sadly.

Your right the bin file is (Rango) but a new wireless driver is up for grabs