Solved asus be92u & bd4 zenwifi via ethernet backhaul local connectivity issue

[xofrot]

hello,

I would like to submit an issue I encounter with the Following setup I have put in place in my home network.
In summary I am facing some kind of Connectivity routing issue between 2 clients connected via an asus RT-BE92U (wired) and some esp32 based devices (Shelly, esphome, …) connected via the Zenwifi BD4 mesh solution.

here is the topology:
- Main router rt-be92u configured with DHCP and network 192.168.1.1 and subnet 255.255.254.0 (so 192.168.0.1 until 192.168.1.254)
- WAN 10g is connected to modem (modem is bridge mode)
- LAN/WAN1 of router connected to my main PC with fixed ip
- LAN2/3 connected to switches to distribute amongst all home devices
- lan4 connected to BD4, 3 pack zenwifi solution, with a wired backhaul (so lan4 to lan1 of bd4 node1, then LAN2 of mesh node1 to lan1 of node2 bd4, then lan2 to lan1 of node3 bd4)
- BD4 mesh devices have been configured with ethernet backhaul setting, and with priority of LAN1 to force them to use ethernet
- Proxmox server is running with homeassistant vm on same subnet (wired).
- main wifi is configured with same subnet


The problem encountered is that when setting this up, the AI mesh is perfectly recognized, devices are connecting to the zenwifi mesh and they all have access to internet.
However, I run into issue when homeassistant (or any other host behind proxmox, including proxmox itself) tries to connect locally from a device connected to one BD4 mesh node.

if I try to connect from my main pc to the wifi esp32 devices, no issue.
if home assistant tries to connect to the same devices, there is no Connectivity at all (ping or http).
if I try to connect from internet to the devices it also works
Only local to local connectivty seems broken (for example 192.168.1.50 to 192.168.1.101)
IF i force the esp32 to use the aimesh of the main router (and not the BD4), then the Connectivity is restored…


This lead me to Believe there is an issue when using BD4 mesh, coupled with router BE92u.

I performed the Following change :
- switched from full ethernet backhaul to normal mode, with manual priority of each port on the BD4, no change
- switched from daisy chain Connectivity (from one BD4 node to the other), towards star-like Connectivity, using ethernet from the main router to each BD4 nodes individually (no change)

However, when I completely deactivated the backhaul ethernet to force using the 5ghz wifi, everything is working as expected… I can fully connect from each devices to other ones in the subnet…

this scenario was tested several times, and the result was the same, enabling the ethernet backhaul cuts the Connectivity between esp32 device and proxmox VM HA…


Last note:
I swapped the connection between LAN1 and LAN4 of the router : (lan1 beeing the BD4 ethernet backhaul and lan4 my home pc)
there I got the Following result :
- BD4 mesh is not able to connect to homeassistant and proxmox server, no issue
- my home pc seems to be the only one that is now not able to connect to other local ip's in same network (so no wifi involved). no able to connect to wifi esp32 or proxmox server.
- my first thought was that is was then not related to BD4 wifi mesh, BUT again, as soon I reverted to 5ghz backhaul, I was able to connect to all my devices !


my main clue is now that there is Something fishy with the ethernet backhaul somehow between this router and the BD4... so any experience is welcome ;-)

thanks again for your time reading all this, I am very curious about other things to try to find out what is happening here...

 

[jzchen]

There are a couple of sentences there that I am not clear whether access is not, now please check over your meaning....

If there is Priority option then you did not select "Ethernet Backhaul Mode" or Ethernet Backhaul Mode did not fully set correctly. It is under General -> AiMesh -> System Settings (tab) in the web GUI

If the router is set to 192.168.1.1 and 255.255.254.0 then 1-2 subnets are allowed: 192.168.1.xxx to 192.168.2.xxx.

I used to have 252 and it used to be 50 - 53. But after a firmware update (to a different model router) and re-setup it change to 48 - 51, both with router 192.168.50.1. I then changed to 254 so 50-51...

There was a reported LAN isolation issue and seems like you may be experiencing it. Make sure you have the latest firmware (released 4/1) or Merlin...

 

[Tech9]

RT-BE92U has/had bugs around LAN ports.

Looking for Feedback: RT-BE92U stability issues

Hi, I'm trying to gather more info/feedback from RT-BE92U owners who are suffering from major performance issues, or general instability or crashes. If you are experiencing issues, please test again using the latest stock firmware (if you were using Asuswrt-Merlin). If you can still reproduce...

www.snbforums.com

Solved - RT-BE92U LAN communication problem with original firmware

Router: ASUS RT-BE92U Firmware: 3.0.0.6.102_38980 So I just bought the above mentioned router and wanted to run some test with the original firmware before installing Merlin. My problem is that any device connected on Lan port 1 can speak to all other devices connected to the other Lan ports...

www.snbforums.com

Not sure if fixed already or not. This router is causing trouble for many users.

 

[xofrot]

RT-BE92U has/had bugs around LAN ports.

Looking for Feedback: RT-BE92U stability issues

Hi, I'm trying to gather more info/feedback from RT-BE92U owners who are suffering from major performance issues, or general instability or crashes. If you are experiencing issues, please test again using the latest stock firmware (if you were using Asuswrt-Merlin). If you can still reproduce...

www.snbforums.com

Solved - RT-BE92U LAN communication problem with original firmware

Router: ASUS RT-BE92U Firmware: 3.0.0.6.102_38980 So I just bought the above mentioned router and wanted to run some test with the original firmware before installing Merlin. My problem is that any device connected on Lan port 1 can speak to all other devices connected to the other Lan ports...

