New Build 41686: 12-10-2019-r41686

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7273
Location: Texas, USA

PostPosted: Thu Dec 12, 2019 6:33    Post subject: Re: RT-N66R Reply with quote
Veritech wrote:
Just over a day and a half of uptime and I get two full syslog pages full of these. Wireless still functions as expected and I see no drops with these error messages.

Code:
Dec 10 21:22:46 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:22:46 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:27:57 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:00 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:25 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:33 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:34 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:35 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:36 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)
Dec 10 21:28:37 RT-N66R kern.err kernel: wl 0000:01:01.0 eth1: (WE) : Wireless Event (cmd=0x8C02) too big (31226)


Anyone have a work around?


Do you have the fancy wireless settings for minimum auth, drop clients if signal strength goes below such and such and all that stuff? If so, it may be related to your settings for that. It has something to do with policy AFAIK.

_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
Sponsor
BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 7029
Location: Dresden, Germany

PostPosted: Thu Dec 12, 2019 7:51    Post subject: Reply with quote
only wpa supplicant uses wireless extensions which may trigger this event. so it looks like he is using peap authentication or something like that
_________________
"So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
wabe
DD-WRT Guru


Joined: 17 Jun 2006
Posts: 765

PostPosted: Thu Dec 12, 2019 11:09    Post subject: Reply with quote
Router/Version: ASUS RT-AC68U ver C1
File: asus_rt-ac68u-firmware.trx
Firmware: DD-WRT v3.0-r41686 std (12/10/19)
Kernel: Linux 4.4.206 #440 SMP Mon Dec 9 15:10:29 +04 2019 armv7l
Mode: Gateway / AP
Previous: r41586
Reset: No, flashed from command line
Status: Works well so far

_________________
AC-68U rev. C1 on Build 44483
AC-68U rev. A1 on Build 44483
AC-68U rev. A1 on Build 44340
hurleyp
DD-WRT User


Joined: 10 Sep 2009
Posts: 285
Location: Ottawa, Ontario, Canada

PostPosted: Thu Dec 12, 2019 15:32    Post subject: Reply with quote
Firmware: v3.0-r41686 std (12/10/19)
Router/Version: Netgear R7000
Kernel: Linux 4.4.206 #440 SMP Mon Dec 9 15:10:29 +04 2019 armv7l
Previous: v3.0-r41586 std (11/21/19)
Mode/Status: Gateway/AP, Up and running for 24 hours
Reset: Soft boot before and after upgrade
Temperatures: CPU 56.9 °C / WL0 44.8 °C / WL1 47.7 °C
Issues/Errors: Some Syslog message times are wrong

Some Syslog messages sent to a remote server have the wrong timestamp. In my case the remote server is a QNAP device on my LAN. The messages from dnsmasq-dhcp and dnsmasq have the correct timestamps, while httpd, ntpclient and process_monitor messages are off by 5 hours. The timezone is Canada/Eastern (UTC -5:00)and I'm using the default NTP server (left blank in Time Settings). I don't have the klogd daemon active. This problem doesn't occur in the DD-WRT webif, all timestamps are correct when viewed in Status/Syslog. This was a problem in r41586 too.

No 'nvram erase' this time. No issues with wireless devices.

Current basic R7000 setup (subject to change of course):
- Static WAN IP
- SFE - On
- STP - On
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 149, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- NO: ttraf, VNC, Zabbix, VPN, Radius, OpenVPN
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware

_________________
Netgear R7000: v3.0-r44627 std (10/22/20)
EdgeRouter-X: EdgeOS v2.0.8
Veritech
DD-WRT User


Joined: 02 Jan 2007
Posts: 181

PostPosted: Fri Dec 13, 2019 0:41    Post subject: Reply with quote
kernel-panic69 wrote:
Do you have the fancy wireless settings for minimum auth, drop clients if signal strength goes below such and such and all that stuff? If so, it may be related to your settings for that. It has something to do with policy AFAIK.


BrainSlayer wrote:
only wpa supplicant uses wireless extensions which may trigger this event. so it looks like he is using peap authentication or something like that


I'm using WPA2-PSK auth, advanced settings are default, ack timing is changed from 2000 to 50,channel is static, and mode is *-Mixed. Nothing fancy. Ideas?
technoside2
DD-WRT User


Joined: 25 Oct 2018
Posts: 63

