Firewall Rule to Restrict WebUI Access on TAP200 Not Working

Dear Teltonika Support Team,

I am using a RUTX50 Router and have three TAP200 Access Points in my network. My goal is to restrict WebUI access for the TAP200s (Ports 80 and 443) to specific IP addresses.

I have created the following Firewall Rules on the RUTX50 under Network → Firewall → Traffic Rules:

Rule: Allow access for Admin PCs

  • Protocol: TCP
  • SourceZone: “GuestZone“
  • Source Address: 10.10.10.100 (Admin PC)
  • Source Port: Any
  • Destination zone: input
  • Destination Address: 10.10.10.2, 10.10.10.3, 10.10.10.4 (TAP200s)
  • Destination Port: 22, 80, 443
  • Action: ACCEPT

Rule: Block access for all others

  • Protocol: TCP
  • SourceZone: “GuestZone“
  • Source Address: Any
  • Source Port: Any
  • Destination zone: input
  • Destination Address: 10.10.10.2, 10.10.10.3, 10.10.10.4 (TAP200s)
  • Destination Port: 22, 80, 443
  • Action: DROP

Additionally, I have also created a similar rule for the RUTX50 Router itself, and it is working as expected, restricting access properly.

Issue: Despite these rules, everyone in the network can still access the WebUI of the TAP200s.

Question: Is there a specific setting on the TAP200 or RUTX50 that I need to adjust to enforce the access restriction effectively?

Thank you for your assistance!

Hello,

As I understand, TAP devices are in the same network as you’re trying to restrict access from. This is unlikely to work, as traffic within the same firewall zone will simply bypass the firewall.
I would suggest configuring separate VLAN either for WebUI/SSH access of TAP200s, or seperate VLAN for TAP users. This way you will have traffic separation and can control traffic leaving/exiting the TAP WiFi network.
If you’d like to place TAP users to a different network, you can follow this guide: https://wiki.teltonika-networks.com/view/How_to_set_up_a_guest_WiFi_network_on_RUTX, just instead of assigning the new RUTX50 guest LAN interface to WiFi AP, assign it to the port that TAPs are connected to. Make sure to use tagged VLANs.
Then on TAP device, edit the created APs and specify the VLAN ID that will be used for user traffic.
Let me know if you need any further help!

Best regards,

Hi,

Thank you for your response and the suggestion to use VLANs for traffic separation. However, the switch used in this setup is unmanaged, meaning VLAN configuration is not possible.

Given this limitation, is there an alternative method to restrict WebUI access to the TAP200s without VLANs? Ideally, I would like to ensure that only specific IP addresses (e.g., Admin PCs) can access the TAP200 WebUI, while blocking all other devices in the same subnet.

I appreciate your guidance on this issue.

Best regards,

Hi,

Just to clarify - the VLANs should be configured on the router. If the switch is unmanaged it will simply forward the traffic with VLAN ID, no additional configuration is needed. Then TAP will only use the VLAN ID for all user traffic.

Best regards,