My DIR-882 router cannot use any of the normal builds. Tried r39296, even the wired ethernet connection did not work at all. I have to rely on broly's builds. They have their own problems but at least the general functionalities are good.
I tested many versions on my DIR 882 and works well with Firmware: DD-WRT v3.0-r36527 std ( 08/09/18 )
My DIR-882 router cannot use any of the normal builds. Tried r39296, even the wired ethernet connection did not work at all. I have to rely on broly's builds. They have their own problems but at least the general functionalities are good.
I tested many versions on my DIR 882 and works well with Firmware: DD-WRT v3.0-r36527 std ( 08/09/18 )
Tried r36527, the lan was good but the wireless MAC address appeared scrambled, unreadable characters were show, and wifi was not available.
I just got a DIR-878, hardware revision A1, came with firmware 1.11.
I didn't have to downgrade to an older firmware to install DD-WRT. I flashed build factory-to-ddwrt build 39296 straight on top of stock 1.11.
I'm not seeing any problems so far. Signal strength is pretty awesome, -43 dBm one floor away, -56 dBM 2 floors away and -70 dBm at the farthest point in the house from the AP.
Is anyone using any other firmware versions successfully?
Unfortunately, neither worked for me, both said Update Failed. I'm running 1.20 and I wonder if the newest factory firmware has disallowed any other firmware to be loaded. Has anyone else had this problem? Can't seem to load anything.
If attempting to upload dd-wrt via the OEM GUI from the factory stock firmware,
Same Firmware Upgrade failed!message with the 01-30-2020-r42174 release as well.
No idea if crash recovery method will work.
Did not bother trying, others with more time may comment.
I managed to install the build r42174 without a problem from the factory GUI, but I think it camed with version 1.01 (not sure about this). I only have a small problem with it, sometimes the internet is not working for 10-30 seconds (the other computers on the local network are still accessible). Apart from this everything is perfect
If attempting to upload dd-wrt via the OEM GUI from the factory stock firmware,
Same Firmware Upgrade failed!message with the 01-30-2020-r42174 release as well.
No idea if crash recovery method will work.
Did not bother trying, others with more time may comment.
afaik you cant upgrade from recovery mode if you are on firmware 1.04+, because they added encryption and signing... you need to downgrade first ...
Thanks SoLoR.
Considering time required for entire process and factoring in time to revert when there are bugs, I'll just wait until there are numerous reports of success by dd-wrt or OpenWrt release before bothering again.
Hi, new here. I'd like to share my experience with D-Link DIR-878 A1 1900 and, may be, find a solution for my issue or at least new ideas to try.
My DIR-878 A1 came with the stock FW v1.20. The only way I found to flash it was via recovery mode (Firmware Upgrade Failed! via GUI). Flashing process was fine and smooth this way. No problem at all.
When it came to wireless operability in AP mode, no problem either with open networks. My problem comes when setting WPA/WPA2 Personal encryption (TKIP, AES). I get to see the network (only 2.4GHz) with the lock symbol from the client (tested with three different clients: 2 android (5.0.1 and 6.0.1) and a MacBook Pro). But I have never got to connect to the network (Android just don't connect and MacBook says Connection failed!). Moreover, the MacBook client asked once for username and password like if the encryption were WPA Enterprise.
I've played with modes (Mixed, B, G, BG, N...), channels, BW (full, half, quarter...), SSID broadcasting, regulatory domain, power transmission and antenna gain, timeouts, low signal threshold, firewall, and interfaces (ath0-2.4GHz, ath1-5GHz)... without success.
I flashed the stock FW back twice (1.04 and 1.20) and WPA* networks worked flawlessly, so it doesn't seem to be a HW issue.
Hi, new here. I'd like to share my experience with D-Link DIR-878 A1 1900 and, may be, find a solution for my issue or at least new ideas to try.
My DIR-878 A1 came with the stock FW v1.20. The only way I found to flash it was via recovery mode (Firmware Upgrade Failed! via GUI). Flashing process was fine and smooth this way. No problem at all.
When it came to wireless operability in AP mode, no problem either with open networks. My problem comes when setting WPA/WPA2 Personal encryption (TKIP, AES). I get to see the network (only 2.4GHz) with the lock symbol from the client (tested with three different clients: 2 android (5.0.1 and 6.0.1) and a MacBook Pro). But I have never got to connect to the network (Android just don't connect and MacBook says Connection failed!). Moreover, the MacBook client asked once for username and password like if the encryption were WPA Enterprise.
I've played with modes (Mixed, B, G, BG, N...), channels, BW (full, half, quarter...), SSID broadcasting, regulatory domain, power transmission and antenna gain, timeouts, low signal threshold, firewall, and interfaces (ath0-2.4GHz, ath1-5GHz)... without success.
I flashed the stock FW back twice (1.04 and 1.20) and WPA* networks worked flawlessly, so it doesn't seem to be a HW issue.
These are the releases I've tried so far:
r39296
r42174
r42278
r42287
r42335
r42366
Thanks for your attention.
I think I got some problem before with both AES and TKIP. I solved the problem by unchecking the TKIP box, leaving only AES box checked, on the Wireless Security page. Hope this helps.
When it came to wireless operability in AP mode, no problem either with open networks. My problem comes when setting WPA/WPA2 Personal encryption (TKIP, AES). I get to see the network (only 2.4GHz) with the lock symbol from the client (tested with three different clients: 2 android (5.0.1 and 6.0.1) and a MacBook Pro). But I have never got to connect to the network (Android just don't connect and MacBook says Connection failed!). Moreover, the MacBook client asked once for username and password like if the encryption were WPA Enterprise.
Try turning on/off KRACK protection (dont remember how its called since im currently not on offical build) i think default is off for some reason (or at least it was)...