PostPosted: Fri Dec 13, 2019 2:27    Post subject: Reply with quote
Router/Version: Linksys WRT54G2 / GS2
File: dd-wrt.v24_micro_generic.bin
Firmware: DD-WRT v3.0-r41686 micro (12/10/19)
Kernel: Linux 2.4.37 #57444 Tue Dec 10 04:48:13 +04 2019 mips
Mode: AP
Reset?: N
Status: Working


Router/Version: Linksys EA6350 v2
File: linksys-ea6350-webflash.bin
Firmware: DD-WRT v3.0-r41686 std (12/10/19)
Kernel: Linux 4.4.206 #440 SMP Mon Dec 9 15:10:29 +04 2019 armv7l
Mode: Router/AP
Reset?: N
Status: Working

_________________
WRT54GL v1.1 - Flashed
Linksys WRT54G2 v1 - Flashed
EA6350 v2 - Flashed
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 695
Location: Hung Hom, Hong Kong

PostPosted: Fri Dec 13, 2019 7:56    Post subject: DD-WRT BS build 41686 and Asus RT-N18U Reply with quote
Router/Version: Asus RT-N18U(rev. A1)
Firmware: DD-WRT v3.0-r41686 std (12/10/19)
Kernel: Linux 4.4.206 #444 Tue Dec 10 05:57:48 +04 2019 armv7l
Previous: D-WRT v3.0-r41664 std (12/06/19)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (not 24/7 & not using IPv6, VAP, VPN; Using NAS & USB)
Reset: NO reset during firmware upgrade but cold boot

1, 2 are related to front panel LAN LEDs. Skipped!

3. There were some strange entries in the system log
listed below, towards the end of each section.

4. Error(s) logged:
grep -i err /var/log/messages
Code:


Jan  1 08:00:15 RT-N18U kern.err kernel: bcmsflash: found no supported devices
Jan  1 08:00:15 RT-N18U kern.err kernel: hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jan  1 08:00:16 RT-N18U daemon.info mstpd[606]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 7
Jan  1 08:00:16 RT-N18U daemon.info mstpd[606]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 7
Dec 13 15:48:55 RT-N18U daemon.err httpd[1459]: httpd : Request Error Code 404: File style/elegant/logo.png not found.


5. Warning(s) logged:
grep -i warn /var/log/messages | grep -v DROP
Code:

Jan  1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan  1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan  1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan  1 08:00:15 RT-N18U kern.warn kernel: Boot partition size = 524288(0x80000)
Jan  1 08:00:15 RT-N18U kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan  1 08:00:15 RT-N18U kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan  1 08:00:15 RT-N18U kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan  1 08:00:15 RT-N18U kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan  1 08:00:15 RT-N18U kern.warn kernel:  2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jan  1 08:00:15 RT-N18U kern.warn kernel: Available 7 bytes at (off,len):
Jan  1 08:00:15 RT-N18U kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Jan  1 08:00:15 RT-N18U kern.warn kernel: Bad eraseblock 356 at 0x000002c80000
Jan  1 08:00:15 RT-N18U kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan  1 08:00:15 RT-N18U kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan  1 08:00:15 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: passivemode set to 0x0
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: txworkq set to 0x1
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan  1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan  1 08:00:15 RT-N18U kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan  1 08:00:15 RT-N18U kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan  1 08:00:15 RT-N18U kern.warn kernel: wl_module_init: txworkq set to 0x1
Jan  1 08:00:15 RT-N18U kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan  1 08:00:15 RT-N18U kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan  1 08:00:15 RT-N18U kern.warn kernel: jffs2: Empty flash at 0x01d41498 ends at 0x01d41800
Jan  1 08:00:15 RT-N18U kern.warn kernel: jffs2: Empty flash at 0x01d49250 ends at 0x01d49800
Jan  1 08:00:15 RT-N18U kern.warn kernel: jffs2: Empty flash at 0x01d5f1f0 ends at 0x01d5f800
Jan  1 08:00:17 RT-N18U kern.warn kernel: EXT4-fs (sda1): Ignoring removed nobh option
Dec 13 15:32:41 RT-N18U daemon.warn dnsmasq[1342]: possible DNS-rebind attack detected: blackhole.inspcloud.com


