Optimized build for the D-Link DIR-860L

Here we go:

 OpenWrt SNAPSHOT, r13533-69f6fc7b15
 -----------------------------------------------------
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00004000 00010000 "u-boot-env"
mtd2: 00004000 00010000 "radio"
mtd3: 00008000 00010000 "factory"
mtd4: 00010000 00010000 "defaults"
mtd5: 00fb0000 00010000 "firmware"
mtd6: 0024ffc0 00010000 "kernel"
mtd7: 00d60000 00010000 "rootfs"
mtd8: 00510000 00010000 "rootfs_data"

I can confirm that Wifi (2.4 + 5GHz) is working fine. I flashed the build (openwrt-ramips-mt7621-dlink_dir-860l-b1-squashfs-factory.bin) via recovery.

1 Like

Thanks for the information.
If you compare both outputs, mtd6 and mtd7 have different sizes, both larger in the newer build.

Do you settings stick after a reboot? In case they don't create a conf files backup so if sh*t hits the fan, you can always upload those :slight_smile:

My changed settings were still valid after a reboot but sadly I can't use this build in my enviroment.
First of all I can't get along with DSA (imho not very userfriendly if you need vlans) and second there is no more ebtables included in your latest build. I've just installed 19.07.3 to see if this build will fit my needs. Kernel Version seems to be a bit newer than r12255 but the first problem that I've encountered with this official OpenWRT build is that DFS channels are not working, only channel 36 seems to be working, otherwise I do get "Wireless is not associated" the following syslog entry:

daemon.notice netifd: radio0 (7271): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 6949 path ()
daemon.notice netifd: radio0 (7271): Device setup failed: HOSTAPD_START_FAILED

If I can't fix this error I will return to your r12255 build as I never had any issues with it.

The change to a DSA is a big one. Unfortunately I don't use vlan so can't offer you advise there.
Forgot to include ebtables. It will be present in the next (test-)build.

Have you set your country in WiFi settings?

1 Like

Thanks, I've tried with driver default and with my country. I'll stick to your r12255 build as Wifi doen't seem to be stable on 19.07.3 (several clients got disconnected a couple of times). The change to DSA really bothers me as swconfig always worked fine and afaik DSA can't even be proper configured via Luci.

Strange since the WiFi never has been more stable for me with the devices I connect to it. So YMMV I guess.
DSA is the chosen path so when 19.07 doesn't get anymore updates that's it for swconfig. Reading this topic it looks like you are able to use vlans but you have to jump through a few hoops which are on fire :sweat_smile:

Keep in mind that I was talking about the Wifi with 19.07.3. I haven't tested the wifi much with your latest build as this build is pretty much not useable for my envirioment. I do need ebtables and working vlans for my IOT and guest network. I'll test DFS and Wifi throughput with your latest build later on and report back but to be honest I never had problems with the wifi on r12255, it was always stable and the throughput was also fine.
The "ethernet driver improvements" sound quite interesting but I don't even know if that would do anything for my DIR860L as I'm using it only as a smart switch + AP behind my main Router (WRT3200ACM).
Anyway if i figure out how DSA works (thanks for the link) I'll give the next (test)build a try in my productive enviroment. The good thing is that I have a second backup device so I can quickly change back to r12255 if something goes wrong.

2 Likes

I finally found the time for some tests...

cat /proc/mtd results are the same already posted by @Kherby

OpenWrt SNAPSHOT, r12255-0709943182
 -----------------------------------------------------
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00004000 00010000 "u-boot-env"
mtd2: 00004000 00010000 "radio"
mtd3: 00008000 00010000 "factory"
mtd4: 00010000 00010000 "defaults"
mtd5: 00fb0000 00010000 "firmware"
mtd6: 001dffc0 00010000 "kernel"
mtd7: 00dd0000 00010000 "rootfs"
mtd8: 00510000 00010000 "rootfs_data"



OpenWrt SNAPSHOT, r13533-69f6fc7b15
 -----------------------------------------------------
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00004000 00010000 "u-boot-env"
mtd2: 00004000 00010000 "radio"
mtd3: 00008000 00010000 "factory"
mtd4: 00010000 00010000 "defaults"
mtd5: 00fb0000 00010000 "firmware"
mtd6: 0024ffc0 00010000 "kernel"
mtd7: 00d60000 00010000 "rootfs"
mtd8: 00510000 00010000 "rootfs_data"

