On another note, there's an updated official firmware (v1.11) for the DIR-882 which fixes a compatibility issue with games consoles (XBone/PS4). Is this likely to be incorporated into DD-WRT anytime soon?
A flash of build 37305 (2018-10-10) doesn't appear to include this update and seems to have issues with an XBox one.
First thing English is not my native language, so sorry for the bad grammar.
So as you would noticed form my first sentence this will be my first post in this forum. I really like the DIR-882 but not so much the firmware form D-link.
Mostly because in the firmware they released, there is a bug where on macOS the finder will not show the NAS. Sometimes it does but that’s pure luck. I can connect to it via the ip but that’s not really a solution for the Time Machine, where macOS should see the NAS to work properly.
Since I had installed padavan firmware on my old rt-n56u, I thought there should be an alternative firmware for my DIR-882 and i found it. So the last year was a try to get this bloody thing working with dd-wrt.
First thing with the dd-wrt firmware is, that the NAS shows up in finder and that’s great. When it works I get good speed, not the full speed (per WiFi) what the hardware is possible with the original firmware but close enough.
With the GC-WB867Di (rev. 4.3) in my PC I get the advertised 867 Mbps, when i use the original firmware on the DIR-882. With dd-wrt the highest I get is 780 Mbps on the 5 GHz net close enough for me.
So when everything works i can connect with the finder to my NAS with one click and best thing is the Time Machine does it’s thing, but high load via WiFi and the router will reboot. So it’s a bit luck for me, is the Time Machine Backup working or is it forcing the router to reboot. But it’s not only the Time Machine that will force the router to reboot, when I copy my backup from my main computer to the NAS it will also reboot. Not every time but often enough that I can force the reboot only with copying a little file with around 1GB for 2 to 3 times to the NAS. That's my main issue with dd-wrt, when it’s working like it’s supposed to do, it is really great but there is the stability issue I have with high load over WiFi.
I tested all Channel Width settings for the 2,4 GHz net, but it was glued to 130 Mb/s. But the 5GHz moved to up 1560 Mb/s.
So the Status page shows me for 5 GHz 1560 Mb/s (in the Manual they say 1733 Mbit/s) and for the 2,4 GHz it shows 130 Mb/s (in the Manual 800 Mbit/s). And still high load over WiFi and the router will reboot.
A week ago I did read in the DIR-878 thread to set the transmitting power to 80mW, it should help with stability, but it didn’t do the trick for me. So I tried different settings from 80 to 75mW till 70mW but I found out for my router 75mW brings it a little bit more on the stable side.
then with the builds 03-10-2019-r39137 and r39144 I had an odd behavior where the power LED was blinking orange and I could not open the router page, while i could still watch YouTube or browse the internet. I had to manually reboot the router and than I could open the router page.
Overall without the stability issues it would really be great to use dd-wrt on the DIR-882 and not to revert back and forth between ogrinal and the dd-wrt firmware.
Maybe someone with way more knowledge about that firmware has a hint for me to improve the stability.
And under wireless is see very few option and am planning to install the latest DD-WRT.
Am pretty new to DD-WRT, so bear with me.
Which will be best release in terms of stability ?
All the features are working ? like USB Ports and WiFi no connection drops.
I use a PPPoE connection, so any known issue with this connection type ?
Also under Wireless Settings do we have option of 160Mhz Channel Bonding ? as i dont see it in the Stock Firmware ?
Hope to hear soon from the Gurus.
Thanks in advance
the wifi hw on the dir882 doesnt support 160 mhz. if you want 160 mhz use a qca9984 based router like the netgear r7800 or the netgear r9000. these routers do support these features and much more due the much better driver and chipset support
Posted: Sun Apr 21, 2019 21:13 Post subject: Re: static g++/gcc/binutils is a success
currently kernel 4.14.111 and DD-WRT v39514
Thank for this build! Trying it now on dir878, lets see how is stability... got a reboot with offical r39296 after 6 and a half days :/ also not sure how interested you are with fixing minor bugs... for example you cant set custom ntp server, however client is obviously working since it sets time from pool.ntp.org, also you cant disable ssh (option does not save) and syslogd does not start with remote loging enabled, i would suspect this is because on offical builds syslog remote loging starts syslogd with -R <ip> option, but on this build syslogd complains this is invalid option.
Posted: Sun Apr 28, 2019 17:37 Post subject: install factory-to-ddwrt.bin
i spent several hours today trying to install DD-WRT on the DIR-882 without luck.
I could install all dlink firmwares and i tried the recovery mode and with loading the start page and selecting the file and restarting again to recovery and upload then but it always says upgrade failed when using factory-to-ddwrt.bin.
Is there another factory-to-ddwrt.bin which works ?
I also tried it with curl like this:
curl -v -i --connect-timeout 99999 -m 99999 -F "firstname.lastname@example.org" http://192.168.0.1/
and waited some minutes. Still i always end with the original firmware.
You can try the crash recovery methods mentioned at the existing topic to install dd-wrt: D-Link Dir-882
NB: Those released in March or earlier should work.
Number of negative experiences reported of the April releases.
Hi, i used the recovery mode because we know that the normal upgrade does not work (also downgrading is blocked then). I would install a newer dd-wrt firmware after the factory-to-ddwrt but it fails so far to install the start image.
Also i have no red LED which flashes but an orange one. I guess my model dir-882 is newer than the one which was used for the factory-to-ddwrt.
Posted: Mon Apr 29, 2019 17:54 Post subject: iexplore
i followed the advice of kabi and used windows (!) with iexplore (!!) to install the factory-to-ddwrt.bin image and voila it worked without even to restart twice into recovery mode.
This is akward. No other browser worked and not even curl. Who did this recovery mode ?
Posted: Sun May 19, 2019 10:48 Post subject: DIR-882 Bug
I have been having sporadic drops and finally after setting up remote logging I captured a stack trace.
But I have no idea what can be causing this.
* I'm running : DD-WRT v3.0-r37305 std (10/10/1
May 19 09:26:40 192.168.2.50 kernel: Kernel bug detected[#1]:
May 19 09:26:40 192.168.2.50 kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: P 3.10.108-d6 #1741
May 19 09:26:40 192.168.2.50 kernel: task: 87c4c070 ti: 87c5a000 task.ti: 87c5a000
May 19 09:26:40 192.168.2.50 kernel: $ 0 : 00000000 00000000 00000042 00000001
May 19 09:26:40 192.168.2.50 kernel: $ 4 : 87f7fb00 00000084 00d62232 87c5bd88
May 19 09:26:40 192.168.2.50 kernel: $ 8 : 000000a8 00000000 00d62274 0000cce0
May 19 09:26:40 192.168.2.50 kernel: $12 : 80326980 00000007 0000000e 87c5bd88
May 19 09:26:40 192.168.2.50 kernel: $16 : 87f7fa80 000005c0 00000002 00000084
May 19 09:26:40 192.168.2.50 kernel: $20 : ffffffff 00000020 87d75000 87d7546c
May 19 09:26:40 192.168.2.50 kernel: $24 : 0000ff40 00000007
May 19 09:26:40 192.168.2.50 kernel: $28 : 87c5a000 87c5bcf8 803e0000 801afc60
May 19 09:26:40 192.168.2.50 kernel: Hi : 00000008
May 19 09:26:40 192.168.2.50 kernel: Lo : cccccccf
May 19 09:26:40 192.168.2.50 kernel: epc : 8015b38c dql_completed+0x10/0x19c
May 19 09:26:40 192.168.2.50 kernel: Tainted: P
May 19 09:26:40 192.168.2.50 kernel: ra : 801afc60 fe_poll+0x158/0x714
May 19 09:26:40 192.168.2.50 kernel: Status: 1100fc03#011KERNEL EXL IE
May 19 09:26:40 192.168.2.50 kernel: Cause : 10800034
May 19 09:26:40 192.168.2.50 kernel: PrId : 0001992f (MIPS 1004Kc)
May 19 09:26:40 192.168.2.50 kernel: Modules linked in: shortcut_fe nf_nat_h323 nf_conntrack_h323 mt_wifi(P) mt7621_wdt
May 19 09:26:40 192.168.2.50 kernel: Process swapper/1 (pid: 0, threadinfo=87c5a000, task=87c4c070, tls=00000000)
May 19 09:26:40 192.168.2.50 kernel: Stack : 0000000b 80016f18 00000000 00000000 8036f0ec 00000000 00000001 80370000
May 19 09:26:40 192.168.2.50 kernel: #011 86fa0000 803d0000 00000002 8001d5f8 00000001 00000020 00000000 00000000
May 19 09:26:40 192.168.2.50 kernel: #011 00000040 81118900 811189c0 0000000f 00030000 87d2ac80 0003000f 8032ac34
May 19 09:26:40 192.168.2.50 kernel: #011 87d75440 8034cfc0 00000001 81110980 87d7546c 00000020 0000012c 0000ff42
May 19 09:26:40 192.168.2.50 kernel: #011 80350000 81110988 80360000 801e1774 00000000 00000020 8034cfc0 8030c710
May 19 09:26:40 192.168.2.50 kernel: #011 ...
May 19 09:26:40 192.168.2.50 kernel: Call Trace:
May 19 09:26:40 192.168.2.50 kernel: [<8015b38c>] dql_completed+0x10/0x19c
May 19 09:26:40 192.168.2.50 kernel: [<801afc60>] fe_poll+0x158/0x714
May 19 09:26:40 192.168.2.50 kernel: [<801e1774>] net_rx_action+0xc8/0x1d4
May 19 09:26:40 192.168.2.50 kernel: [<8002c838>] __do_softirq+0x138/0x22c
May 19 09:26:40 192.168.2.50 kernel: [<8002ca28>] do_softirq.part.14+0x8c/0xa0
May 19 09:26:40 192.168.2.50 kernel: [<8002ccec>] irq_exit+0xa8/0xdc
May 19 09:26:40 192.168.2.50 kernel: [<8000a490>] ret_from_irq+0x0/0x4
May 19 09:26:40 192.168.2.50 kernel: [<80016e0c>] __pastwait+0x0/0x8
May 19 09:26:40 192.168.2.50 kernel: [<8005e0d8>] cpu_startup_entry+0xf8/0x150
May 19 09:26:40 192.168.2.50 kernel: Code: 8c860044 01461023 0045182b <00038036> 8c890040 8c8c004c 00c54021 00493823 010c5823
May 19 09:26:40 192.168.2.50 kernel: ---[ end trace c4f5856326a2dc6c ]---