www.snbforums.com

Not sure if fixed already or not. This router is causing trouble for many users.

yes using latest firmware stable release : 3.0.0.6.102_39061

it is indeed not easy to pinpoint if issue is located at router or zenwifi bd4 side, but as I managed to get the router configured with my modem to get a wan ip, I am a bit reluntant to reconfigure everything only using BD4 to exclude router

 

[xofrot]

There are a couple of sentences there that I am not clear whether access is not, now please check over your meaning....

If there is Priority option then you did not select "Ethernet Backhaul Mode" or Ethernet Backhaul Mode did not fully set correctly. It is under General -> AiMesh -> System Settings (tab) in the web GUI

If the router is set to 192.168.1.1 and 255.255.254.0 then 1-2 subnets are allowed: 192.168.1.xxx to 192.168.2.xxx.

I used to have 252 and it used to be 50 - 53. But after a firmware update (to a different model router) and re-setup it change to 48 - 51, both with router 192.168.50.1. I then changed to 254 so 50-51...

There was a reported LAN isolation issue and seems like you may be experiencing it. Make sure you have the latest firmware (released 4/1) or Merlin...

thanks for your reply, I was sure this forum have experienced user that help me figure out what is happening ;-)

to clarify the ethernet backhaul points, in fact, I tested both configuration, with similar results, if I use ethernet backhaul mode or if I switch to normal mode with priority, I got the same results...

about your second statement, What is confusing me is that normally if I set 192.168.1.1 with a /23 (255.255.254.0) then I expect the router to assign dhcp addresses from 192.168.0.1 to 192.168.1.254, and not the 192.168.2.x range.
That is indeed what is happening, I got some devices assigned with range 192.168.0.x ip... which I find normal... to not complicate the topic, I let dhcp assign the range 192.168.0.x to mobile devices, that are not used in my in home domotic, and I regulate the range 192.168.1.x with fixed ip and manual assign ip's...

If anybody has experience in issue working like this, I can for sure reduce the range and only works with a /24 subnet ;-)

I heard about firmware release as well, kindly let me know if there is any advantage to test or investigate specific ones... I am very open to test stuff ;-)

 

[jzchen]

Yes the router LAN DHCP Server settings will only allow a range that is acceptable to it. If you try the wrong way it will not allow it. What confused me was the first setup I tried to encompass the same subnet as my AT&T BGW320-500 gateway which I switched to 192.168.68.254 address. A TP-Link router (specifically a Deco BE95) would automatically enforce separating the subnets behind the gateway. I did not realize this was a "no-no". But I think initially with older firmware the BE19000Ai avoided that by setting 50-53....

Merlin's latest firmware appears to solve the LAN isolation issue. (I think there was a random reboot issue but I am not sure):

3006_102.7_2 would be the one to try:

Asuswrt-Merlin - Browse /RT-BE92U/Release at SourceForge.net

Alternative firmware for Asus wireless routers

sourceforge.net

 

[xofrot]

Yes the router LAN DHCP Server settings will only allow a range that is acceptable to it. If you try the wrong way it will not allow it. What confused me was the first setup I tried to encompass the same subnet as my AT&T BGW320-500 gateway which I switched to 192.168.68.254 address. A TP-Link router (specifically a Deco BE95) would automatically enforce separating the subnets behind the gateway. I did not realize this was a "no-no". But I think initially with older firmware the BE19000Ai avoided that by setting 50-53....

Merlin's latest firmware appears to solve the LAN isolation issue. (I think there was a random reboot issue but I am not sure):

3006_102.7_2 would be the one to try:

Asuswrt-Merlin - Browse /RT-BE92U/Release at SourceForge.net

Alternative firmware for Asus wireless routers

sourceforge.net

Thanks I will try that.

As it is first time I do that, can you let me know if I can use the same firmware for the BD4 wifizen nodes ? I assume all nodes must run the same version... ?

 

[jzchen]

Thanks I will try that.

As it is first time I do that, can you let me know if I can use the same firmware for the BD4 wifizen nodes ? I assume all nodes must run the same version... ?

The firmware is router model (and hardware version where noted) specific. Please do not try to install RT-BE92U firmware onto the BD4s, (although there are safeguards to protect from this happening I have never dared try).

 

[Tech9]

As it is first time I do that

Keep using the stock firmware. If your issue is the port related one - the fix is coming from ASUS, they'll update the firmware at some point. In general on future upgrades avoid the cheapest devices of the type and check user feedback before purchase. There is a lot of false advertising around consumer products and specific devices are more problematic than others. In general AiMesh with one tri-band main router and 3x dual-band nodes in home environment is a recipe for disaster already.

 

[xofrot]

The firmware is router model (and hardware version where noted) specific. Please do not try to install RT-BE92U firmware onto the BD4s, (although there are safeguards to protect from this happening I have never dared try).

Thanks a lot, looks like the merlin FW did the trick indeed.

I had some doubt after installing it and restarting because the ai mesh with bd4 nodes were not able to join, but after disabling the ethernet backhaul mode, and using the default one where you can indicate the preferred interface, everything is able to interconnect.
I have also access to all ip's in subnet, including the ones connected to proxmox and bd4 wifi devices, together with a wired backhaul...

I'll then stick to ths configuration and enjoy the additional features of the merlin firmware... I hope the bug will be fixed officially, don't know how to report it to Asus for push to solve or if it's just a matter of time ...

thanks again for your support, I knew I was at the right place !