@Kevin_Z I have now installed the Pre-Release Firmware on my two BE800 Routers. I hope it probably solves the sudden reboots I have experienced in the short time I have the two BE800 active with the older firmware. The main router suddenly has rebooted and I have lost internet connection for 2 to 3 minutes.

 

One of the BE800 is as main router and the other as satellite easy mesh configured.

 

One issue or inconvenient I see on the one configured as a satellite with the pre-release firmware is, that it renew its IP every Minute.

 

Here a some entries from the log.

 

2024-12-29 12:33:55 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:33:55 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:33:55 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:33:21 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:33:21 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:33:21 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:32:47 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:32:47 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:32:47 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:32:13 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:32:13 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:32:13 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:31:38 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:31:38 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:31:38 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:31:04 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:31:04 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:31:04 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:30:30 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:30:30 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:30:30 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:29:56 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:29:56 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:29:56 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:29:22 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:29:22 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:29:22 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:28:47 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:28:47 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:28:47 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:28:13 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:28:13 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:28:13 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:27:39 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:27:39 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:27:39 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:27:05 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:27:05 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:27:05 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:26:31 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

2024-12-29 12:26:31 DHCPC INFO [27044] send select request with options(cliid=01/b0:19:21:39:4f:72:;)

2024-12-29 12:26:31 DHCPC INFO [27044] 1/2 lease passed, enter renewing state

2024-12-29 12:25:57 DHCPC INFO [27044] receive ack from server with ip 192.168.5.251, options(serverid=192.168.5.1;lease=4294967295;subnet=255.255.255.0;dns=192.168.5.1 192.168.5.1;router=192.168.5.1;)

 

Greetings Markus

  @Kevin_Z  Hi Kevin. As it is not a long time since I have installed the pre release firmware, I can't be 100 percent sure.

But so far it looks promising that the sudden reboots not happen anymore.

 

About the many dhcp request of the be800 in satellite mode. Do you mean that it will be solved in a next firmware?

 

Another thing I have noticed on the satellite be800. The LED screen there shows now only a exclamation mark "!" and not even anymore the default symbols.

  @Kevin_Z 

What are the odds of getting a larger Access Control list?

  @Kevin_Z Hi Kevin. I have just rebooted the BE800 in satellite mode and it still shows only the exclamation mark "!"

 

It could be probably related as I had configured the symbols I wanted to show there before I have added it as a easy mesh node. I had configured the time, date and weather as symbols.

 

I had before adding it as a easy mesh node resettet the device with the reset tool and connected first on a only lan interface and when it was show up as easy mesh node switched to the wan/lan 10Gbit port.

 

But probably the device still thinks it is partially in router mode or the weather led symbol which was configured before trigger it somehow.

 

From the functionality I don't see so far with the clients any difference. As I see as example 6GHz device connected to it and it seams to work normally.

 

I have another understanding question.

I have 3 mesh nodes configured.

1 BE800 as main Router.

1 BE800 described above connected over 10GBit Ethernet.

2 RE900XD Extenders over WLAN.

 

Is it normal that the Extenders always connect to the main Router for the mesh? The BE800 mesh node with the Ethernet connection would be nearer to them and they could probably get a better back channel connection, if they would connect to it instead to the main router.

  @memzila 

I had a similar problem.

My network is: the main router BE800, and the satellite router is BE550 together connected by Ethernet cable. BE550 is in AP mode.

I connected to the easyMesh TP Link RE815XE mesh and it always, always connected to the main router which was one floor below. And next to it was BE550. When I installed it in the next room not far from BE550 it gave information that it was too close to the main router, but when I moved it two meters away it lost the 5 GHz signal. I couldn't get it to work with BE550, and when I connected it by Ethernet cable to BE550 it didn't want to work, and the main router kept restarting for no reason. So I disconnected RE815XE and sent it back because I had such an opportunity (I bought it on Amazon). The TP Link Mesh network is a joke. My previous network was based on AVM products and everything worked like clockwork, but then it wanted WiFi7 and from that moment on there were only problems. So to answer your question, you can't force this device to work with AP, it always connects to the main router. And that's it. There is clearly a software problem here. And it doesn't matter whether you have the official software for BE800 or the Beta version.

memzila wrote

  @Kevin_Z Hi Kevin. I have just rebooted the BE800 in satellite mode and it still shows only the exclamation mark "!"

 

It could be probably related as I had configured the symbols I wanted to show there before I have added it as a easy mesh node. I had configured the time, date and weather as symbols.

 

I had before adding it as a easy mesh node resettet the device with the reset tool and connected first on a only lan interface and when it was show up as easy mesh node switched to the wan/lan 10Gbit port.

 

But probably the device still thinks it is partially in router mode or the weather led symbol which was configured before trigger it somehow.

 

From the functionality I don't see so far with the clients any difference. As I see as example 6GHz device connected to it and it seams to work normally.

 

I have another understanding question.

I have 3 mesh nodes configured.

1 BE800 as main Router.

1 BE800 described above connected over 10GBit Ethernet.

2 RE900XD Extenders over WLAN.

 

Is it normal that the Extenders always connect to the main Router for the mesh? The BE800 mesh node with the Ethernet connection would be nearer to them and they could probably get a better back channel connection, if they would connect to it instead to the main router.

 

  @DanielOK

 

Hello, 

Can I ask which firmware you use on BE550v1?

 

Becouse I have the BE800v1 + 2x BE550v1 satellite easymesh (one connected with Ethernet and the second by Wi-Fi).

I remember BE550v1 1.0.12 Build 20240902 firmware, was bad from me :( all the time, the Internet gets disconnections, or satellite routers stop answering, totally unstable for EasyMesh. 

 Previous 1.0.11 Build 20240807 for BE550v1 was a bit better, but it's buggy with the LED light if you turn them off manually on the satellite device. After time, you may lose internet or stability of satellite router. 

 

BTW TP-LINK Enegainers sent to me a new beta for BE550v1 couple weeks ago. 

And works the most stable from what i test before and also have AP Easymesh feature.

If you PM me, I will send you a link to download. And you can check out how it will work for you.

I notice there is a little bug with speed and USB storage, but at least sattlite routers works much stable than other firmwares on easymesh.

 

What i know TP-link engieners already working on it to fix it.

So hope soon we will get new offical firmare or new preview beta to test for BE550 and BE800 :)

  @Kevin_Z 

 

Hi, I updated my BE800 to this pre Release version and now I cannot login via Webinterface. I only see the Picture of teh TPlink Beta Wallpaper. Via Tether App I can login, but cannot downgrade the Firmwar eto the latest official build.

Even after several Power Off's and unplugging the PSU, no login possible to the Webinterface.

 

Is there a way I can downgrade or fix this?

 

br

Mike