Ethernet backhaul not enabled

Hello,

I recently acquired a Microtik Router with RouterOS. I updated to v7.2.3
On my previous router Ethernet backhaul was working out of the box, but now I can’t find how to enable this in Router OS.
Because I already had a mesh system. I ordered a router without wifi. (RB750GR3)
But when I check my mesh AP’s they tell me there mutual communication is over wifi, While it should be over Ethernet because it’s more stable and faster.
Because of the heavy concrete in my home wifi communication between different floors is almost impossible or really poor.

I know in some routers I need to enable some kind of ethernet-backaul package.

But I can’t find how to do this.

no one has any solution?

I did some more research and found that Ethernet Backhaul is described in “IEEE 1905.1”.
https://en.wikipedia.org/wiki/IEEE_1905
https://standards.ieee.org/ieee/1905.1/4995/

I cannot find a final answer on this but it looks like Router OS does not support this standard, that’s why it’s not working.

I’m not sure how to apply a feature request so I send an email to support. But they haven’t respond yet.

I think support for this standard would be really valuable for people with Mesh networks.

Who is the producer of your Mesh? I’m asking because I tested for a long period of time a TPLink Deco X60 mesh, set as AP mode, connected to a Mikrotik HexPoe; Deco units reported Ethernet backhaul.

Hello,

I’m also using tp-link but Deco M4 instead of X60,
I checked and my deco’s are set to AP mode. I have installed the latest firmware(1.5.4)
Based on this drawing

url as image isn’t working: https://static.tp-link.com/Ethernet_backhaul_1614068228173u.png
I would like to set it up as the 3th option.
where router and switch are combined in my case,

And on my previous router my meshpoint were reporting ethernet, where now they are reporting 2.4Ghz/5Ghz which means wifi

My case was also the 3rd one: both X60s connected to a TP-Link switch which was connected to hex router.
If your config is same as mine, try connecting the second M4 directly to main M4, just to test if the switch is to blame.

I already did, And then it says Ethernet.

So it doesn’t seem to be the wiring.
One difference we have is that I don’t use a TP-link but connected all 3 AP’s directly to my mikrotik.

I actually had a reason not to by any more TP-link network stuff anymore. The reason was that most settings can’t be done in the webinterface and you need the app which you need to register.
But that’s another issue not related to this brand at all.

Try this: disconnect all 3 Decos and power them down. Power up the main M4 and connect it to Mikrotik router - don’t connect anything to its 2nd eth port. After it signals that everything is ok (I assume LED will turn from red to green), power up second M4 and connect its cable. Again, no other device connected to 2nd unit. Same for 3rd unit. After it goes green as well, check if app reports ethernet backhaul and afterwards connect other devices, if it’s the case, to the M4 units.

In the Mikrotik router, do you have any non-standard settings concerning bridge, ports etc?

I took me a while to find a timeslot where no one needed internet;)
but I found it.

I did the test, but one change. I left my DHCP server connected to Eth1, because without that server there shouldn’t be any connection possible.
I connected the mesh points in the order you asked, but still they are reporting WiFi.

for the settings I left most by default,
but I disabled DHCP, as I use the one from my pi.hole.
I also modified the default ip address to be equal to my previous gateway.
I have 2 port forwards, 1 for wireguard and 1 for homeassistant. but those are pretty straight forward.

Not sure where the problem is - I also have a PiHole in the network layout but DHCP is done by router; I use it only to filter DNS.

I managed to re-create the network - hexPoe and both Deco’s connected individually, directly to hex, main in port 2, slave (bedroom) in port 3.
The screenshot is taken within Deco app, from the 2nd unit.

Maybe it has something to do with this?
IMG_0766.jpg

“Maybe it has something to do with this?”
Maybe, But I don’t fully understand all of it.
I tried some stuff with “L3 HW offloading” but for some reason those settings are reset whenever I come back to the page.
all my ports are in switch one, so that won’t be it.
I tried something with Mesh, maybe I needed to setup something there but that broke the whole router so I needed to do a factory reset.
After this reset I checked the mesh status immediately but it still was wifi. so I applied my changes again.
I’m sure I’m missing something but I can’t figure it out.

Show Mikrotik settings

ah, this is how I can include images

All is default except form this
forwarding.png
and this
basic.png
I tried to play around with this checkbox,
hw offloading.png
but it doesn’t save

Edit: mask dyndns

I did and cables are fine,
Is there any debug stuff I can do?

Did you ever figure this out? I have a similar setup, all was fine while on RouterOS 6.5, updated to 7 and now Eth. Backhaul is gone…

just an update in case it helps anyone, I reverted to 6.49.6 and backhaul is back :slight_smile:

I actually went with OpenWrt https://openwrt.org/toh/mikrotik/rb750gr3 which fixed a few issues for me including the Ethernet Backhaul.

I won’t say you should use this, but it’s a possibility.

Hi!

News for this? My configuration is M9Plus + M4R + M4R with a Mikrotik hEX

M9Plus in ether3
M4R in ether4
M4R only for wify

In the DHCP Server you can see:
Screenshot 2022-11-17 105534.png
Thanks!

I’ve raised the support request for the issue and some good news are on the way:

“Hello,
We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide a release date now.
The workaround is to disable bridge HW offloading or use the “protocol-mode=none” setting for the bridge which disables RSTP.”

Cheers,
IP

Works for me!
Captura de pantalla 2023-01-10 174906.png
Thanks!!! :smiley:

Hi all!

Just for your interest, in version 7.7 you need to apply the workaround.
Still not fixed.

:wink: