Odds of timely D-Link DIR-882 or 878 support in 2018?

I am new to here, recently replaced my MW4530R with DIR882 and installed padavan hanwckf. I am not quite familiar with this fw at all. And I need mwan, 80211r on DIR882 which is not available on padavan hanwckf.

By any chance OpenWrt can support DIR882 soon? What are the road blocks? Where can see the progress?

@Lucky1 added support, see this thread. He also has built images based on master, since that's where devices get support first. Since 19.07 is right around the corner it's very unlikely it will see support for the DIR-878.

If you'd like to compile yourself, his pull request is here.

Edit: @ikkisunshine - to clarify: the DIR-878 and DIR-882 are basically the same hardware except for the latter having a USB 3 port. I think there was someone running a slightly modified DIR-878 build on his DIR-882 (for the USB port), a search on the forum should turn that up. If you want to use the USB port you should add it to the DTS, I believe.

@Borromini, Thank you so much. I found the thread and downloaded source codes from GitHub, after several days learning I am now compiling the OpenWrt FW now. I don't need the USB 3 at the moment, therefore I am good with DIR-878 FW. Thanks again!

@Borromini, I installed an Ubuntu and git clone from the repository, I followed the steps in readme, and run make V=s but the firmware I finally made not working. It not booting up at all. I have to roll back to Padavan from breed console. Any clue what I did wrong?

Use the binaries then (my first link).

Few more days running the DIR-882 with almost the latest mt76 drvier and it seems the MCU timeouts still appear.

Fri Jan 3 13:26:35 2020 kern.err kernel: [68574.682275] mt7615e 0000:01:00.0: Message 73 (seq 8) timeout
Fri Jan 3 13:27:13 2020 kern.err kernel: [68613.082522] mt7615e 0000:01:00.0: Message 73 (seq 9) timeout

This time the AP is not totally dead as only the 2,4G radio is rendered useless and 5GHz AC radio keeps on working as well as before, the only major gripe being slow tx speeds.

@GaryTTirn I see you've been keeping your fork with these DIR-882 changes up to date. Has there been any improvement in stability or performance since your last post above in January?

I've now been running my 3 DIR-882As for 21 to 23 days with the latest build with full wpad.
Two of these are configured as plain WiFI APs in one location and third is acting as WiFi AP and broadband router in a remote location. About dozen WiFi clients in both locations, mostly stationary and only few mobile devices.

No major issues see, all devices have ieee80211r, ieee80211v and ieee80211k configured.
I did change GTK Rekey interval to one day (86400 seconds) as it seemed to improve WiFi stability and in my case security impact is negligible. 160MHz channel on AC seems to come up but the client is unable to connect, but that's about the only remaining issue for me. With 80Mhz channel AC works just fine.

Under optimal rather optimal conditions I get 350-500Mbps downlink and 500-600Mbps uplink bandwidth when tested with iperf.

I was getting somewhat lower numbers before and to improve performance I've been running with this affinity patch.

Since now it is merged in master it will be the default.

I actually need to rebase my fork to the latest master soonish as an improved padding recipe was added and DIR-878 A1 support was finally merged.

1 Like

Thanks for the update. Great to hear it's working well.

@GaryTTirn How is WiFi performing for you?

I'm repeating the same test I did back in December, same devices and placement.

I'm getting good signal in that test arrangement (VHT-MCS 9, VHT-NSS 2, Short GI for both TX/RX) and signal is not as badly affected by even slightly obstructed line of sight between AP and client as it used to be.

kari@zenbook:~$ iperf3 -R -c
Connecting to host, port 5201
Reverse mode, remote host is sending
[  4] local port 42526 connected to port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  42.9 MBytes   360 Mbits/sec                  
[  4]   1.00-2.00   sec  44.9 MBytes   376 Mbits/sec                  
[  4]   2.00-3.00   sec  50.8 MBytes   426 Mbits/sec                  
[  4]   3.00-4.00   sec  56.2 MBytes   472 Mbits/sec                  
[  4]   4.00-5.00   sec  56.5 MBytes   474 Mbits/sec                  
[  4]   5.00-6.00   sec  55.1 MBytes   462 Mbits/sec                  
[  4]   6.00-7.00   sec  37.5 MBytes   315 Mbits/sec                  
[  4]   7.00-8.00   sec  56.0 MBytes   470 Mbits/sec                  
[  4]   8.00-9.00   sec  56.3 MBytes   472 Mbits/sec                  
[  4]   9.00-10.00  sec  55.4 MBytes   465 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   521 MBytes   437 Mbits/sec  111             sender
[  4]   0.00-10.00  sec   512 MBytes   429 Mbits/sec                  receiver

kari@zenbook:~$ iperf3 -c
Connecting to host, port 5201
[  4] local port 42688 connected to port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  61.9 MBytes   519 Mbits/sec    0    913 KBytes       
[  4]   1.00-2.00   sec  66.9 MBytes   561 Mbits/sec    0   1.25 MBytes       
[  4]   2.00-3.00   sec  66.4 MBytes   557 Mbits/sec    0    979 KBytes       
[  4]   3.00-4.00   sec  67.7 MBytes   568 Mbits/sec    0   1.19 MBytes       
[  4]   4.00-5.00   sec  65.4 MBytes   548 Mbits/sec    0   1.15 MBytes       
[  4]   5.00-6.00   sec  66.2 MBytes   556 Mbits/sec    0   1.12 MBytes       
[  4]   6.00-7.00   sec  67.0 MBytes   562 Mbits/sec    0   1.24 MBytes       
[  4]   7.00-8.00   sec  67.3 MBytes   564 Mbits/sec    0   1.47 MBytes       
[  4]   8.00-9.00   sec  65.4 MBytes   549 Mbits/sec    0   1.20 MBytes       
[  4]   9.00-10.00  sec  70.0 MBytes   587 Mbits/sec    0   1.19 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   664 MBytes   557 Mbits/sec    0             sender
[  4]   0.00-10.00  sec   661 MBytes   554 Mbits/sec                  receiver

I don't see frequent disconnects from the stationary clients according to the logs and of course having ieee80211r configured on the APs and most mobile clients being recent enough to take advantage of that so handovers between different APs and bands seem to be quick enough not to be noticeable.

1 Like

I got this up and running on a dir-2660-a1 with trivial modifications to adapt

to master:

So definitely looks like dir-1960 and dir-2660 at least can use a common dts.

Support has been added to master now. Thanks @Lucky1 and and @Sixtiz for all your hard work :sunglasses:


Great to hear this. Is it means we will be able to use DIR882 at next release?

Just the DIR-878 has been added for now. So in that case, yes.

I currently have a PR in review that extends the support for DIR-878, recently merged to master, to both DIR-867 and DIR-882. Hopefully these models should also have official support soon...


PR seems to be merged now.

Great work, thanks.

1 Like

Well that was quick. Neat!

Now that support for both devices has been added, we can finally close this topic. Please open new topics for any open questions. Thanks!


This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.