But in my case there is no way to keep settings after reboot on r13533.
I tried to flash factory build from D-Link recovery, to normally flash the update without to save settings, reset after install, double flashing but the settings are not saved in any way.
Also after set manually the new settings and saving them as backup, after a reboot I can't restore it.
@Bartvz , if you have any idea or tests to perform please let me know

I've just flashed r13533 again on my backup device to do some speedtests and I can confirm now that any saved settings will be gone after a reboot. So it seems to a generell problem with r13533.
I guess we have to wait for the next build...

1 Like

Great work on the optimized builds and many thanks!

Your r12255 has been rock solid for me (using the router only as an AP, currently with 20+ days uptime) in terms of Wi-Fi speed and stability, whilst the last official openwrt build was quite buggy - frequent wi-fi issues, especially on the 5ghz band, requiring frequent reboots.

2 Likes

Same here, I'm using my DIR-860L as a smart switch + AP and 12255 is working quite good. Very stable and I'm also happy with the wifi performance (2.4 + 5GHz).

1 Like

I might have jumped the gun a bit....everything was rock solid until 5GHz started dying... with the following errors:

Mon Aug 10 19:32:48 2020 kern.err kernel: [589780.317390] mt76x2e 0000:01:00.0: MCU message 2 (seq 7) timed out
Mon Aug 10 19:32:48 2020 kern.info kernel: [589780.398664] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Aug 10 19:32:48 2020 kern.info kernel: [589780.409821] mt76x2e 0000:01:00.0: Build: 1
Mon Aug 10 19:32:48 2020 kern.info kernel: [589780.418195] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Aug 10 19:32:48 2020 kern.info kernel: [589780.447370] mt76x2e 0000:01:00.0: Firmware running!
Mon Aug 10 19:32:48 2020 kern.info kernel: [589780.467376] ieee80211 phy0: Hardware restart was requested

Any ideas?

Has anyone tried a "tickless" kernel and if so what were the performance results for forwarding/transfers/sqm?

My DIR-860L just failed upgrading to the latest snapshot from Jun 10 snapshot, which I am pretty sure is using DSA driver. Any idea how to do that without re-configure the whole device?

root@OpenWrt:/tmp# sysupgrade -v /tmp/openwrt-ramips-mt7621-dlink_dir-860l-b1-sq
uashfs-sysupgrade.bin
Device dlink,dir-860l-b1 not supported by this image
Supported devices: dlink,dir-860l-b1 dir-860l-b1 - Image version mismatch: image 1.1, device 1.0. Please wipe config during upgrade (force required) or reinstall. Reason: Config cannot be migrated from swconfig to DSA (early adopters with DSA already set up may just force-flash keeping existing config)
Image check failed.

You cannot upgrade while keeping your configuration, since the DSA driver is not compatible with swconfig that was used earlier. Make a backup of your /etc/config folder so you can restore compatible settings after upgrading, but do NOT restore the network file, as that will softbrick your device.

1 Like

Pretty sure the snapshot I am using is already DSA driver enabled:

 OpenWrt SNAPSHOT, r13542-78e8360878
 -----------------------------------------------------
root@OpenWrt:~# uname -a
Linux OpenWrt 5.4.45 #0 SMP Wed Jun 10 23:49:24 2020 mips GNU/Linux

I am confused with the aformentioned warnings.

If you are sure, then it's probably a false positive. Just upgrade (without keeping settings so it actually works), and then restore all your configuration files. Do keep in mind that if it turns out your configuration is indeed not compatible, you might softbrick your device. Thankfully, the recovery on the DIR-860L is really solid. I have already recovered from softbricks on multiple occasions.

Fortunately I am be able to use just 'sysupgrade -F' to successfully upgrade and all settings kept.

Latest snapshot keeps the settings after reboot?

Can anyone comment in terms of 5GHz stability with the latest snapshot?
I'm still getting random errors on the 5GHz band with 12255, 2.4 appears to be rock solid....