Router/Version: Asus RT-AC68U rev. A1
Firmware: DD-WRT v3.0-r45493 std (01/19/21)
Kernel: Linux 4.4.252 #1865 SMP Tue Jan 19 11:00:40 +07 2021 armv7l
Mode: Gateway / AP
Reset: No, flashed from CLI
Previous: 01-13-2021-r45420
Status: Working well. _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Firmware: v3.0-r45493 std (01/19/21)
Router/Version: Netgear R7000 Kernel: Linux 4.4.252 #1865 SMP Tue Jan 19 11:00:40 +07 2021 armv7l
Previous: v3.0-r45420 std (01/13/21)
Mode/Status: AP wired and wireless, Up and running for 1 day.
Reset: Soft boot before and after upgrade
Temperatures: CPU 56.4 °C / WL0 44.5 °C / WL1 49.6 °C
Issues/Errors: Nothing significant
Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
There is a mysterious "Sysctl" tab in the Administration tab that seems to allow a lot of fine-tuning. It is very tempting to change some of these just to see what happens.
There is a minor issue with the packet count on wl0.1 and "Connected Clients" stuck at zero. The wl0 and wl1 counts seem correct.
Upload and Download speeds are to ISP spec. Nothing unexpected in the syslog.
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 custom scripts
- NO: ttraf, Tor, VNC, Zabbix, VPN, Radius, OpenVPN
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Router/Version: Asus RT-AC66U /
File/Kernel: dd-wrt-45493-Asus_RT-AC66U.trx / Linux 4.4.252 #6313 Tue Jan 19 18:23:57 +07 2021 mips
Previous/Reset: v3.0-r44772 / no
Mode/Status: AP, Gateway, Router / OK
Issues/Errors: no / no (other than mitigated uncorrectable ECC errors)
Router Model: Netgear R8000
Firmware Version: DD-WRT v3.0-r45493 std (01/19/21)
Kernel Version: Linux 4.4.252 #1873 SMP Tue Jan 19 12:02:19 +07 2021 armv7l
Previous Version: DD-WRT v3.0-r45420 std (01/13/21)
Drivers: Experimental
Services: samba, wireguard client, openvpn client, dhcp, wifi 2.4 ghz, usb, nas
Status: working
Updated: via webgui
Mode: AP/gateway
Issues: none
Reset: no
Reboot: hard reboot
Uptime: 19:14
Temperatures: CPU 46.4 °C
Errors: as reported in the syslog below
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-manager/1174]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-worker/1175]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-worker/1175]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Dec 31 20:00:20 DD-WRT user.err wsdd2[1163]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jan 20 21:52:25 DD-WRT user.err wsdd2[1163]: Terminated received.
Jan 20 21:52:25 DD-WRT local5.err ksmbd: [ksmbd-manager/1174]: ERROR: WARNING: child process exited abnormally: 1175
Jan 20 21:52:26 DD-WRT local5.err ksmbd: [ksmbd-worker/2257]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Jan 20 21:52:26 DD-WRT local5.err ksmbd: [ksmbd-worker/2257]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Jan 20 21:52:29 DD-WRT local5.err ksmbd: [ksmbd-manager/2557]: ERROR: Failed to create lock file: File exists
Jan 21 17:04:08 DD-WRT daemon.err httpd[1420]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Joined: 14 Sep 2019 Posts: 301 Location: Maine, USA
Posted: Fri Jan 22, 2021 17:15 Post subject:
Router/Version: Asus RT-N66U
File: dd-wrt.v24-45493_NEWD-2_K3.x_mega_RT-N66U.trx
Firmware: DD-WRT v3.0-r45493 mega (01/19/21)
Kernel: Linux 4.4.252 #6329 Tue Jan 19 18:48:51 +07 2021 mips
Mode: Gateway/USB
Previous: r45420
Reset?: N
Status: Working
Router/Version: Linksys E3200
File: dd-wrt.v24-45493_NEWD-2_K3.x_mega-e3200.bin
Firmware: DD-WRT v3.0-r45493 mega (01/19/21)
Kernel: Linux 4.4.252 #6329 Tue Jan 19 18:48:51 +07 2021 mips
Mode: Guest Gateway/QOS
Previous: r45420
Reset?: N
Status: Working
Joined: 08 Apr 2017 Posts: 49 Location: Underground lair
Posted: Fri Jan 22, 2021 17:46 Post subject:
Router/Version: Netgear R8000
File/Kernel: r45493 experimental/Linux 4.4.251
Previous/Reset: r45454 experimental/yes
Mode/Status: Primary gateway/Working. Seems pretty stable. Performance is good. VAP is working and bridged.
Issues/Errors: Wireless stops working entirely after any change to wireless settings if "Apply Settings" is used. Have to power cycle to restart. The other option is to only use "Save", then reboot when I'm ready to apply.
Something else I quickly discovered is there are dozens of wireless setting combinations that simply do not work at all and only a handful that do. For instance, I cannot use 40MHz on the 2.4GHz radio. It will not transmit a signal. Nor does 40MHz work on the 5GHz radio, only 20MHz/NG-Mixed or 80MHz/AC,N-Mixed. Any other combination leaves the radios off regardless of what the status page says.
Enabling single user beam forming on the 5GHz radios kills them. So too does LL(-6) and UU(+6). It's LU(-2) and UL(+2) or nothing.
And glutton for punishment that I am, I have two more e4200's on the way which I will again try to install DD-WRT. I will also be upgrading my e1200 v1 and WRT54G v3 and posting my results here.
Edit: AFter more testing I retract my comment that VAP is working. It broadcasts SSID but rejects all connections. _________________ Routers: Netgear R8000, Linksys E1200v1, E4200, WRT54Gv3, TL-WDR4300v1.7
Last edited by ZeroLabs on Sat Jan 23, 2021 3:31; edited 2 times in total
Forgot to do hard reset: My own fault for forgetting.
does the k24 mean 2.4ghz? how do i know what kernel im running? maybe that's why it's not working......
Had access to gui for a moment and it would let me try a password, totally locked out. tried admin/root/no password
then i couldn't access the landing page at all
had solid power light and reflashed with linksys tftp from their download page back to stock firmware during the first few seconds of a power cycle.
recovered to stock linksys firmware.
always try the recovery mode which is unplug router, plug back in and hold reset for five seconds as you're pluggin in, check ping -t 192.168.1.1 for ttl= replies and flash with tftp. if you have solid wlan and power you're not bricked.
I have the same router (WRT54GL 1.1) and it appears bricked as well - Flashing power light is all that happens. 30/30/30 no response. you are right, the switch appears to still work, but it's dead as a router. Since this is a spare to me, I might try to recover by shorting it again - it fixed it last time, and I was able to tftp Linksys firmware to it, and then flash DDWRT.
my solution for recovery of Linksys WRT54GL v1.1 due to 45493 flash fail
tho was limited on bins i had
Code:
+ (ye buttony reset) > TFTP flash factory firmware ( FW_WRT54GL_4.30.17.011_ETSI_20150623.bin_)
+ (ye factory reset) > 36300 mini gen ( kernel: Linux 2.4.37 #49934 Mon Jul 16 10:05:27 CEST 2018 mips )
+ (no factory reset) > 44715 std spec ( kernel: Linux 2.4.37 #62650 Tue Nov 3 07:12:35 +03 2020 mips )
+ (no factory reset) > 45493 std spec >>>>>> {FAILURE}
+ (ye factory reset) > 45493 std spec >>>>>> {FAILURE}
note: used only the short push-restart-pin until it blink power LED and does restart
build 44715 works, changes saving, restarts too
multiple attempts to get any feasible 45393 ends in failure to respond except TFTP to original fw
Posted: Sat Jan 23, 2021 21:01 Post subject: WRT54GSv1
Soft bricked again back to 45229. Updated via WebUI, recovery through CFE boot break then tftp 45229 build. Attached is all serial output from upgrade, log queries, and tftp recovery.
I have the same router (WRT54GL 1.1) and it appears bricked as well - Flashing power light is all that happens. 30/30/30 no response. you are right, the switch appears to still work, but it's dead as a router. Since this is a spare to me, I might try to recover by shorting it again - it fixed it last time, and I was able to tftp Linksys firmware to it, and then flash DDWRT.
my solution for recovery of Linksys WRT54GL v1.1 due to 45493 flash fail
tho was limited on bins i had
Code:
+ (ye buttony reset) > TFTP flash factory firmware ( FW_WRT54GL_4.30.17.011_ETSI_20150623.bin_)
+ (ye factory reset) > 36300 mini gen ( kernel: Linux 2.4.37 #49934 Mon Jul 16 10:05:27 CEST 2018 mips )
+ (no factory reset) > 44715 std spec ( kernel: Linux 2.4.37 #62650 Tue Nov 3 07:12:35 +03 2020 mips )
+ (no factory reset) > 45493 std spec >>>>>> {FAILURE}
+ (ye factory reset) > 45493 std spec >>>>>> {FAILURE}
note: used only the short push-restart-pin until it blink power LED and does restart
build 44715 works, changes saving, restarts too
multiple attempts to get any feasible 45393 ends in failure to respond except TFTP to original fw
I was able to recover by TFTP, original Fw, then loaded 44970 std generic, and I'm back in business. _________________ ASUS RT-AC3100 AP Merlin 386.12_4
ASUS RT-AC68U Media Bridge/Merlin 386.12_4 (x2)
ASUS RT-AC68U AP r54604
ASUS RT-AC68U Gateway/AP r54604
Edgerouter-4, v2.0.9-hotfix7