6. Kernel debugging messages:
grep -i debug /var/log/messages
Code:
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x10: [mem 0x18026000-0x18026fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: [14e4:4715] type 00 class 0x020000
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x10: [mem 0x18027000-0x18027fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x10: [mem 0x18012000-0x18012fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: supports D1 D2
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
Jan  1 08:00:15 RT-N18U kern.debug kernel: pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
Jan  1 08:00:15 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan  1 08:00:15 RT-N18U kern.debug kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Jan  1 08:00:26 RT-N18U daemon.debug ntpclient[1113]: Connecting to time.hko.hk [118.143.17.82] ...
Dec 13 15:26:22 RT-N18U daemon.debug process_monitor[1111]: Restarting cron (time sync change)
Dec 13 15:26:22 RT-N18U daemon.debug process_monitor[1322]: We need to re-update after 3600 seconds
Dec 13 15:26:23 RT-N18U daemon.debug ntpclient[1352]: Connecting to time.hko.hk [223.255.185.2] ...
Dec 13 15:26:23 RT-N18U daemon.debug process_monitor[1348]: We need to re-update after 3600 seconds


Firmware Size

From 30515200 (b.31277) to 24711168 (b.33555) = -5804032 bytes
From 24711168 (b.33555) to 27054080 (b.34929) = 2342912 bytes
From 27054080 (b.34929) to 26640384 (b.35531) = -413696 bytes
From 26640384 (b.35531) to 25022464 (b.36995) = -1617920 bytes
From 25022464 (b.36995) to 25427968 (b.37961) = 405504 bytes
From 25427968 (b.37961) to 25804800 (b.38570) = 376832 bytes
From 25804800 (b.38570) to 27574272 (b.38840) = 1769472 bytes
From 27574272 (b.38840) to 27774976 (b.39031) = 200704 bytes
From 27774976 (b.39031) to 27779072 (b.39137) = 4096 bytes
From 27779072 (b.39137) to 27779072 (b.39144) = 0 byte
From 27779072 (b.39144) to 28672000 (b.39267) = 892928 bytes
From 28672000 (b.39267) to 27926528 (b.39296) = -745472 bytes
From 27926528 (b.39296) to 27918336 (b.39494) = -8192 bytes
From 27918336 (b.39494) to 27918336 (b.39508) = 0 byte
From 27918336 (b.39508) to 28147712 (b.39572) = 229376 bytes
From 28147712 (b.39572) to 28151808 (b.39654) = 4096 bytes
From 28151808 (b.39654) to 28151808 (b.39715) = 0 byte
From 28151808 (b.39715) to 27938816 (b.39800) = -212992 bytes
From 27938816 (b.39800) to 27938816 (b.39884) = 0 byte
From 27938816 (b.39884) to 27942912 (b.39944) = 4096 bytes
From 27942912 (b.39944) to 28024832 (b.40065) = 81920 bytes
From 28024832 (b.40065) to 28479488 (b.40459) = 454656 bytes
From 28479488 (b.40459) to 28749824 (b.40900) = 270336 bytes
From 28749824 (b.40900) to 27856896 (b.41174) = -892928 bytes
From 27856896 (b.41174) to 27873280 (b.41686) = 16384 bytes



speedtest.net result for DD-WRT BS build 41686 and Asus RT-N18U.png
 Description:
Speedtest.net result for DD-WRT BS build 41686 and Asus RT-N18U
 Filesize:  13.15 KB
 Viewed:  3036 Time(s)

speedtest.net result for DD-WRT BS build 41686 and Asus RT-N18U.png



_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
tinkeruntilitworks
Guest





PostPosted: Fri Dec 13, 2019 12:59    Post subject: Reply with quote
Router: Netgear R7000P
Kernel: Linux 4.4.206 #445 SMP Tue Dec 10 06:03:11 +04 2019 armv7l
Mode: Gateway/AP IPv6 Unbound JFFS2
Status: all seems well
*
I've seen the (WE) : Wireless Event (cmd=0x8C02) too big (31226) at times too the last couple builds.

Sometimes I leave my setup default as possible. Other times I'll make some changes suggested in the basic and advanced wireless setup wiki guide.
Preamble to short
Shortslot Override to short
Bluetooth Coexistence Mode to preemption on 2.4
adjust Beacon Interval to 97 & 103
Sensitivity Range (ACK Timing) to 0

i think adjusting some of the above settings takes an extra reboot to get rid of the errors

*
I was also using beamforming and QoS

**
had 2.4 & 5 both with the same name as well

***
after doing a clean install i haven't noticed it
possible it was just the last build


Last edited by tinkeruntilitworks on Mon Dec 16, 2019 14:33; edited 1 time in total
decompiled
DD-WRT User


Joined: 02 Jan 2008
Posts: 78

PostPosted: Sat Dec 14, 2019 22:22    Post subject: Reply with quote
Router Model Netgear R7000
Firmware Version DD-WRT v3.0-r41686 std (12/10/19)
Kernel Version Linux 4.4.206 #440 SMP Mon Dec 9 15:10:29 +04 2019 armv7l
Mode: Router
Reset: No

BS FW has been working well. Noticed CPU was 100% in UI and 2.4ghz had dropped to 1mbps speeds. Reboot seemed to clear the issue. First issue I've had in a while and will monitor.
mj666
DD-WRT Novice


Joined: 26 Nov 2010
Posts: 22

PostPosted: Sun Dec 15, 2019 11:04    Post subject: Reply with quote
For the E3000 cron is still working with this build but not for all three ASUS routers. See the exact types in my singnature.
_________________
Asus AC-RT88U (asus_rt-ac88u-firmware_44213.trx)
Asus AC-RT68U (asus_rt-ac68u-firmware_44213.trx)
Asus AC-RT66U (dd-wrt-44213-Asus_RT-AC66U.trx)
Linksys E3000 (dd-wrt.v24-44213_NEWD-2_K3.x_mega-e3000.bin)
Linksys E4200 V2 (openwrt-18.06.5-kirkwood-linksys_viper-squashfs-sysupgrade.bin)
scans
DD-WRT Novice


Joined: 04 Oct 2018
Posts: 12

PostPosted: Mon Dec 16, 2019 2:43    Post subject: Reply with quote
Router: Netgear WNDR4000 (x2)
Firmware: DD-WRT v3.0-r41686 mega (12/10/19)
Reset: No
Mode: 2.4/5Ghz access points, DynDNS, Wireguard, bridged VAP (hidden and unhidden)

Re-key issue reappeared after 48 hours. Back to r41586.
WouldRatherBeFOSS
DD-WRT User


Joined: 09 Nov 2019
Posts: 88

PostPosted: Tue Dec 17, 2019 1:07    Post subject: Reply with quote
On this build I'm getting, of late, one brief disconnect per day, in the early morning. Still, the culprit might be my ISP or VPN-provider. Neither of those seems to have had widespread recent outages, but it is hard to tell. I suppose I should enable logging on the router and do the telnet thing to get the logs. (An easier way of getting logs is desirable.)
_________________
My router: Asus RT-AC66U

Operating systems on devices that I use with that router: GNU-Linux; Windows 10; Android Lollipop
WouldRatherBeFOSS
DD-WRT User


Joined: 09 Nov 2019
Posts: 88

PostPosted: Tue Dec 17, 2019 3:44    Post subject: Reply with quote
I can't see anything relevant - to the disconnections that I mentioned before (and which have become more frequent, even with my VPN off) in the log. I've posted the log here. (The log contains lots of stuff about failed authentications. But that was me messing around with my password manager - and not at the time I had the outages.)
_________________
My router: Asus RT-AC66U

Operating systems on devices that I use with that router: GNU-Linux; Windows 10; Android Lollipop
dslayer6989
DD-WRT Novice


Joined: 06 Dec 2017
Posts: 24

PostPosted: Wed Dec 18, 2019 0:55    Post subject: Netgear Nighthawk AC3200 (R8000) Reply with quote
Router/Version: Netgear R8000
Firmware: DD-WRT v3.0-r41686 std (12/10/19)
Kernel: Linux 4.4.206 #445 SMP Tue Dec 10 06:03:11 +04 2019 armv7l
CPU Model: Broadcom BCM4709
Previous: r33675
Reset?: Yes
Status: Working, but Wireless Issues

Okay, so did the peakcock thread to update, and it worked just fine. Finally have Gigabit speeds, but the old version I was on would only support up to like 400 MBps. Upgrade, and wired connection is getting around 920 (still not the full 1000, but good to start).

Now, however, the wireless speeds (which were close to the 250 MBps I use to have before Gigabit) are only topping at at like 5 MBps on the 2.4GHz and 50 MBps on the 5GHz. Any suggestions, guys? It's absoutely terrible. Yes, SFE is already set to enabled automatically, and I left that on. No, I don't have QOS enabled.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7273
Location: Texas, USA

PostPosted: Wed Dec 18, 2019 1:40    Post subject: Reply with quote
I'm afraid to ask what your wireless settings are.
_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum