Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer 2. krack fixes for Broadcom were completed in r33678, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issue #4 below).
4.R6400v2 support added in r36811-36818, 36825, and 36826. R6700v3 support added in r36828-36840.
Tickets closed as 'fixed' (Broadcom-related and general): -
Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build. _________________ #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 Thu Jan 17, 2019 14:19; edited 3 times in total
Router/Version: Netgear WNDR4500v2
File: .bin upgraded via telnet
Kernel: Linux version 3.10.108-d8 (root@linux) (gcc version 8.2.0 (OpenWrt GCC 8.2.0 r7577-d14647dd59) ) #22599 Tue Jan 15 01:39:53 CET 2019
Mode: 2.4 GHz CB / 5 GHz AP+VAP
Status: Didn't test much, but seems fine.
Edit: I didn't double-check the version after reboot, but the `write` process succeeded. Will check tonight if it's really 38302.
Update: Yup the 4500 indeed is running 38302. I didn't notice both initial failures were the same device. Better safe than sorry for new users jumping the gun... _________________ #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 Wed Jan 16, 2019 2:07; edited 3 times in total
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r38253 std (01/10/19 Kernel: Linux 4.4.169 #4451 SMP Thu Jan 10 09:06:00 CET 2019 armv7l Present: BSr38253
I tried three times to upgrade to this version and i keep getting the Upgrade failed message. I did a power cycle of the router and got the same message.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Tue Jan 15, 2019 20:36 Post subject:
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r38302 std (01/14/19)
Kernel Version Linux 4.4.170 #4470 SMP Mon Jan 14 18:44:43 CET 2019 armv7l
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r38302 std (01/14/19)
Kernel: Linux 4.4.170 #4470 SMP Mon Jan 14 18:44:43 CET 2019 armv7l
Previous: r38253
Mode/Status: Gateway / working
Reset: no
Issues/Errors: No issues so far.
Uptime: 23m
Temperatures: CPU 62.5 °C / WL0 47.8 °C / WL1 51.6 °C
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r38253 std (01/10/19 Kernel: Linux 4.4.169 #4451 SMP Thu Jan 10 09:06:00 CET 2019 armv7l Present: BSr38253
I tried three times to upgrade to this version and i keep getting the Upgrade failed message. I did a power cycle of the router and got the same message.
Can you change to any version or are you stuck on the 38253 version? (trying to determine if it is the 38302 build, but more than likely it the build old build has the problem.)
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Wed Jan 16, 2019 0:05 Post subject:
mwchang wrote:
jwh7 wrote:
New Build 38302 BS: 01-14-2019-r38302 [FAILS to upgrade]
Calm down.... calm down... do NOT rush!
Why was the firmware upgrade process affected? Maybe an interesting reason....
Wildlion wrote:
Brimmy wrote:
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r38253 std (01/10/19 Kernel: Linux 4.4.169 #4451 SMP Thu Jan 10 09:06:00 CET 2019 armv7l Present: BSr38253
I tried three times to upgrade to this version and i keep getting the Upgrade failed message. I did a power cycle of the router and got the same message.
Can you change to any version or are you stuck on the 38253 version? (trying to determine if it is the 38302 build, but more than likely it the build old build has the problem.)
Could be bad CRC check results, could be something in the r38253 build, but the topic should read, "Buffalo WZR-1750DHP/DHPD fails to upgrade" until others report the same issue.
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r38253 std (01/10/19 Kernel: Linux 4.4.169 #4451 SMP Thu Jan 10 09:06:00 CET 2019 armv7l Present: BSr38253
I tried three times to upgrade to this version and i keep getting the Upgrade failed message. I did a power cycle of the router and got the same message.
Can you change to any version or are you stuck on the 38253 version? (trying to determine if it is the 38302 build, but more than likely it the build old build has the problem.)
The current build i am on now is the one just before this one.
I can flash to any older version from 2018, as i have recently checked this. Since my post i have even reset my router via the reset button on the back and tried to flash, and it still fails.
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Wed Jan 16, 2019 0:16 Post subject: Cisco Linksys E4200 v1
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-38302_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r38302M mega (01/15/19)
Kernel: Linux 3.10.108-d8 #22615 Tue Jan 15 02:02:08 CET 2019 mips
Previous: DD-WRT v3.0-r38253M mega (01/10/19)
Reset: No
Mode: Gateway/AP
Uptime: ~9 hrs
Status: OK
Issues/Errors:
Code:
write block [7667712] at [0x00750000]
done [7733248]
[UPGRADE] ret: 0
send dhcp lease release signal
Sending SIGTERM to all processesBCMDOG: WDT device closed unexpectedly. WDT will not stop!
SQUASHFS error: xz_dec_run error, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x46dc6a
SQUASHFS error: Unable to read fragment cache entry [46dc6a]
SQUASHFS error: Unable to read page, block 46dc6a, size d25c
SQUASHFS error: Unable to read fragment cache entry [46dc6a]
SQUASHFS error: Unable to read page, block 46dc6a, size d25c
SQUASHFS error: squashfs_read_data failed to read block 0x56e664
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: Unable to read metadata cache entry [56e664]
SQUASHFS error: read_indexes: reading block [56e664:1648]
SQUASHFS error: xz_dec_run error, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x195712
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
SQUASHFS error: Unable to read fragment cache entry [195712]
SQUASHFS error: Unable to read page, block 195712, size 9654
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000a
Rebooting in 3 seconds..Please stand by while rebooting the system...
Again, it would be advisable for folks to have serial console up when they are flashing, especially any build after 37442. It just seems as if things are eating themself...
Geez people, chill out... I hadn't noticed that both early failures were the same device. It was preemptive when I noticed it this afternoon, to potential curtail a bunch of newbies from bricking their routers. Then I came home to do some modding and network reconfiguration. :-/
Posted: Wed Jan 16, 2019 5:19 Post subject: Upgrade Failed
I just gave it a try through SSH and I get a bad CRC error.
root@BUFFALO:~# write buffalo-wzr-1750dhp-webflash.bin linux
Flash is NAND
freeram=[456577024] bufferram=[5206016]
The free memory is enough, writing image once.
buffalo-wzr-1750dhp-webflash.bin: Bad CRC (0xC2BBDD87 expected, but 0x6E4DEED8 calculated)
