GrenSo wrote

 

Kevin_Z wrote

  

GrenSo wrote

There's only one thing that still bothers me, but I know that it's unlikely to change anytime soon, and that's the certificate error when accessing the router's web interface via https.

 

Do you refer to the concerns reported on other models that when you try to access the router web GUI via its IP address (192.168.0.1), it will redirect you to tplinkwifi.net? I cannot say for sure whether or when this will be optimized in all router firmware, but this was forwarded to the development team a long time ago, and I thought it had been optimized.

 

No, that's not exactly what I mean. Rather, when I access the web GUI locally (I always use the router's IP address), I get a certificate error. In Chromium, it's "NET::err_cert_authority_invalid," and in Firefox, it's "SEC_ERROR_UNKNOWN_ISSUER."

 

Yes, I know, you can make the appropriate changes in your browser, but I don't think that's in the best interest of the average user without prior knowledge of the topic.

 

@GrenSo I see. 

The reason why some browsers recognize tplinkwifi.net or 192.168.0.1 as “insecure” is that tplinkwifi.net’s Certificate is a self-signed Certificate. Most browsers do not accept this kind of Certificate because it is not an authoritative CA. This has been explained in more detail in this FAQ.

staza wrote

  @Kevin_Z 

 

Hello Kevin_Z

Thanks for your reply (on the previous thread).

Yes i am using fw 1.1.2 and the situation with BE200 for me is the same.

Windows 11 24H2 show that it is connected to both bands 5 and 6GHz and when i check the routers web UI i see that all the traffic is done through 6GHz and 5GHz is just connected with a 6mbps link on transmit (which i actually think is receive). This seems to be compliant with MLO-eMLSR.

Also checking on this intel link

https://cdrdv2-public.intel.com/761674/761674_Intel_Wi-Fi_7_BE200_GalePeak2_Product_Brief_Rev1p1.pdf

it states that be200 is compliant with just MLO-eMLSR witch make sense since it seems to have just one radio.

Yet on some intel community posts i saw that BE200 supports MLMR as you have mentioned in a previous post but this is not the case for me.

 

Also for troubleshooting purposes only, do note that the problem with the double WAN connection to the ISP during router reboot (or start-up) when connected via VDSL ppoe pashthrough still persist leading to the router not updating no-ip DDNS with the correct ip for the first hour until the next scheduled update (it updates it with the first WAN ip it gets but not with the second which is the final routers wan ip TKID250206919).

 

Thanks again

Stavros
 

@staza 

The Intel BE200 is compliant with eMLMR. This has been confirmed in discussions within the Microsoft community, where users have assured that the BE200 supports eMLMR functionality. You can find more details in the relevant community threads.

Additionally, I recommend updating the driver version for the BE200 to ensure optimal performance and compatibility. The latest driver version available is 23.120.0, which was released on March 4, 2025. Keeping your drivers up to date can help resolve any potential issues and improve connectivity.

cryalcin wrote

I was able to update after resetting the device. i guess tplink doesn't want us to touch dhcp, router ip, dns and other similar settings.

@cryalcin Happy to hear you got it updated successfully.

Just let us know if there is any issue with the new firmware.

Legalmap wrote

New firmware and same problems.

@Legalmap Sorry to hear that.

If that is the case, I will escalate your case to our support engineers for further investigation. Please check your registered email box and follow up.

ChrisBS wrote

  @Kevin_Z 

Hey, after few weeks testing, i found out one big problem with LED status.

When you turn off led status on sattlite easymesh device connected via WiFI to main router. After time device become unstable connecting and disconnecting all the time.  And showing offline on main router webpage.

 

 

@ChrisBS What's the current network topo? Is one BE550 running as the main router and another BE550 connects to the main one wirelessly via EasyMesh?

Could you please provide a detailed procedure for how you reproduced the issue? Once disabling the LED status of the satellite BE550, will it show as offline on the main's Mesh Device Details page, and a recurring notification of "Device disconnected" pop up?

Does the issue disappear immediately if you re-enable the LED status?