@David-TP just to confirm: is 2.4ghz for MLO a possibility or can we put our hopes to rest? Also when is the official firmware expected to release? I'm kinda afraid to try out the beta on my brand new unit 😅

  @David-TP 

Hi, according to my previous post for 1.2.0, I'm still stuck in 1.1.7 with custom fix for Qos bug. I see a new firmware again and still no one can tell me if and when your engineers are going to include the fix.

i'm sorry, but this is not the way to take care of customers. I spent hours to let engineers to remote connect to my router and solve a qos bug. And now I can't benefit of new firmware. Very disappointed in your way to consider users. Besides, activating MLO causes a mess  in my network configuration and i would be interested in trying new firmware. Last, i'm forced to use qos (i have a fiber 2,5 gbit) because your router is not capable of solving bufferbloat (poor upload speed) while communicating with my ont and i was curious to try new fimware. i wrote a mail to assistance and via discord. No response.

i kindly ask you to tell me if you're going to solve this situation. if you are not able to solve, please let me Know so i'll sell the router. It's useless to have a router i can't firmware upgrade.

Thanks 

  @David-TP is there a plan to get the BE65 V1 hardware firmware up to the same version as it seems to always get left behind. I have one v1 and one v2 (is the primary device) but never sure if having the versions mixed like I do if it causes problems with devices not connecting and a reboot of both solves it. 

How is this firmware running for everyone compared to the official 1.2.0?  Any tangible improvements?

@MikeS3000 why not install it yourself and find out?

  @WelshPaul Good call.  Installed this morning and no issues so far!  

Hi  @David-TP 
I'll check multiple times this new firmware on my be65 pro based system (AP Only).

I checked as soon as the firmware was released. At that moment, the results was good at first and bad at the end. Some of my devices were not connecting to the network and some have too bad bandwidth  (few kbit/s). I switch back to 1.2.0.

As I saw multiple good feedback and I had more time (christmas holidays) I tested a second time.
I encountered almost the same result but found out things that make everything better.

• I disabled an option named Terrestrial Link Aggregation (or something similar, my interface is in french)
• I saw that the main error of my devices is that there are connected to farthest AP instead of nearest. They do not changed to other AP even if Fast Roaming is activated. Need to reboot the device to ensure they can select another AP. I changed the preferred deco in the interface, it fixes most of the issue but for some reasons I do not know, some of my devices do not want to connect to specific AP. If I select an AP for some devices these devices do not connect at all.
• I saw a decrease in network latency with this 1.2.10 firmware
• Internal Bandwidth test is now working as expected, had 800/800 with 1.2.0 and 2400/800 with 1.2.10

Final thought, it's not perfect but a great improvement on my side. It seems to fix the issue I reported here: BE65 Pro wifi instabilities and slow down - Home Network Community

If you have a procedure or an idea how I can drill down why some of my devices do not connect to specific AP (you can find the description of my network configuration in the post mentioned above), it could be great.
 

  @David-TP 

Erratum: 
After some more hours working on 1.2.10 I found out that some devices are not having network working.
They are connected to the network but do not have any traffic going. On one of the device, forgetting the network and connecting again make it work again.
On my phone, Google Pixel 8 Pro, roaming from one AP to the one next to these devices, the same things happens, try rebooting, no change.
After changing the ethernet backhaul from 2.5gbit port to 5git port, internet came back on my phone, but do not know yet if it will persist. I didn't have issue with the wired devices connected to the same AP.

Continuing the investigations ...