Wanted to flash my devices in order to give results tomorrow after extensive testing.
R7000 (WAN PPP VLAN7) update r45677 to this one.
no routing possible anymore, connected devices no connection to internet, router seemingly not able to access internet after receiving time via ntp.
Was able to access webinterface and downgraded back to r45677.
Not a BCM device, but same happend to my WRT1900acsv2 (WAN IP NO VLAN). Recovered it also by flashing older release.
N66u update r45677 to this one (dd-wrt.v24-45735_NEWD-2_K3.x-big-RT-N66U.trx)
Device does only boot into mini CFE, no webinterface anymore.
Reboot only results in mini CFE again.
TFTPing r45677 again resulted in device becoming unresponsive.
Searching for this console cable
Reissued r45677 via TFTP in console and everything is fine again.
Router came up, wireguard came up.
DOn't know what is with this build will omit 02/11/2021 - r45735
I'd like to help solve the "does only boot into CFE issue" for N66u with this release:
As it looks like another user reported also having only CFE boot and no GUI.
I fetched another n66u of mine and saved the normal boot phase (with old firmware, see putty login.log)) and the whole upgrade process including reboot (see putty update and problem.log).
This does look like the cause for the device not being able to boot into GUI:
squashfs: SQUASHFS error: unable to read inode lookup table
List of all partitions:
0100 4096 ram0 (driver?)
0101 4096 ram1 (driver?)
0102 4096 ram2 (driver?)
0103 4096 ram3 (driver?)
0104 4096 ram4 (driver?)
0105 4096 ram5 (driver?)
0106 4096 ram6 (driver?)
0107 4096 ram7 (driver?)
0108 4096 ram8 (driver?)
0109 4096 ram9 (driver?)
010a 4096 ram10 (driver?)
010b 4096 ram11 (driver?)
010c 4096 ram12 (driver?)
010d 4096 ram13 (driver?)
010e 4096 ram14 (driver?)
010f 4096 ram15 (driver?)
1f00 256 mtdblock0 (driver?)
1f01 32384 mtdblock1 (driver?)
1f02 23129 mtdblock2 (driver?)
1f03 128 mtdblock3 (driver?)
1f04 7168 mtdblock4 (driver?)
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
Please stand by while rebooting the system...
Let me know if further information is needed, I'll happily help.
Router/Version: Linksys WRT54GS v1.1
File/Kernel: dd-wrt.v24_mini_generic.bin (r45735) / Linux 2.4.37 #64064 Thu Feb 11 09:36:14 +06 2021 mips
Previous/Reset: r43190 (May 18th 2020)/Yes (I did a factory reset through 'Admin > Factory Defaults' prior to flashing through 'Admin > Firmware Upgrade')
Mode/Status: Standard use (Access point)
Issues/Errors: Everything appears to be okay so far.
NOTE: I am running it at 240MHz (which I did on r43190 without issue). default is 216MHz. I noticed resetting through interface (i.e. Admin > Factory Defaults) does not clear the overclock, but I think that is normal. but holding reset for 30 seconds does clear the overclock and puts it back to it's 216MHz default. so when I flashed, it was still at 240MHz. I would imagine it's probably safer to say hold reset button for 30 seconds and then proceed to flash through the interface though.
I upgraded from DD-WRT r43190 (from May 18th 2020) as I just reset to factory defaults first (Admin > Factory Defaults) then after reboot, entered a username/password, then upgraded through the Admin > Firmware Upgrade. I used 'After flashing, reset to = Don't reset'. then after that finished (wait 5 minutes to be extra safe), I just held reset on the router for 30 seconds and then reconfigured router to my liking.
p.s. I would have stayed on r43190 but I noticed there was some security issue with Dnsmasq about a month ago that I just very recently noticed (i.e. https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327899 ; but from what I can tell it does not appear anyone has exploited stuff like that so it's probably not critical to update but still a good idea) and it appeared to be a good idea to upgrade. so here I am on r45735.
SHA256SUM of dd-wrt.v24_mini_generic.bin (r45735)= "27dcdc4bb3ba743b53b04e25acb2a557b3256b6dae51ba1489a92a80e3efb6f2" _________________ Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r46239 Apr 1st 2021) ; new Panasonic capacitors Feb 11th 2020 | ASUS WL-520gU /w dd-wrt.v24_mini_generic (r46329 Apr 13th 2021) | Linksys WRT54GS v6 /w DD-WRT v24-12548_NEWD_micro | Belkin F5D7230-4 v1444 (bricked on Apr 6th 2021)
The only thing I am a little iffy on is the ack timing setting being 0. That may be what is breaking it. With all of the changes over the past couple of years or so, I don't know what the proper settings are for Broadcom, I used to always leave it at the old default of 2000. Apparently, the new recommendation is 90-500, or 0.
the default setting on that page is (Default: 500 meters) - it's not visible because I cropped the screenshot to fit the 768px rule.
I've set the ACK timing to 500, Save & Apply. Key Renewal Interval is 0 now. I'll report the result after one day. Thanks for your help.
there are still some "user.info : nas : daemon successfully stopped" in the log. The settings were applied on Feb 15 at 12:01
You don't have any time / access restrictions enabled, do you? I don't see why the nas daemon keeps flaking, that shouldn't be happening unless a client is crashing the wireless. I would have to flash this build on my R7000P and reconfigure it to swap out with my WRT3200acm to see if it is having these issues. I generally leave the ack timing at 2000 and gtk rekey at 3600 and have seen no issues in the past.
no, both Radio Scheduling and Access Restrictions are disabled.
my only wireless client device is Xiaomi Redmi Note 9 Pro Global (joyeuse) running stock ROM (Android 10)
Router/Version: Asus RT-AC66U /
File/Kernel: dd-wrt-45677-Asus_RT-AC66U.trx / Linux 4.4.255 #6793 Thu Feb 11 18:26:50 +06 2021 mips
Previous/Reset: v3.0-r45632 / no
Mode/Status: AP, Gateway, Router / OK
Issues/Errors: no / no
Joined: 16 Mar 2019 Posts: 174 Location: Szczecin, Poland EU
Posted: Wed Feb 17, 2021 21:07 Post subject: New Build - 02/11/2021 - r45735
Router: Netgear WNR3500L v2
Kernel: Linux 4.4.255 #6793 Thu Feb 11 18:26:50 +06 2021 mips
Mode: Internet gateway, WIFI AP, Dnsmasq server
Errors: kern.warn kernel: br0: received packet on eth1 with own address as source address. This error is repeated many times.
I'm update device via ssh. I have error with MACs. I don't know how to fix it. Router is online, I don't see any significant problem.
Router/Version: Netgear WNDR4000
File/Kernel: v3.0-r45735 mega (02/11/21)/Linux 4.4.255 #6809
Mode/Status: AP/full access wifi and guest wifi
I installed this WNDR4000 to replace a TP-Link WR1043ND which was easier to get up and running in the desired configuration but had intermittent wifi dropouts.
On the newly installed WNDR4000 I followed this blog post to add guest wifi access isolated from the rest of my LAN. But initially clients were not able to connect to the guest wifi. With help from previous forum posts I managed to fix that. This bit of additional code made it happen. It was added to the startup code, under Administration-Command-Startup.
For now it seems to be running well. Hoping to see stable wifi guest access over the next couple of days.
Note on power consumption
This WNDR4000 seems to consume a bit more juice compared to the TP-Link. So I tried if lower clock speed would help. From stock 480MHz back down to 300MHz doesn't seem to make a difference, so I settled in the middle at 400MHz. Perhaps the extra power consumption has to do with two radio's rather than one. This box has both 2.4 and 5 GHz, even though I only use 2.4GHz.