EasyMesh Ethernet Backhaul Bug: Link Remains Limited to 100 Mbps After Replacing Cat5 with Cat7 Cable

[tulgar]

Description

Hello Keenetic Team,

I would like to report a possible EasyMesh Ethernet backhaul issue.

Environment

• Keenetic routers configured in an EasyMesh network.
• Initial Ethernet backhaul established using a Cat5 cable.
• The Cat5 cable negotiates at 100 Mbps, which is expected.
• After the mesh network is fully established, the Cat5 cable is replaced with a Cat7 cable.

Problem

Although both routers report that the Ethernet link is connected at 1 Gbps, the actual communication between the mesh nodes continues to be limited to approximately 100 Mbps.

The system appears to keep using the previous 100 Mbps link parameters even after the physical connection has successfully renegotiated to 1 Gbps.

Expected Behavior

After replacing the cable with a Cat7 cable and the Ethernet link successfully negotiating at 1 Gbps, the EasyMesh Ethernet backhaul should immediately utilize the full Gigabit bandwidth.

Temporary Workaround

The only way I have found to restore Gigabit backhaul performance is to recreate or reinitialize the mesh connection. Simply reconnecting the Ethernet cable or waiting for auto-negotiation is not sufficient.

Additional Notes

This behavior can easily mislead users because the interface correctly reports a 1 Gbps Ethernet connection, while the actual mesh backhaul throughput remains capped at around 100 Mbps.

Could you please investigate whether this is an EasyMesh backhaul caching issue or a firmware bug?

Thank you.

[tulgar]

I have found the cause of the issue.

The problem was resolved after I manually set Port 2 to 1000 Mbps in the port settings. After making this change, the EasyMesh Ethernet backhaul started working correctly at Gigabit speed.

 

Thank you for your time and for looking into this. I really appreciate your support.

Edited July 16 by tulgar

[KYTECHNGAMING]

Which model/models do you use? 

[tulgar]

hopper and giga

Edited July 13 by tulgar

[tulgar]

I would like to emphasize that this is not a minor issue.

 

I believe this issue deserves further investigation from the Keenetic team.

[eralde]

2 hours ago, tulgar said:

I would like to emphasize that this is not a minor issue.

 

I believe this issue deserves further investigation from the Keenetic team.

Hello @tulgar

Please attach self-test files from the Keenetic devices experiencing this issue here or contact the tech support.
Since self-test files contain sensitive data, if you decide to attach them here, we will hide them so that only forum moderators and administrators can see them.

[eralde]

@tulgar thank you, I see the self-tests 🤝
I've made them visible for moderators.

[eralde]

@tulgar I see speed negotiation for Ethernet in the self-test for KN-3810, but there are no messages about that in the self-test for KN-1010. I find that quite strange.

Can you tell me which ports on both devices you used to connect them to each other or to some other equipment?

[tulgar]

21 minutes ago, eralde said:

@tulgar I see speed negotiation for Ethernet in the self-test for KN-3810, but there are no messages about that in the self-test for KN-1010. I find that quite strange.

Can you tell me which ports on both devices you used to connect them to each other or to some other equipment?

• KN-3810: Port 2
• KN-1010: Port 1

[eralde]

20 minutes ago, tulgar said:

I have found the cause of the issue.

The problem was resolved after I manually set Port 2 to 1000 Mbps in the port settings. After making this change, the EasyMesh Ethernet backhaul started working correctly at Gigabit speed.

 

Thank you for your time and for looking into this. I really appreciate your support.

Great news!

Thank you for looking into the issue in more detail and finding a solution on your own 🔥

[tulgar]

24 minutes ago, eralde said:

Great news!

Thank you for looking into the issue in more detail and finding a solution on your own 🔥

 

I have noticed another issue while using MainOS 5.1.1.

Devices connected to the network are sometimes displayed under the wrong network segment on the main router. The actual network connection and functionality are correct, but the segment shown in the web interface does not match the segment to which the device is actually connected.

 

Unfortunately, I haven’t found any workaround or solution for this issue yet.😂😂

 

[eralde]

1 hour ago, tulgar said:

I have noticed another issue while using MainOS 5.1.1.

Devices connected to the network are sometimes displayed under the wrong network segment on the main router. The actual network connection and functionality are correct, but the segment shown in the web interface does not match the segment to which the device is actually connected.

Unfortunately, I haven’t found any workaround or solution for this issue yet.😂😂

Thank you @tulgar
This is a know issue that will be fixed in one of the future releases 🙂

[KYTECHNGAMING]

@Atalante