Unable to reach PCs behind RUTX50 from Amarisoft 5G Callbox

[kba]

Hello,

I am experiencing an issue with my RUTX50 connected to an Amarisoft 5G Callbox. Here is my setup and what I have done so far:

Initial situation (NAT enabled)

PCs behind the RUTX50 were accessing the 5G network through the router.

The router had its WAN IP assigned by the Callbox: 192.168.3.2.

The Callbox could see the router, but could not reach the PCs behind it.

Attempt to ping PCs

When I tried to ping the PCs from the Callbox, the 5G network could not see them, which is expected with NAT.

Switch to bridge / IP passthrough mode

I set the RUTX50 to bridge mode, so the PCs would get an IP from the 5G network via the router.

The PCs now receive an IP, but the Callbox still cannot ping them.

Added a route on the Callbox

I added a static route to the LAN network via the router’s WAN IP (192.168.3.2).

Despite this, communication to the PCs behind the router still fails.

Current configuration:

RUTX50: NAT disabled, firewall Forward FRAMED → LAN = accept

PC: LAN IP 192.168.1.249, gateway 192.168.1.1

Callbox: static route 192.168.1.0/24 via 192.168.3.2

Does the RUTX50 block WAN → LAN traffic even without NAT, and if so, what configuration or alternative would allow the Callbox to reach the PCs behind the router on a private 5G network?

Thank you in advance for your assistance.

[Martynas]

Hello,

By default, the firewall on the RUTX50 does not allow forwarding traffic from WAN to LAN, even when NAT is disabled. In your case, you will need to add the LAN zone to allow forwarding from the WAN zone in the WAN zone settings:

If the Callbox still cannot reach the RUTX50 LAN network, could you please share a simple sketch of your network topology, including the IP addresses?

Additionally, there was a similar topic regarding accessing the LAN network from WAN that might be helpful or provide some insights for your setup:

Two-way WAN-LAN connection

Hello community, I'm learning with Teltonika products and have the following question: I have two different networks on WAN and LAN. I log in from the LAN side and can reach the devices behind the WAN, but if I log in from the WAN side, I can't reach any devices behind the LAN! What's the simplest rule for two-way communication? Thanks.

Best regards,

[kba]

Hello,

Thank you for your response.

I have applied the suggested configurations:

• Static route on the Callbox to the RUTX50 LAN network (192.168.1.0/24 via 192.168.3.2)

• Verified automatic routes on the RUTX50

• FRAMED (WAN) firewall zone allows forwarding to LAN

However, the Callbox still cannot reach the PCs behind the RUTX50.

• The PC can ping the RUTX50 WAN interface (192.168.3.2)

• The PC cannot ping the Callbox (192.168.3.1)

To clarify the situation, I am attaching a diagram of my complete network topology, showing all interfaces and IP addresses used.

Thank you in advance for your help in identifying what is blocking the WAN → LAN communication.

[Martynas]

Hello,

Apologies for the delay in getting back to you, and thank you for the clarified setup description with topology.

Could you please confirm whether this issue is still relevant?

If so, for this specific setup, you’ll need to have enabled Framed routing under Network → WAN → mob1s1a1 settings:

Best regards,

[kba]

Hello,

Thank you for your message. I am trying to apply this configuration, but it fails with the “failed to edit configuration” error. The issue is still ongoing.

Thank you for your help.

Best regards,

[kba]

Hello,

I always can’t apply this configuration, may be it’s not possible for a wan cellulaire ??

Best regard !

[Martynas]

Hello,

Could you please confirm which firmware version your RUTX50 is currently running?

If possible, could you try updating the device’s RutOS firmware to the latest available version (7.18.1), either with or, if feasible, without “Keep Settings” enabled, and then checking whether the issue persists?

Best regards,

[kba]

Hello,

Thank you for your reply.
I updated the firmware and currently have the “framed routing” option enabled.
However, the callbox still can’t ping the PCs behind the router (192.168.1.0/24).

Best regards,

KB

[Martynas]

Hello,

Could you please share screenshots of all configuration changes made so far? In general, this setup should work with only the Framed routing option enabled and a static route to 192.168.1.0/24 via 192.168.3.2 configured on the Callbox. There’s no need to modify any settings in the “Framed” or “WAN” firewall zones.

For testing purposes, for a clean setup, if feasible, first try factory resetting the RUTX, then enable framed routing on the mob1s1a1 interface and leave the firewall zones as default.
Make sure the static route is correctly configured on the Callbox, and if the Callbox still cannot reach the 192.168.1.0/24 network, add a static route (Network → Routing → Static Routes) on the RUTX with the following parameters:

• Interface: mob1s1a1
• Target: 192.168.3.0
• Netmask: 255.255.255.0
• Gateway: 192.168.3.2

I hope this helps to achieve your setup.

Best regards,

[kba]

Hello,

I have reset the RUTX50 to factory defaults and applied the recommended configurations (enabled framed routing, added the static route, and verified the firewall zones).
However, the communication is still not working as expected.

Please find attached the screenshots of the applied configurations.

Best regards,
KB