This document provides step by step procedures to set up communication to the LAN side of a wired router to devices that do not have a default gateway. For example, a plant floor has a wired router at various locations. Each device behind the wired router has the same LAN subnet i.e. 192.168.10.0/24 and no default gateway set on any device. Remote access to devices in that LAN will be problematic since all traffic outside of that LAN’s subnet will get dropped due to the lack of a configured default gateway. This document solves that problem by using Masquerading and Port Forwarding.
RAM-6021 & RAM-6021M12 Wired Router
Web Browser
4.16 or higher
Set up a Wired Router to get access to devices on the LAN side that does not have a default gateway set using port forwarding
Part 1 – Setting up IP address on ETH1
In this example, we will use the following setup:
Edit where needed to fit your network subnet and topology.
When done entering all information, click Apply
Part 2 - Setting up Masquerade Rule
Here we set up masquerade rules to NAT the source subnet on the WAN side of Router.
Part 3 - Setting up Port Forwarding
Here we set up forwarding to send traffic to different devices behind the router on the LAN side.
Note: In this example, we are using Windows Remote Desktop for proof of concept. If using another device behind the router that has a web interface such as a Red Lion DSP, substitute port 3389 for port 80 or whichever port is configured on the connected device.
Part 3 - Setting up Port Forwarding
Here we set up forwarding to send traffic to different devices behind the router on the LAN side.
Note: In this example, we are using Windows Remote Desktop for proof of concept. If using another device behind the router that has a web interface such as a Red Lion DSP, substitute port 3389 for port 80 or whichever port is configured on the connected device.
Part 5 – Test
Note: A ping test will not work in this case because the firewall does not forward pings to LAN devices. This is strictly for accessing devices behind the router like web UI’s, polling Modbus, etc using port forwarding.
It is the customer's responsibility to review the advice provided herein and its applicability to the system. HMS makes no representation about specific knowledge of the customer's system or the specific performance of the system. HMS is not responsible for any damage to equipment or connected systems. The use of this document is at your own risk. HMS standard product warranty applies.
If you have any questions or trouble, contact HMS Technical Support by clicking here.
For more information: Product warranty and return policy | HMS Networks