RUTx50 and TAP100 mesh

I have

  • RUTx50 in “LocationA”
  • TAP100 in “LocationB”.
  • 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 tried to create a mesh network following the advice here https://wiki.teltonika-networks.com/view/TAPxxx_Wireless_Mesh_Configuration

I need to be able to pass data through the Ethernet port of the TAP100 at “LocationB” It does not appear to work correctly.

My idea was to use client mode on the TAP100, which would be simple but this feature does not exist any more.

Please help

Cheers
Dave

Hi,

Need more info where did you stuck while making mesh:

  1. Does mesh status shows that it found other client?
  2. Did you tried to placing devices near each other to check if it is configuration or signal issue?
  3. “Scan 2.4Ghz” in Wireless > SSIDs page on RUTX50 and check if it finds mesh. Does it have decent signal?
  4. Make sure that you correctly fallowed instructions:
    1. Did you used 2.4ghz on RUTX50?
    2. Did you set same channel on both devices?

Also did you upgraded to latest firmware on both devices?

Try to check logs:

  1. Turn off mesh on one of the devices
  2. Turn on it back
  3. Wait for 1min
  4. Then on both devices
    1. Got to System > Maintenance > Troubleshoot
    2. Download “troubleshoot file” (for the future if support asks for it as you cannot upload it here)
    3. Check “System log” in System > Maintenance > Troubleshoot
    4. Check if the end of log does not have any weird stuff like stack traces
    5. Search for lines containing “wlan0-2” or “wpa_supplicant”. Maybe it tells something interesting

Hi Dainius

Thanks for your reply. I will check some of the system log files.

I did follow everything exactly and I’m using the 2.4Ghz radio on both, all on the same Channel 8.

Do you know if it’s possible to achieve my request to use the Ethernet port on the TAP100 to connect remote site wired device to the RUTx50?

Cheers
Dave

Yep, https://wiki.teltonika-networks.com/view/TAPxxx_Wireless_Mesh_Configuration should bridge both device ports (except wan port on RUTX50) without any other changes

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.

Hi @Dainius

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.

Cheers, Dave

Hello @DaveRoberts,

Could you please let me know if your issue has been resolved or if you still need assistance?

If the problem persists, please share your WebUI configuration here so I can review it and ensure everything is set up correctly.

Best regards,

Hi @marija

The problem was with the DHCP server in the RUTx50 not giving addresses. We made a factory reset and now it’s working. It’s a bit slow, but it works.

The issue is resolved, thanks for asking

Hello,

Thank you for confirming that!

Feel free to reach out on the forum if you need any further assistance.

Best regards,

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.