The locations are 50m apart but no way to connect cable between.
I need to connect all the wired devices in “LocationB” to the “LocationA” network (RUTx50). The TAP100 is connected to a switch along with all the wired devices in “LocationB”
I’ve followed this example very closely, but I used my own SSIDs. I can see the mesh connection on both the RUTx50 and TAP100. I do not see a DHCP lease for the TAP100 on the RUTx50.
As soon as I turn on DHCP on the TAP100, following the guide, I loose the ability to connect to the TAP100 because for some reason traffic is not passing between TAP100 and RUTx50.
I have ticked correctly the option for pass mesh traffic.
Firmware is latest on both devices - 07.13.3
I just fallowed the whole guide with tap100 and rutx11(has same wifi radio) on 7.13.3 and everything worked. The only one thing that is not clearly mentioned with concrete step to do is selecting network: lan on rutx50 mesh config
If you already have it correctly set then not sure where to go from here with limited information. Did you checked system logs for wpa_supplicant messages. Do you see MESH-PEER-CONNECTED or MESH-SAE-AUTH-FAILURE . What is the last one? I saw that even if auth failed WebUI shows that mesh has a client(other node) is connected.
I think I found the problem. The RUTx50 is not functioning correctly. It will not give DHCP IP addresses to any client that tried to connect on LAN port or by WiFi. So it’s not giving IP address to the TAP100s either.
I tried everything to fix this problem, update firmware, restart DHCP. I will do a factory reset tomorrow to see if this fixes the problem. I let you know.