I can ping myself through the open vpn assigned IP
I can ping the RUT through 192.168.100.10 and access its config page through HTTP. This IP was the one that is shown in General / Sessions
I CAN NOT ping the PLC through 192.168.100.3
Following another post’s suggestion, I logged into the RUT device config page, headed to Network → Firewall → Zones and set the Masquerading option in “lan⇒wan” to ON. For some reason it was OFF. In the other zones it was already ON.
Still can’t ping the PLC through 192.168.100.3. What am I doing wrong? Thank you!
I followed the video steps, where they demo how to use the RMS / VPN to access a camera. Very similar to my scenario. And it worked in the video.
Basically in the router section, I selected the automatic discover of end devices. They presented all found, I clicked the one I’m interested in (the PLC 192.168.100.3), and selected ADD. It created that route for me.
The automatically created route made sense to me, as with the netmask 255.255.255.255 (ie, all /32 bits reserved for the host), I thought I basically were only opening the desired host. No need to open up all the 255 range of addresses, as with a 255.255.255.0 net mask.
Anyway, I’ll try your suggestion (I don’t have access to the route right now).
Could you (or someone else) explain if my thought process was correct or why it isn’t? How to open access to just one end device / host?
By default, the Virtual Network IP address is 192.168.255.0, we don’t usually change this at all, and technically speaking, it shouldn’t cause issues either, but I believe this would cause an IP conflict between your LAN (which is also 192.168.100.0/24) and the server address, which, you’ve set to the same LAN.
When it comes to your questions, you did everything like it was supposed to be done, no issues whatsoever, changing from a direct IP to the entire subnet is just good practice if there’s a need to add more than a single device, or even reaching the RUT + the end device without having to create multiple routes.
Hi MatasR. Thanks again for your reply and for noticing the change I had made to the Virtual Network IP address. I had done that in “desperation”. Changed back to 192.168.255.0, but no success solving the problem.
(btw, I noticed in the original post I uploaded the wrong screenshot for sessions)
As before, I can ping and access the device (RUT) config page, through the IP shown in the sessions: now through 192.168.255.10 instead of 192.168.100.10 as was before. I also don’t understand why it is 192.168.xxx.10 and not 192.168.xxx.1. What if I wanted to access the .10 end device?
Nevertheless, I just can ping myself (192.168.255.6) and the router (192.168.255.10). Not the PLC (expected it would be 192.168.255.3).
Any suggestions? Should I change some configurations in the router config pages?
I’m using openvpn software, and using the ovpn file downloaded from my RMS user. Should I try to use the built-in vpn from windows 11? Would it help? (nevertheless, I’m currently able to access the router page through 192.168.255.10…).
Also strange is that pinging 192.168.255.4 gives “Destination host unreachable.” instead of “Request timed out.”. Tested pinging several addresses (from .1 to .25) and besides .6 (me) and .10 (router) that work ok, all gave “Request timed out.” error, except the .4 that gave “Destination host unreachable.”.
Any suggestions? Any way to “debug” where the problem / problems are?
I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is **14911**.
Hi. Just filled and submitted the form. Will this now create a ticket, accessible through a different place?
Just fyi, I’ll be on vacation (for one week) without computer, starting this Sunday.
Thank you.
