Posted: Thu Feb 24, 2022 9:00 Post subject: New Build - 02/24/2022 - r48425
Welcome to Broadcom r48425 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, 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:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• DNScrypt 1.95 can still be used in WebUIbut v2 (not compatible) requires Golang and thus Entware. See Trac ticket #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. Try client or repeater modes, but YMMV.
• VAPs not working at bootare fixed, both unbridged (r40634) and bridged (r47822). Please test, removestartup commands.
• If startup scripts do not work from USB add delay (wait script), sleep 25 or try Administration -> Commands -> Save USB.
• Broadcom ARM devices if 5 GHz channels are missingvia Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT WAN: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & /tmp/.ipt. Misc: stracetcpdumpwireshark.
• Gremlins: reset & configure manually, not restore a backup. Reboot. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) and applicable configurations to reproduce.
Firmware did not process correctly via WebUI (Edge) > WebUI unresponsive. Power cycled > UI reports as being previous version. Tried firmware upgrade again > No problems.
Wireless clients being lazy again today. But I see all SSIDs are present & correct, so not worried and expect clients shortly. _________________ Hardware (Device/Firmware/Roles):
Netgear RAX50 | Stock | Gateway, DHCP, AP, NAS.
Netgear WNDR4500v2 | FreshTomato | Router, WAP (2G), WDS-AP (5G), Samba, Torrent Client.
Netgear WNDR4500v2 | FreshTomato | Router, WAP (2G), WDS-AP (5G).
Router/Version: Trendnet TEW811DRU / DD-WRT v3.0-r48425 mini (02/24/22)
File/Kernel: trendnet-811dru-webflash.bin / Linux 4.4.302 #5319 Thu Feb 24 08:14:07 +07 2022 armv7l
Previous/Reset: DD-WRT v3.0-r48402 mini (02/20/22)/no
Mode/Status: Client AP/ Booted ok Temps: CPU 79.1 °C / WL0 54.4 °C / WL1 60.0 °C
Issues/Errors: after 15 mins, navigating to Status_Lan.asp and Status_Router.asp seems sluggish for newly booted router
reverted to 48402,lag is noticeable less
Last edited by angler on Sat Feb 26, 2022 11:07; edited 2 times in total
Posted: Fri Feb 25, 2022 15:15 Post subject: All good
Router/Version: Asus RT-AC5300
File/Kernel: asus_rt-ac5300-firmware-DDWRT-48425.trx Linux 4.4.302 #5321 SMP Thu Feb 24 08:24:00 +07 2022 armv7l
Previous/Reset: r46442 / No
Mode/Status: Router, AP (multiple WAP), Entware, YaMon 3 / All good
Issues/Errors: No issues noted after 18 hours uptime.
Big jump in version for me but went perfectly via the webUI, did not reset. No issues noted, and bonus! throughput is measurably faster (don't know why so treat as apocryphal).
Hello. Jump backed into this and loaded this in 3 wrt's. Seeing if posting works. Didnt work yesterday. Cool. Ill edit this.
Router wrt54g/Version: 1.0
File dd-wrt.v24-13491_VINT_std/Kernel:
Previous Bricked from messed up upgrade/Reset:
Mode Default AP/Status: Still running 24 hours later
Issues Had to relearn Jtag procedures./Errors: Recovered very well.
Router wrt54g/Version: 3.0
File dd-wrt.v24_std_generic48425/Kernel:
Previous Linksys stock version/Reset:
Mode Default AP/Status: Still running 24 hours later
Issues No issues/Errors: No errors.
Router wrt54g/Version: 8.2
File dd-wrt.v24_micro_generic48425/Kernel:
Previous Linksys 8.02/Reset:
Mode Default AP/Status: Still running 24 hours later
Issues Abit Squirly. /Errors: No errors now.
Got 3 units running but not doing much. No PCs connected but each with Pro Trump SSIDs broadcasting from the wireless. Hah. Thats mostly my motivation to get these running. Now my TV has 5 "we are doomed" type labels that show up on all networks in my vicinity. Hah.
The learning curve took days. The info was very convoluted and conflicting. After I finally figured out what It all ment, I probably flashed all 3 in less than an hour. I went and made a cheat sheet for doing this in case I have to do this again years later.
Anyways, 8.2 was rather perplexing. I did VxWorksPrep-Gv72-v1 3 or 4 times and always got a failure message in bad english. Dang. The coder for Linksys must have been a foreigner. After each failure I waited a few minutes before pushing anything. After clicking continue, it went back to the progess bar stuck on the second bar of like 100. So it didnt get far. And no indication it did much of anything. I then went to factory reset menu and clicked ok for factory reset. After it rebooted, I tryed the Prep again. Same result. Same reset. Tried a third time. No sign any change was happening as a third failure message poped up. So now what. I just went for it. After the last factory reset, I went to upgrade page and did VxWorksKiller-Gv72-v3. Now I got some action. Upgrade success. Waited about 5 minutes and refreshed page. No connection to browser. Went and pinged it and got good ping results. So ran command and typed in the tftp command to load dd-wrt.v24_micro_generic. Success. Waited 5 minutes before trying the opra browser. Bingo. Got DDwrt page. From there I just upgraded to dd-wrt.v24_micro_generic48425 effortlessly. Been running ever since. So all 3 units updated as far as they will go. I have another V1 unit but its radio is hacked into a power booster that I used to use long ago for cantennas and big wifi antennas when networks were open and freely shareing. I doubt Ill ever be powering that one up again. Anyways, a post to show how the new code works with the old stuff.
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Sat Feb 26, 2022 6:34 Post subject:
stts wrote:
Got 3 units running but not doing much. No PCs connected but each with Pro Trump SSIDs broadcasting from the wireless. Hah. Thats mostly my motivation to get these running. Now my TV has 5 "we are doomed" type labels that show up on all networks in my vicinity. Hah.
The learning curve took days. The info was very convoluted and conflicting. After I finally figured out what It all ment, I probably flashed all 3 in less than an hour. I went and made a cheat sheet for doing this in case I have to do this again years later.
Anyways, 8.2 was rather perplexing. I did VxWorksPrep-Gv72-v1 3 or 4 times and always got a failure message in bad english...
This adventure should be documented as a Wiki?
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 02 Apr 2007 Posts: 14 Location: Richmond, CA
Posted: Sat Feb 26, 2022 8:05 Post subject: Re: New Build - 02/24/2022 - r48425
Router/Version: R8000
File: /dd-wrtv2/downloads/betas/2022/02-24-2022-r48425/netgear-r8000/netgear-r8000-webflash.bin
Kernel: Linux 4.4.302 #5321 SMP Thu Feb 24 08:24:00 +07 2022 armv7l
Previous: r44467 -> bad flash of dd-wrt.v24-48425_NEWD-2_K3.x_mega-nv64k.bin -> nmrpflash r48208-factory-to-dd-wrt.chk -> r48425 (experimental drivers, via webgui) -> r48425 via webgui (current)
Reset: no
Mode/Status: Router, AP, working fine so far up 17 min
Issues/Errors: tried the experimental drivers first but two of the radios weren't working even though status said they were on. Switched to regular drivers and seems like all three radios are now working.
Get firmware from dd-wrt.com forum. All "new builds" are rather generic and work on wrt routers except the revision 1 versions that require the old Vint radio drivers. Read "New Build" threads in "Broadcom SoC based Hardware" to see if theres any big bugs being worked on. Firmware link is in the build thread. If you find the repository of all builds, most of the wrt builds are generic located in the "Broadcom" directory. Dont mess with "linksys-wrt54g2v11" directory. Theres nothing related there.
Correv = 13 : Correv <= 4 use Vint builds, so this uses NewD builds.
Flash = 2Mb : So can only use micro builds.
Voltage = 12V 0.5A Make supper sure you dont use the wrong wall plugin even if it plugs into unit. Each Linksys is
different.
Turn on tftp windows service and use it to load micros after VXkiller has been run. The "SimpleHelp" has the instructions. Also VXprep failed to load on every attempt. So reset router and loaded VXkiller anyway. It loaded fine and blank router pinged like normal. Then windows tftp load worked like normal too.
Wow I never found this one. Ill add it to my cheat sheet.
The third link I posted had an install guide link for wrt54gv8.2. That link sent me to the list of install guides labeled: Linksys WRT54G/GL/GS/GX (Redirected from Linksys WRT54G v7.2 & 8.0 & v8.2). Looking down to wrt54gV8.2, it says Gv8.0 & v8.2 (see below for v8.1). So guess what. I clicked the one above boxed with this label. "See Linksys WRT54G v7.2". That link gave me what I used. It was boxed together with the Gv8.0 and Gv8.2. Now its clear to me that the layout is confusing and I made the wrong choice. Oh well, just abit more of the convoluted nature of all this. At least it worked out well. With this new info, maybe Ill see if theres an even better micro for my router.
Joined: 02 Apr 2007 Posts: 14 Location: Richmond, CA
Posted: Sat Feb 26, 2022 19:24 Post subject: Re: New Build - 02/24/2022 - r48425
Router/Version: WNDR3700v3
File: /dd-wrtv2/downloads/betas/2022/02-24-2022-r48425/broadcom_K3X/dd-wrt.v24-48425_NEWD-2_K3.x_mega-nv64k.bin
Kernel: Linux 4.4.302 #14740 Thu Feb 24 09:17:17 +07 2022 mips
Previous: r43718
Reset: no
Mode/Status: AP, seems ok, up all of 18 min
Issues/Errors:
@stts: I found that link directly from the wikidevi article you linked under "Links Of Interest". I don't know how you missed it.
The third link I posted is the WikiDevi I assume your talking about. A search doesnt even turn up "interest" on the page. But even still. Once I was sure I got a firmware, I was not inclined to look any more. I thought I had what I needed. Especially when I saw "Generic" in the file names. Backed up by the "Redirected" links, told me that all roads were being directed to generic firmware intended for many router versions. So it didnt occur to me to question what I had. Im not trying to label blame of some kind, Im just pointing out what I did after seeing the pages that I saw. Its a useful tool to test presentations by seeing what a newbie does with it. Newbie as in a person thats never seen that page in a long while if ever. I will check out Links of Interest when I find what your talking about.
Oh I found links of interest in the Russian page. Hah, its a russian page. Its got router details like the FCC Id code and other router specs. Thats why I saved that page. But the forum has posted to not trust links and instructions from other sites because of the timelyness of the info. Aint no way I would have chased down those links. It listed right in the DDwrt "Linksys WRT54G/GL/GS/GX" in the "Gv8.0 & v8.2" box. The link for V7.2. Boom, I had the best there is. Opps I guess I didnt. But it worked out.
Anyways, thats my chain of thinking that lead me to where I went. Strictly food for thought.
