Slow Download Speeds R710 Unleashed

[max_p_eogltxsc8]

Strange issue with R710 on latest unleashed firmware. Upload speeds consistently incredible on both laptop and phone but downloads even from 5 ft away never go over 200 but stay consistent through 3 thick walls. Speedflex on android shows 550 up 550 down to AP. Iperf reflects speedtest.net results. Cable shouldn't be the problem as I have plugged my laptop on it and gotten the gigabit fiber speeds I should be getting. I have factory reset it countless times set everything to auto and tried manually setting the bands and channel width, am I missing something? Any help would be appreciated.

[rob_m_istij3wx4]

I seem to be having some issues with the firmware. I'm getting an error after upgrading my R610 that the firmware for the R510 does not match when trying to upgrade it separately. It failed when I tried to upgrade both at the same time, so I upgraded the R610 first and then tried to upgrade the R510 that is meshed. Also, the firmware upload is extremely slow.

Edited: I got it working now, just need to reset the ap and reupload the firmware.

[stefan_mehre]

So this firmware seems to have solved the issue for me on iPad OS. Download and
Upload are pretty close.
But on my Samsung S10 download is still much less than upload. But if I am right, the
fix for all devices will be released with 200.9.xxx. Or am I wrong?

[veno77]

you are wrong. This firmware should fix all download issues... 200.9 will be new firmware probably with new features and supporting newer future released devices. I am waiting to see how will be the 200.7 fix firmware when released, hopefully next week.

[stefan_mehre]

Really, but Michael wrote:
“ I have received confirmation from DE manager that we will have the ER-7956 iOS device performance fix in Unleashed 200.8 update by tomorrow (Friday US). “

So sounds for me only iOS and iPadOS fix and that‘s what I am seeing with iPerf3
from iPad and Samsung S10 to iPerf Server on my Router.

[veno77]

if they fixed this only for ios and not for other devices and platforms... this is really pity... having in mind it took them more than 1 year to identify and fix the issue "partially"???