RV50x - Port Forwarding Not Working

AirLink Routers AirLink routers
1

I have a RV50x running the latest available ALEOS and Radio Firmware.
ALEOS Software Version: 4.15.3
ALEOS Build number: 003

|Device Model:|RV50X|
|Radio Module Type:|MC7455|Radio Module Identifier:|VERIZON|
|Radio Firmware Version: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30|

See attached image showing these versions:
Version Info

I am unable to get Port Forwarding to function.
I have a device on the LAN at http://192.168.1.100 which has a web server running on port 80. When my laptop is connected to the LAN I can access the website so I know this device is accessible when I am on the same network.

The device at 192.168.1.100 has a statically assigned IP.
My DHCP range supplied by the RV50X starts at 192.168.1.125.

I have the following Port Forwards enabled:

PortForwards
PortForwards1520×578 28.5 KB

I tried setting the Stop Port Number to match the Start Port Number and also set the Stop Port Number to 0, but this did not make a difference.

I do have Inbound IP restrictions enabled as shown below as I don’t want just anyone connecting :wink: :

IPRestrictions
IPRestrictions1287×470 19.2 KB

Even with these IP restrictions removed I am unable to connect to any of the ports I have setup in the Port Forwarding screen.

Is this a bug with this model/firmware?
Are there other settings I need to enable to allow the Port Forwarding setting to function?
Is there any logging or configuration I can supply to help diagnose this problem?
Thanks!

2

Hi @ITDude ,
Welcome you to our community!
Could you please share with me some information as below so I can help you further:

  1. Please let me know How do you want to use Port Forwarding? Where do you forward the data and where do you want to receive it?
  2. What interfaces are you using for Port Forwarding? (eg Ethernet, Cellular, …)

Thanks,

3

Hi jerdung,
Thanks for your reply! It turns out we had some misconfiguration on the web server where it was only allowing traffic from certain external IP addresses. For port 23 we should have it set to port 22 and I believe the vendor managing connections to the port 22 services may have been restricting access to certain external IPs as well.

Once I removed all the Trusted IP Restrictions (Friends) and we reconfigured access on port 22 and 80 on those particular services, the Port Forwarding started working.