Not a single one.
Edit: The router's routing part works fine, while the 5G Hz WiFi suddenly went down just now, have to restart the WiFi from ssh.
Is the 5G Hz WiFi a known problem for D-Link DIR-860L b1?
Not a single one.
Edit: The router's routing part works fine, while the 5G Hz WiFi suddenly went down just now, have to restart the WiFi from ssh.
Is the 5G Hz WiFi a known problem for D-Link DIR-860L b1?
No WiFi issues on mine during the entire uptime:
root@OpenWrt:~# uptime
09:34:10 up 40 days, 15:58, load average: 0.08, 0.12, 0.04
Running an unpatched/stock 19.07.1 image.
Is impressive. It is clear that those of us who have problems are because of the SoC. I have doubts that a patch can definitely fix it more than soften the problem.
5.4 update coming soon.
That was quick. Already in master branch now
I am testing the 5.4 branch on a 860L B1 in the last 3 weeks, and even though I never had more uptime than 6 days (due to updating the device), I never seen any errors, or had any reboots or wifi issues on the 5.4 branch. Now that it is in master, I just switched back to master and now is time for a longer test. If someone does not want to compile it, just wait a couple hours for the next snapshot builds, those should include the 5.4 patchset.
For those who are afraid of loosing HW NAT: on my 1000/300 PPPoE fiber connection, I can reach 800/325 with "just" SW offload and RPS.
Is that more than you were able to reach on the older kernel with just SW offloading?
It is a bit more, but I can see that the CPU is not loaded to its full capacity, so it may be that the FTTH network is a bit congested and that is the reason I cannot reach the 940-950Mbit in DL which is the absolute maximum WAN speed I have ever seen. Non the less: if I need to choose between a stable 800Mbits, and the previous rebooting, and timeouts, I am happy to choose the 800Mbits
I also Iperf-ed the LAN-LAN side, and in both directions it is stable 945Mbits.
I will try it in 9 days. I want to test first if the restarts with 19.07.1 were due to the power supply, to rule out future problems.
Restarted 1h 45min ago. Discarded power supply. I'll try master branch now. Can the network settings for kernel 4.14 be preserved or does it completely change the names of the switch and ethernet ports?
Start fresh, since it's using DSA ethernet driver now
Will sysupgrade -n -F be enough to do the trick?
But for te new driver only affects the /etc/config/network configuration doesn't it? I think i can keep the one from dnsmasq, firewall and other packages.
How to compile master branch kernel 5.4 with DSA driver? In target/linux/ramips there is only the kernel 4.14 directory and the 5.4 patch directory. I don't see 5.4 kernel files or DSA driver. And KERNEL_PATCHVER: = 4.14 appears in the Makefile file.
Just make clean, git pull and compile it for the latest master. It will compile with kernel 5.4 for ramips.
Thanks. Compiling it.
Running the latest master powered with Linux 5.4 kernel now. According to the output:
CPU0 CPU1 CPU2 CPU3
8: 225655 225453 225761 225733 MIPS GIC Local 1 timer
9: 6781 0 0 0 MIPS GIC 63 IPI call
10: 0 2403 0 0 MIPS GIC 64 IPI call
11: 0 0 7466 0 MIPS GIC 65 IPI call
12: 0 0 0 2508 MIPS GIC 66 IPI call
13: 6960 0 0 0 MIPS GIC 67 IPI resched
14: 0 55429 0 0 MIPS GIC 68 IPI resched
15: 0 0 18217 0 MIPS GIC 69 IPI resched
16: 0 0 0 52894 MIPS GIC 70 IPI resched
17: 0 0 0 0 MIPS GIC 19 1e000600.gpio-bank0, 1e000600.gpio-bank1, 1e000600.gpio-bank2
19: 12 0 0 0 MIPS GIC 33 ttyS0
20: 0 0 0 0 MIPS GIC 29 xhci-hcd:usb1
21: 469880 0 0 0 MIPS GIC 10 1e100000.ethernet
23: 0 0 0 0 1e000600.gpio 7 keys
24: 0 0 0 0 1e000600.gpio 18 keys
25: 2 0 74989 0 MIPS GIC 11 mt76x2e
26: 97702 0 0 0 MIPS GIC 31 mt76x2e
ERR: 1
it seems the WiFi interrupt 31 (mt76x2e) is using cpu0, which used cpu 1 with 4.14 IIRC.
Edit: Much less ERRs, which is a good sign. I thought it can be 0 ERR until the first one emerged.
CPU1 is a virtual core, only CPU0 and CPU2 are real. I believe it is correct to tie the two wifi cards to the two actually existing cores.
On my side there are 250 ERRs, but no actual issues. Even on my x86 NAS (HP microserver) there are a few errors in /proc/interrupts, so this may even be completely normal.
There's a real issue here, the ed2k server I was connected will always lost connection every 15 minutes, which is normal before with 4.14 kernel.
This is with soft offloading on, now I am testing how's it going with soft offloading off.
Edit: I remember I have had similar issue with 4.14 and hard offloading, but that issue has been resolved after some time.
Edit2: Without soft offloading, the 860L only can handle 200Mbps download or upload. I started to miss the full-functioned 4.14.
Mostly correct. Assuming the other configs don't care about raw interfaces.