Router: Asus RT-AC5300
Firmware: DD-WRT v3.0-r35927 std 05/13/18
Status: boot loop
Errors: 5Ghz radio Repeater Bridge mode is broken again. VHT160 mode is now missing in GUI.
What was the last build that worked for you on the AC5300 on? Currently, running 35831.
labo wrote:
You have no idea about the issue that I'm talking about it:
I'm not following this response? You state that RB is broken again, insinuating that it was previously working. Right?
Updated some k3.x routers:
Router/Version: Netgear WNDR4000
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: 2.4 GHz CB and 5 GHz AP + VAP
Issues: as others verified, ntp works again
Router/Version: Netgear WNDR4500v2
Firmware: DD-WRT v3.0-r35927 giga ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19136 Sun May 13 12:18:14 CEST 2018 mips
Mode: as above
Issues: as above
Router/Version: Linksys E1500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: nope _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Alright, falling back to 10-20-2017-r33555 and the HTTP webUI bricked again.
When httpd crashes, try `startservice httpd` from telnet/ssh. When I tested 35910, I had this happen on the first GUI try on my WNDR4000, but httpd restarted fine, and never saw it since, after many days. Also, when you set to reset with the flash, you were getting the 'set a password' prompt right? Just making sure the reset worked. I would suggest trying an `erase nvram && reboot` from telnet/ssh, and manually setup...BUT I think some EA-series routers don't handle that well? Or used to? You'd have to search about that.
[Edit: it appears to be fine, peruse here.]
Got the ol' WRTs back from the in-laws over Easter, so updated them to...
Router/Version: Linksys WRT54GLv1.1
Firmware: DD-WRT v3.0-r35927 std-special ( 05/13/18 )
Kernel: Linux 2.4.37 #49358 Sun May 13 06:07:23 CEST 2018 mips
Mode: AP
Issues: File was actually was nokaid_special_generic. Wireless appears ok (for a G router...)
Router/Version: Linksys WRT54GSv6
Firmware: DD-WRT v3.0-r35927 micro ( 05/13/18 )
Kernel: Linux 2.4.37 #49366 Sun May 13 06:16:51 CEST 2018 mips
Mode: AP
Issues: 35531 had issues with the wireless channel list always showing Auto, but that it fixed in 35927.
Going to try them for a while in CB mode soon, for later potential use with my nephew's friends who have 4 Mb/s DSL. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Tue May 15, 2018 3:56; edited 2 times in total
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Mon May 14, 2018 18:36 Post subject:
jwh7 wrote:
zerophase wrote:
labo wrote:
Router: Asus RT-AC5300
Firmware: DD-WRT v3.0-r35927 std 05/13/18
Status: boot loop
Errors: 5Ghz radio Repeater Bridge mode is broken again. VHT160 mode is now missing in GUI.
What was the last build that worked for you on the AC5300 on? Currently, running 35831.
labo wrote:
You have no idea about the issue that I'm talking about it:
I'm not following this response? You state that RB is broken again, insinuating that it was previously working. Right?
Well, With Kong's latest build r35900M and BS previous build, it was not crashing anymore and trying to scan Chanels to connect..
and I believe it is closer to working at least.
And still RB was not getting connected which is probably a minor issue to get fixed.
But now it crashing again which is back to square. and VHT160 mode is removed
Something got fixed partially and broken again which is what I meant.
All three AC5300 routers like Dlink DIR895l, Asus RT-AC5300 and Netgear R8500 have the same issue. _________________ ASUS AXE16000 Main Gateway: Fiber 2gbps up/down
2 X ASUS RT-AX89X: Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
Nighthawk SX10 10GbE Switch
3 X R9000 DD-WRT Mesh
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r35927 std ( 05/13/18 )
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Previous: r35916
Mode/Status: Gateway / working
Reset: no
Issues/Errors: None so far, for my setup.
Uptime: 1 day, 5:04
Temperatures: CPU 64.1 °C / WL0 45.5 °C / WL1 49.3 °C
Router Model: Buffalo WZR-1750DHP
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Previous: DD-WRT v3.0-r35900M kongac (05/08/18)
Status: AP / Local DNS / QoS HFSC - FQ-CODEL/ Static DHCP x 12
Errors: No specific errors ...
Router Model: Linksys EA6500
Firmware: DD-WRT v3.0-r35916 giga (05/11/18)
Kernel: Linux 3.10.108-dd #19106 Fri May 11 18:09:37 CEST 2018 mips
Previous: DD-WRT v3.0-r35452 giga (03/20/18)
Reset: GUI
Status: Client Bridge (5GHz)
Errors: Initially working well. Needed power cycle to complete flash.
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Previous: DD-WRT v3.0-r35452 std (03/20/18)
Reset: GUI
Status: Client Bridge (5GHz)
Errors: Initially working well.
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Previous: DD-WRT v3.0-r30631 std (09/14/16)
Reset: GUI
Status: VPN AP
Errors: First OpenVPN 2.4 build I've tried that seems relatively stable.
Router Model: Linksys E3000
Firmware: DD-WRT v3.0-r35927 mega (05/13/18)
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Temperatures: WL0 59.0 °C / WL1 60.5 °C
Previous: DD-WRT v3.0-r34777 (01/31/18)
Reset: GUI
Status: Backup AP
All the broadcom units seem to be a little erratic with QoS. May be compounded
by my asymmetrical 18/1.5 AT&T service.
Alright, falling back to 10-20-2017-r33555 and the HTTP webUI bricked again.
When httpd crashes, try `startservice httpd` from telnet/ssh. When I tested 35910, I had this happen on the first GUI try on my WNDR4000, but httpd restarted fine, and never saw it since, after many days. Also, when you set to reset with the flash, you were getting the 'set a password' prompt right? Just making sure the reset worked. I would suggest trying an `erase nvram && reboot` from telnet/ssh, and manually setup...BUT I think some EA-series routers don't handle that well? Or used to? You'd have to search about that.
[Edit: it appears to be fine, peruse here.]
Got the ol' WRTs back from the in-laws over Easter, so updated them to...
Router/Version: Linksys WRT54GLv1.1
Firmware: DD-WRT v3.0-r35927 std-special ( 05/13/18 )
Kernel: Linux 2.4.37 #49358 Sun May 13 06:07:23 CEST 2018 mips
Mode: AP
Issues: File was actually was nokaid_special_generic. Wireless appears ok (for a G router...)
Router/Version: Linksys WRT54GSv6
Firmware: DD-WRT v3.0-r35927 micro ( 05/13/18 )
Kernel: Linux 2.4.37 #49366 Sun May 13 06:16:51 CEST 2018 mips
Mode: AP
Issues: 35531 had issues with the wireless channel list always showing Auto, but that it fixed in 35927.
Going to try them for a while in CB mode soon, for later potential use with my nephew's friends who have 4 Mb/s DSL.
lol.... I'm not too familiar with telnet/ssh since I'd quitted the IT professional industries over 10 years ago already, let alone the router devices Linux systems, totally not professional, so you may have to teach me how.
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response! much stabler than all builds since Nov 2017 until now! So buggy, too buggy for my EA2700, from the builds of Nov 2017 until r35927. I guess Linux kernel 3.10.108 is not really compatible with my Linksys EA2700. My EA2700 can run only 3.10.107 really fine, I guess so, it seems like
I have no ideas why the builds of DD-WRT in these months become much dirtier and dirtier, much buggier and buggier...... I have completely no ideas about what the hell is really going on with the developers of DD-WRT in these months, ruined the routers. (facepalm)
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!
Weren't you saying before that you had issues in 33555? So it might be that a hard reset in 35927 might work as well?
Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: All appears ok _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 06 Jun 2006 Posts: 7445 Location: Dresden, Germany
Posted: Wed May 16, 2018 4:28 Post subject:
labo wrote:
Router: Asus RT-AC5300
Firmware: DD-WRT v3.0-r35927 std 05/13/18
Status: boot loop
Errors: 5Ghz radio Repeater Bridge mode is broken again. VHT160 mode is now missing in GUI.
Coredump:
ERROR: Necessary service setting not found: milkfish_username - aborting.
The Milkfish Router Services
Restoring SIP ddsubscriber database from NVRAM…
Empty.
The Milkfish Router Services
Restoring SIP ddaliases database from NVRAM…
Empty.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = 80004000
[00000000] *pgd=00000000
Internal error: Oops - BUG: 80000007 [#1] SMP ARM
Modules linked in: shortcut_fe dhd wl(P) igs(P) emf(P) switch_robo switch_core et(P)
CPU: 1 PID: 207 Comm: kworker/1:1 Tainted: P 4.4.131 #3086
Hardware name: Northstar Prototype
Workqueue: events _254 [dhd]
task: 87bc2800 ti: 87bca000 task.ti: 87bca000
PC is at 0x0
LR is at _939+0x6c/0xa8 [dhd]
pc : [<00000000>] lr : [<7f45fcac>] psr: 80000013
sp : 87bcbe70 ip : 80441f40 fp : 87bcbea4
r10: 00000000 r9 : 00000004 r8 : 00000000
r7 : 00000000 r6 : 87b46dc0 r5 : 00000000 r4 : ffffe000
r3 : 87bcbe70 r2 : 00000004 r1 : 8500a000 r0 : 87b46dc0
Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 070e404a DAC: 00000055
Process kworker/1:1 (pid: 207, stack limit = 0x87bca190)
Stack: (0x87bcbe70 to 0x87bcc000)
be60: 00000000 00000000 857e1900 87b67400
be80: 857e1980 857e8000 a0000013 00000000 00000000 8050ba84 87bcbec4 87bcbea8
bea0: 7f45fd24 7f45fc4c 857e19a0 857e1980 0000000c a0000013 87bcbef4 87bcbec8
bec0: 7f461db8 7f45fcf4 87bcbf0c 87853d08 87b67400 7f45fce8 857e1980 87b92780
bee0: 86be1480 86be6e00 87bcbf24 87bcbef8 8004d42c 7f461d14 00000000 8050ba84
bf00: 87b92780 86be1480 86be1480 87b92798 86be1494 00000000 87bcbf5c 87bcbf28
bf20: 8004e59c 8004d284 804fe100 87bca000 00000000 00000000 87b93780 87b92780
bf40: 8004e39c 00000000 00000000 00000000 87bcbfac 87bcbf60 80052890 8004e3a8
bf60: 40000000 00000000 00000000 87b92780 00000000 00000000 87bcbf78 87bcbf78
bf80: 00000000 00000000 87bcbf88 87bcbf88 87b93780 80052798 00000000 00000000
bfa0: 00000000 87bcbfb0 80009600 800527a4 00000000 00000000 00000000 00000000
bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 87bcbff4 00000000
Backtrace:
[<7f45fc40>] (_939 [dhd]) from [<7f45fd24>] (_336+0x3c/0xfc [dhd])
r10:8050ba84 r9:00000000 r8:00000000 r7:a0000013 r6:857e8000 r5:857e1980
r4:87b67400
[<7f45fce8>] (_336 [dhd]) from [<7f461db8>] (_254+0xb0/0xbc [dhd])
r7:a0000013 r6:0000000c r5:857e1980 r4:857e19a0
[<7f461d08>] (_254 [dhd]) from [<8004d42c>] (process_one_work+0x1b4/0x2d8)
r7:86be6e00 r6:86be1480 r5:87b92780 r4:857e1980
[<8004d278>] (process_one_work) from [<8004e59c>] (worker_thread+0x200/0x3e4)
r9:00000000 r8:86be1494 r7:87b92798 r6:86be1480 r5:86be1480 r4:87b92780
[<8004e39c>] (worker_thread) from [<80052890>] (kthread+0xf8/0x100)
r10:00000000 r9:00000000 r8:00000000 r7:8004e39c r6:87b92780 r5:87b93780
r4:00000000
[<80052798>] (kthread) from [<80009600>] (ret_from_fork+0x14/0x34)
r7:00000000 r6:00000000 r5:80052798 r4:87b93780
Code: bad PC value
—[ end trace 6634b0e0931cb9b6 ]—
Kernel panic - not syncing: Fatal exception
CPU0: stopping
CPU: 0 PID: 0 Comm: swapper/0 Tainted: P D 4.4.131 #3086
Hardware name: Northstar Prototype
Backtrace:
[<8001b950>] (dump_backtrace) from [<8001bbd8>] (show_stack+0x18/0x1c)
r7:804f1f20 r6:60000193 r5:00000000 r4:80510da0
[<8001bbc0>] (show_stack) from [<8016401c>] (dump_stack+0x8c/0xa0)
[<80163f90>] (dump_stack) from [<8001d754>] (handle_IPI+0x110/0x1a8)
r7:804f1f20 r6:00000000 r5:00000000 r4:805231a0
[<8001d644>] (handle_IPI) from [<80009394>] (gic_handle_irq+0x78/0x7c)
r7:b0100100 r6:804f1f20 r5:b010010c r4:804ffb1c
[<8000931c>] (gic_handle_irq) from [<80009ea0>] (__irq_svc+0x40/0x54)
Exception stack(0x804f1f20 to 0x804f1f68)
1f20: 86bd4248 00000000 00040128 8000a9c0 804f0000 804ff8e0 80433a50 804ec224
1f40: 804f1f90 804c38c8 00000000 804f1f7c 804f1f80 804f1f70 80019564 80019568
1f60: 60000013 ffffffff
r9:804c38c8 r8:804f1f90 r7:804f1f54 r6:ffffffff r5:60000013 r4:80019568
[<8001952c>] (arch_cpu_idle) from [<8006c424>] (default_idle_call+0x30/0x34)
[<8006c3f4>] (default_idle_call) from [<8006c530>] (cpu_startup_entry+0x108/0x13c)
[<8006c428>] (cpu_startup_entry) from [<80012aac>] (rest_init+0x80/0x84)
r7:80523020 r4:00000000
[<80012a2c>] (rest_init) from [<8049acc0>] (start_kernel+0x320/0x32c)
[<8049a9a0>] (start_kernel) from [<0000807c>] (0x807c)
Rebooting in 10 seconds..
the crash is related to your repeater bridge tries. the ac5300 has no repeater bridge nor client bridge support. i still left it in the gui for testing. the differences on these devices is that they are all based on a own wifi firmware on the wifi chip itself which will it make impossible to implement fake bridge modes. it may work under some conditions, but officially i cannot support this.
disable it. use client mode or repeater or ap mode, everything else will likelly fail
fo the missing vht160 mode. this is a bug fix. the ac5300 has no vht160 support
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Status: VPN AP
CPU Model: Broadcom BCM4708
CPU Cores: 2
CPU Features: EDSP
CPU Clock: 800 MHz
Load Average: 59% 1.00, 1.21, 1.31
Temperature: CPU 64.7 °C / Not available
After some moderate streaming, load averages reported >1. Graph (59%) probably close. Radios are turned off ATM.
But anyway, done a hard reset (30s power on, 30s power off, 30s power on) soon before and now the WebUI become fine again And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!
Weren't you saying before that you had issues in 33555? So it might be that a hard reset in 35927 might work as well?
Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Mode: AP
Issues: All appears ok
No issues in r33555, that's the stablest ever DD-WRT for my EA2700. Only all builds after r33555 until now are buggier and buggier.
What I meant was, when I was flashing the firmware back to r33555 via the Web page of r35927, it bricked the http web interface, can't load http://192.168.1.1 by any browsers, but the router still worked, can still go through to facebook or any other websites else.
The web service bricked until I'd done a hard reset, then I could load into http://192.168.1.1 and saw the page showed me that's r33555. Then I'd just re-flashed to r33555 one more time by the web page of r33555, smoothly successful like a virgin. Now all things just are running very well, no more wifi sessions hangs.
Wireless Mode: AP
Wireless Network Mode: Mixed
Security Mode: WPA2 Personal Mixed
WPA Algorithms: TKIP+AES
Regulatory Domain: Hong Kong
Router Name: "Cisco Linksys EA2700"
Timezone: Asia/Hong_Kong
Time Server Host: stdtime.gov.hk
NAT sessions: 65536
UPnP enabled
WPA2 Personal Mixed and TKIP+AES are really running very fine in r33555 without any Wifi jams, but only hang wifi from r33607 until r35927 for my EA2700.
All my Wifi clients are android phones, an LG smart TV and a Windows 10 notebook with Broadcom Wireless Adapter. The rest 2 Windows 10 desktop PCs are wired connections. No any connection hangs for ethernet, they're always fine.
And yes, the 'set a password' prompt appeared fine at the first screen, just set passwords, login to the reset r33555 then flashed the r33555 again one more time. So now everything is running fine, really fine! no more wifi hangs, the router's wifi signals always response!