Posted: Thu Apr 01, 2021 10:08 Post subject: New Build - 04/01/2021 - r46239
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• DNScrypt 1.95 can still be used in the GUI, but v2 (not compatible) requires Golang and thus Entware. #6246
• WDS does not work on Broadcom ARM devices(only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs in40562 - 40566. Effective startup commandsdiscussion thread is here.
• If start-up scripts do not work from USB add a delay, e.g. wait script or 'sleep 25'.
• Broadcom ARM devices if 5 GHz channels are missing, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Router/Version: Linksys wrt320n
File: dd-wrt.v24-46239_NEWD-2_K3.x_mega_wrt320n
Kernel: Linux 4.4.264 #7897 Thu Apr 1 12:36:24 +07 2021 mips
Previous: 46130
Reset: Yes
Mode/Status: Defaults with wifi
Issues/Errors: Yes, I can't set a strong router username and password. Also, the time Windows spends "checking network requirements" when trying to connect to wifi after a router power cycle when it can see the wireless network seems to take longer than other recent builds.
*After reset, I configured the router using a basic username and password while doing so, and on each page first saving, then applying.
*Then I enable https Web Access and disable http, save, and apply
*Then I login to https site
*Then I attempt to set a stronger username and password, save, and apply
*Upon hitting save, Firefox (Private Browsing) prompts me to login again. When I do, it immediately displays these errors, usually the first one, but sometimes the second if I refresh:
An error occurred during a connection to x.x.x.x PR_END_OF_FILE_ERROR
An error occurred during a connection to x.x.x.x PR_CONNECT_RESET_ERROR
The only way to get back into the router is to power cycle, and the new username and password have not been applied. However, if I change the user and password to something simple, but different than before, the settings apply and I can log in with them. Have un/pw special character requirements changed?
EDIT:
In testing again, I can repeat the steps below to trigger the problems.
I try a different weak un and pw than before and only hit save. After ~15 seconds, Firefox prompts me to log in. That works. Then I hit apply. While it says "Processing... Please, wait", the wireless connection disconnects. I close and open a new browser. I reconnect to wifi (Windows is set to not reconnect automatically). I can login with the new weak un and pw.
The above is repeatable with different weak un/pw, including the wireless connection disconnecting when I hit apply. If I set a strong un and pw and hit save, then when it prompts me to login and I reenter the strong un/pw, it does not accept the credentials. I try the old weak un/pw and get to the Management screen. As soon as I click anything, I get:
An error occurred during a connection to x.x.x.x PR_CONNECT_RESET_ERROR
I power cycle the router and I can again log in with the old weak un/pw.
Last edited by mastaofdisastax on Fri Apr 02, 2021 12:10; edited 9 times in total
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r46239 std (04/01/21) (prev. DD-WRT v3.0-r46220 std (03/31/21))
Kernel: Linux 4.4.264 #2404 SMP Thu Apr 1 06:50:30 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: As mentioned in report for previous release, after update was done and unit rebootet, the syslog was filled with red lines.
This time I was able to save /var/log/messages and dmesg. See attached document.
After reboot or powercycle this error is gone and seemingly cannot be triggered again.
Hardware Problem?
Router/Version: Asus RT-N66U
File: dd-wrt.v24-46239_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r46239 big (04/01/21) (prev. DD-WRT v3.0-r46220 big (03/31/21))
Kernel: Linux 4.4.264 #7893 Thu Apr 1 12:31:35 +07 2021 mips
Mode: Gateway, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: 1h:42 up, ok.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Apr 02, 2021 14:54 Post subject:
Zyxx wrote:
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r46239 std (04/01/21) (prev. DD-WRT v3.0-r46220 std (03/31/21))
Kernel: Linux 4.4.264 #2404 SMP Thu Apr 1 06:50:30 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: As mentioned in report for previous release, after update was done and unit rebootet, the syslog was filled with red lines.
This time I was able to save /var/log/messages and dmesg. See attached document.
After reboot or powercycle this error is gone and seemingly cannot be triggered again.
Hardware Problem?
Router/Version: Asus RT-N66U
File: dd-wrt.v24-46239_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r46239 big (04/01/21) (prev. DD-WRT v3.0-r46220 big (03/31/21))
Kernel: Linux 4.4.264 #7893 Thu Apr 1 12:31:35 +07 2021 mips
Mode: Gateway, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: 1h:42 up, ok.
do
nvram set console_debug=1
nvram commit
so i see where it happend. i can at least tell you that it s related to a connected usb drive _________________ "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
Command inserted, will report, as soon as something happens again / when next update hits.
And you are right. A few monthts ago I had an USB stick connected, didn't need it anymore and disabled USB Core Support BUT left USB Storage Support enabled...
Did not change the settings, did not hit apply, will wait for next event.
Code:
root@R7000:~# nvram set console_debug=1
root@R7000:~# nvram commit
ledtool 1
ledtool 1? Hmm, as soon as nvram commit is issued this output happens *shrug* will see
Issues:
There is still the appearance and growth of the .meta folder with the file name similar to the one I saved in its folder with that name, i.e. if the file I saved name bob, I placed it in a folder named bob. The .meta folder will appear in my bob’s folder and grows with a file inside name bob also. The program used to read the file I saved named bob cannot read the file name bob in the .meta folder. Currently the file I saved is 1.32 Gb and the .meta folder and file is 26.9 GB. Prior to ntfs3, the .meta folder and file grew to around 170 bytes
You cannot write, but you can delete, data across the network with windows explorer directly to the share folder on the external drive. You must directly attach the external drive to a computer.
EDIT: After removing a lot of the text in this post... r46239 works on Linksys WRT54GS v1.1. but avoid overclocking the router (I am back on 216Mhz which is the stock speed) as it seems to cause issues vs my previous build of r45735 (Feb 11th 2021) which does not seem to mind the 240Mhz overclock (NOTE: overclocking is done at your own risk as if your note careful it can brick the router!)
with that said... if someone does have issues (like reset button not working, 192.168.1.1 interface not working and no internet) on a WRT54GS v1.1 router with this r46239 build it seems a way to bring it back to life is to... unplug router, wait a little bit, press reset button, and while still holding reset button, plug the router in and count 30 seconds, release reset button. then after a short while you should be able to access the 192.168.1.1 page once again. but if this stuff happens to you and you don't want to mess around with it, r45735 is a good build that I did not have a issue with. _________________ Primary Router: Linksys WRT54GS v1.1 /w dd-wrt.v24_mini_generic (r46640 May 13th 2021) ; new Panasonic capacitors Feb 11th 2020 | Backup Router: Linksys WRT54GS v6 /w dd-wrt.v24_micro_generic (r46640 May 13th 2021)
Last edited by ThaCrip on Tue Apr 06, 2021 15:21; edited 3 times in total