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.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sun Aug 04, 2019 15:59 Post subject:
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r40527 std (08/04/19)
Kernel Version Linux 4.4.187-rc1 #623 SMP PREEMPT Sun Aug 4 07:49:29 +04 2019 armv7l
Status: Working (PPPoE, AP 2&5 Ghz, QoS, Wireguard)
Reset: No
Errors: None
Asus RT-N12D1
DD-WRT v3.0-r40527 mega (08/04/19)
Linux 3.10.108-d8 #25713 Sun Aug 4 14:34:00 +04 2019 mips
dd-wrt.v24-40527_NEWD-2_K3.x_mega.bin
GUI install on the WAP ...NO reset and it all seems ok so far.
On the spare Asus RT-N12D1
same ol problem with VAP ...have to use as startup in .../Diagnostics.asp:
sleep 20; stopservice nas; wlconf eth1 down; wlconf eth1 up; startservice nas
just to tinker a bit with this 10/100 switch 300MHz oldasfoever unit and see what she will do ---
reset to defaults --- SFE is Now disabled by defaultiffin you do a reset
download speed across its WAN
NOTE:
When enable SFE and 'Apply Settings' you may loose all WAN connection ....just wait 2 ~ 4 minutes and it will be back.
Same thing happened on the EA8500 and its dual 1400MHz but only had wait 'bout 1 minute for its WAN to come back alive
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r40527 std (08/04/19)
Kernel: Linux 4.4.187-rc1 #623 SMP PREEMPT Sun Aug 4 07:49:29 +04 2019 armv7l
Previous: r40501
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far (since 6729 claims, "SFE in Build 40441 and beyond, Fixed, UDP and PBR working with SFE from 40526", I will enable SFE and test with Xbox Live gaming).
Edit... tested some Xbox gaming and this build seems to have done the trick for joining parties (has been problematic for a while), no problems with network/NAT tests, and no random network errors in game. Thanks to those squashed the applicable bugs!
Uptime: 45min
Temperatures: CPU 69.1 °C / WL0 48.5 °C / WL1 54.5 °C
Last edited by flyzipper on Mon Aug 05, 2019 5:05; edited 2 times in total
Router/Version: Linksys EA6300
Firmware: DD-WRT v3.0-r40527 std (08/04/19)
Kernel: Linux 4.4.187-rc1 #623 SMP PREEMPT Sun Aug 4 07:49:29 +04 2019 armv7l
Previous: 08-02-2019-r40501
Mode/Status: Gateway/VAP/WireGuard
Reset:
Issues/Errors: workaround is needed for VAP
ERROR when I try to write linux2 MTD device
root@ddwrt:/tmp# mtd -f write linksys-ea6400-webflash.bin linux2
Unlocking linux2 ...
Could not unlock MTD device: linux2
linux2: Not supported
Writing from linksys-ea6400-webflash.bin to linux2 ... [e]Failed to get erase block status
I don't know, the operate to write to linux2 is successful ?
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Mon Aug 05, 2019 0:26 Post subject:
flyzipper wrote:
Issues/Errors: Working so far (SFE remains disabled because its UDP forwarding issues continue to periodically mess with my Xbox Live gaming experience).
Issues/Errors: Working so far (SFE remains disabled because its UDP forwarding issues continue to periodically mess with my Xbox Live gaming experience).
Did you actually test it? .......
Fair, I was lazy with that copy and paste, updated...
(since 6729 claims, "SFE in Build 40441 and beyond, Fixed, UDP and PBR working with SFE from 40526", I will enable SFE and test with Xbox Live gaming)
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Mon Aug 05, 2019 7:02 Post subject:
DStar wrote:
Can anyone say if this offers 802.11w/MFP on R7000?
I saw BS make some commits into 40366,40367, but I don't know if R7000 will offer it.
AFAIK, /services/networking/madwifi.c is for Qualcomm devices as denoted by references to ath* interfaces and such, not Broadcom, so my best educated guess is no.
