As the title says, I have a RUT240 setup to transfer LPR data from a camera to a VPS that further handles the data. However, it was working perfectly fine until the update to the latest firmware. Nothing from the configuration settings have been altered at the time.
Now even though both the RUT240 CLI and the VPS can access external devices/IPs, they don’t communicate with each other AT ALL.
The port forward from the camera to the static IP of the router works as intended since it can be accessed from a browser/Postman.
There are no rules that reject any traffic.
I’ve tried turning off all attack prevention settings, to no avail.
My latest thought was that somehow the static IP of the VPS got blocked by the router, but there is no information in the “logread” command from the CLI on RUT240, and whenever I try to access the “System → Administration → Access Control → Security” screen, it gets stuck on the spinning loading animation (I left it for more than an hour so no, it’s not a huge data problem).
It sounds like you’ve encountered quite the conundrum with your RUT240 setup. Have you tried reaching out to the manufacturer’s support team? They might have insights or solutions specific to this firmware update. Additionally, have you considered rolling back to the previous firmware version to see if the issue persists? Sometimes, updates can introduce unexpected bugs or changes that affect functionality. It’s frustrating when things that used to work seamlessly suddenly stop cooperating, but hopefully, with a bit of troubleshooting and perhaps some assistance from the experts, you’ll get your setup back on track soon!
You mentioned that port forwarding from the camera to the router works and that the camera can be accessed from a browser or Postman. This indicates that the issue likely lies in the connection between the router and the VPS.
Could you provide more details about the data transfer solution you are using and the settings configured on the RUT240 for this solution?
The router was updated to RUT2_R_00.07.06.11, and the modem to EC25ECGAR06A09M1G_01.001.01.001. I got reassured by the VPS provider (ISP that provides the 4G) that the VPS has allowed communication from and to the corresponding ports to the router.
The communication is done via API fetch (same as Postman), and has been working as intended for the past 2 years until now. The same application run locally establishes communication to the router and pulls data. I saw that in the firmware update there are a lot more Network settings, which might have overwritten/defaulted the previous ones?
Just because your ISP has opened certain ports for communication doesn’t mean those ports will automatically be open on your router. If you know which ports need to be open, go to Network → Firewall → Traffic Rules on your router and open those specific ports.