I just installed BS 24461 ... its working fine so far ..
i notice a problem with time zone .. it was already fixxed by kong ..
I fixed it, then BrainSlayer moved from uclibc to musl, which does not honor /etc/TZ and thus had to also make it compatible with musl. And you will find more broken things in latest release, there are major changes going on right now.
I have a WZR-1750DHP with factory firmware installed. I was going to upgrade to 24461 using factory-to-dd-wrt.bin Should I wait until the major changes that you mentioned are implemented?
for me it seems QoS is messing up my wireless signal while on the last 24500 fw.
Signal drops and bad range when QoS is on, everything working perfect when QoS is disabled......
My unit's uptime has been around 35 hours since the upgrade from 24045M to 24500M. Everything is so far so good.
[OK] No router hang with burst DNS proxy service queries from eMule
[OK] No PPPoE connection dropping with some unrelated generic setting changes
[OK] 5GHz 802.11ac VHT(80+80MHz)CH149+155
[OK] 2.4GHz 802.11n WideHT(20+20MHz) CH11+7
[OK] SSH Tunnel
[OK] OpenVPN tap,TCP:443,SHA1,BlowFish,DH2048,TLS_Auth
[OK] 16GB USB2_stick ext2 at /jffs
[OK] QoS HFSC,FQ_CODEL on dns,http,https,ssh,icmp
[OK] Smartphone's stable smb 50Mbps BD streaming via 1T1R 802.11ac at 4 meter away
[OK] uTorrent new session speed 32 per second, up to 8192 connections.
The 802.11ac performance is better and more stable with the new Broadcom WiFi driver/firmware. There is no performance drop observed when the QoS function is always enabled.
But I still need to observe it for 1 week. Previously 24200M/24340M versions showed some random weird issues around 1 week's uptime. There is also too frequent PPPoE connection lost issue with some general configuration update.
About 1 week's running, I can say that KongAC 24500M is indeed a good-performance and somewhat still stable version for WZR-1750DHP's long term usage. Of course further running at least 1 more month w/o any glitch is needed to prove if it is really stable.
To me the only inconvenient issue is the UTC(GMT) time instead of the local time-zoned one viewed with the Web UI.