John Adler
Regular Contributor
Hi
just did a dirty flash of ß3 on my router
VPN PPTP/L2TP working fine!
many thanks again!
just did a dirty flash of ß3 on my router
VPN PPTP/L2TP working fine!
many thanks again!
Long term know issue, here is a reply from RMerlin from 2012.Looks like I spoke too soon, no issues with 384.14_b3 .... found this within 24 hours...
Dec 7 13:16:11 kernel: device eth0 entered promiscuous mode
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:11 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:16 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:16 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:17 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:17 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:17 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:18 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:18 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:16:18 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:16:19 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:35 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:35 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:35 kernel: protocol 0800 is buggy, dev eth0
Dec 7 13:17:36 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:36 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:36 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:36 kernel: protocol 0000 is buggy, dev eth0
Dec 7 13:17:39 kernel: device eth0 left promiscuous mode
Also an old know issue, here is the RMerlin explanation.Also have a ton of these lines in 384.14_b3...
Dec 6 22:30:39 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc A0:72:2C:79:85:1A, status: 0, reason: d11 RC reserved (0)
Dec 6 22:31:02 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc A0:72:2C:79:85:1A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 6 22:31:02 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth A0:72:2C:79:85:1A, status: 0, reason: d11 RC reserved (0)
Dec 6 22:31:02 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc A0:72:2C:79:85:1A, status: 0, reason: d11 RC reserved (0)
Dec 6 22:31:13 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc A0:72:2C:79:85:1A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 6 22:31:13 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth A0:72:2C:79:85:1A, status: 0, reason: d11 RC reserved (0)
Dec 6 22:31:13 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc A0:72:2C:79:85:1A, status: 0, reason: d11 RC reserved (0)
Dec 6 23:26:33 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 78:32:1B:A9:F0:12, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 6 23:36:04 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 78:32:1B:A9:F0:12, status: 0, reason: d11 RC reserved (0)
Dec 6 23:36:04 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 78:32:1B:A9:F0:12, status: 0, reason: d11 RC reserved (0)
Dec 7 00:29:22 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 60:8C:4A:AC:5A:8A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 7 00:29:26 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 60:8C:4A:AC:5A:8A, status: 0, reason: d11 RC reserved (0)
Dec 7 00:29:26 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 60:8C:4A:AC:5A:8A, status: 0, reason: d11 RC reserved (0)
Dec 7 00:35:17 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 44:61:32:E5:405, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 7 00:35:48 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 44:61:32:E5:405, status: 0, reason: d11 RC reserved (0)
Dec 7 00:35:48 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 44:61:32:E5:405, status: 0, reason: d11 RC reserved (0)
Dec 7 00:49:22 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Disassociated due to inactivity (4)
Dec 7 00:49:22 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc E0:89:7E:0C:9C:08, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 7 00:49:30 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind E0:89:7E:0C:9C:08, status: 0, reason: Class 3 frame received from nonassociated station (7)
Keeping my 7756 based AX88 firmware for now unless there is a good reason to change (so far no stability issues as far as I've noticed. Havn't checked logs for errors though)
Updated from 14 B.1 - B.3. The link rate on my one stream AC 5 Ghz devices (primarily dot speakers ) dropped from 433/433 per wireless section of log to 6/6. Reverted back to B.1 and bandwidth restored.
Look at your System Log, it will tell you why. There's a good chance that either you are being throttled by Let's Encrypt's servers, or your /jffs partition is full.More problems with Letsencrypt:
Code:Status : Authorizing Issued to : SAN : undefined Issued by : Expires on :
Also have a ton of these lines in 384.14_b3...
Updated from 14 B.1 - B.3. The link rate on my one stream AC 5 Ghz devices (primarily dot speakers ) dropped from 433/433 per wireless section of log to 6/6. Reverted back to B.1 and bandwidth restored.
6/6 usually indicates power saving state of the device.
What you see may not be a problem, but an improvement in log accuracy.
This has nothing to do with the beta, the wireless driver hasn't changed since Beta 1.
I'm seeing this on Beta2 as well.Not sure if my beta install went smooth but after installing FreshJR I noticed 'Runner' and 'Flow Cache' are still enabled in the Tools>Sysinfo>HW acceleration section. Anyone else seeing this or did something go wrong on my end?
I don't understand why you expect that to change, Adaptive QoS keeps hardware acceleration enabled. FreshJR just tweaks Adaptive QoS, it's not doing anything on it's own.Not sure if my beta install went smooth but after installing FreshJR I noticed 'Runner' and 'Flow Cache' are still enabled in the Tools>Sysinfo>HW acceleration section. Anyone else seeing this or did something go wrong on my end?
Thanks
Only error I see in the process is in system log:Look at your System Log, it will tell you why. There's a good chance that either you are being throttled by Let's Encrypt's servers, or your /jffs partition is full.
Dec 7 17:05:40 kernel: cat: write error: Invalid argument
4.34 / 63.00 MB
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!