Weidmueller
Weidmueller
User Manual
Edition 1.0
2022-11-25
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
Copyright Notice
Copyright © 2022 Weidmüller Interface GmbH & Co. KG
All rights reserved.
Reproduction without permission is prohibited.
Disclaimer
Information in this document is subject to change without notice and does not represent a commitment on the part of Weidmüller.
Weidmüller provides this document "as is," without warranty of any kind, either expressed or implied, including, but not limited to,
its particular purpose. Weidmüller reserves the right to make improvements and/or changes to this manual, or to the products
and/or the programs described in this manual, at any time.
Information provided in this manual is intended to be accurate and reliable. However, Weidmüller assumes no responsibility for its
use, or for any infringements on the rights of third parties that may result from its use.
This document might include unintentional technical or typographical errors. Changes are periodically made to the information
herein to correct such errors, and these changes are incorporated into new editions of the publication.
Contact Information
Weidmüller Interface GmbH & Co. KG
Klingenbergstrasse 26
32758 Detmold
Germany
Phone +49 (0) 5231 14-0
Fax +49 (0) 5231 14-2083
E-Mail info@weidmueller.com
Internet www.weidmueller.com
1. Introduction
1.1 About
Weidmüller Routers of series IE-SR-2TX-WL-(4G) are reliable and cost-effective Industrial Security Routers, providing a versatile and
redundant Internet / WAN connectivity. The devices are equipped with
▪ 2 x 10/100Base T(X) ports (LAN /WAN)
▪ 1 x WLAN interface (IEEE 802.11 b/g/n)
▪ 1 x Serial interface (RS232/422/485)
▪ 1 x LTE/4G CAT4 modem (Models IE-SR-2TX-WL-4G-EU and IE-SR-2TX-WL-4G-US-V)
− Model IE-SR-2TX-WL-4G-EU covers bands LTE-FDD:B1/B3/B7/B8/B20/B28A, LTE-TDD:B38/B40/B41, WCDMA:B1/B8 and
GSM:B3/B8. It is primarly intended for use in region EMEA.
− Model IE-SR-2TX-WL-4G-US-V covers bands LTE-FDD:B2/B4/B5/B12/B13/B14/B66/B71 and WCDMA:B2/B4/B5. It is applicable
for mobile operators of region North America. Additionally, it is certified by cellphone provider Verizon.
IE-SR-2TX-WL
The devices can be used in a variety of applications like IP-Routing, Firewalling, IP address management (NAT), secured VPN connections or
Ethernet/Serial data conversion.
2. Overview Hardware (1 / 3)
2.1 Panel Views
IE-SR-2TX-WL-4G-EU
IE-SR-2TX-WL IE-SR-2TX-WL-4G-US-V Item Descriptions
Front Panel View Front Panel View
1. 4-Pin Terminal block power input PWR1 / PWR2
2. Grounding screw / Frame ground (Note: The shielding ground of LAN
and WAN port is electrically connected to the grounding screw)
3. PoE Indicator (powered via PoE)
4. Power input LEDs (PWR1 / PWR2)
5. LAN port Link/Activity LED
6. WAN port Link/Activity LED
7. WLAN Link/Activity LED
8. LTE/4G Connection Status LED (only LTE/4G models)
9. Digital I/O ports Status LEDs (ON/OFF)
10. WLAN antenna connector (RP-SMA female)
11. Terminal block for Digital Input and Output
12. Reset Button
Pressing < 5 seconds: Reboots the device (Warm Start) and sets IP
of LAN port to Factory Default IP.
Top Panel View Rear Panel View Pressing >= 5 seconds: Resets the device completely to factory
default settings.
13. WAN Port 10/100Base-T(X)
14. LAN port 10/100Base-T(X) / PoE (Powered Device)
15. Serial Port (RS 232 connector)
16. LEDs TX/RX Status of Serial Port
17. Article Number
18. Slot for 2 SIM Cards with format Mini SIM (only LTE/4G models)
19. Main Antenna LTE/4G Interface (SMA-female)
20. AUX Antenna LTE/4G Interface (SMA-female)
21. DIN-rail Clip
2. Overview Hardware (2 / 3)
Product Properties LED Indicators
2.2 Technical Specifications
2. Overview Hardware (3 / 3)
2.3 Wiring and SIM Card installation
Power Wiring Wiring Digital Input and Output SIM Card Installation (only for 4G models)
Note: For using SIM cards with format Nano or Micro use a
Attention: For device installation and for safety notice refer to document ‘Hardware
frame from attached SIM card adapter set.
Installation Guide’ for Router series IE-SR-2TX-WL-xx (Part No. 2682560000,
2682580000, 2682590000).
The document can be downloaded from the Weidmüller Online Product Catalogue.
Select or search for device name IE-SR-2TX-WL or part numbers and refer to
section ‘Downloads’.
3. Getting Started
3.1 Hardware Installation 3.4 Web Interface Access
▪ Install and power-up the device according to ‘Hardware Installation Guide’ for Router series ▪ By factory default, the Router only can be accessed via the HTTPS-secured web interface
IE-SR-2TX-WL-xx (downloadable from Weidmüller Online Product Catalogue). and being connected to the wired LAN Port. All other access modes (HTTP, Telnet, SSH)
▪ Consider the safety notices mentioned in the Hardware Installation Guide! and any access from other interfaces are not allowed by default. Granting additional access
modes can be configured via section ‘Access Settings’ of configuration page ‘Administration
→ System Settings.
3.2 Factory Default Settings
▪ Factory Default Settings:
▪ Login credentials (Factory default settings):
▪ IP LAN port: 192.168.1.110 / 255.255.255.0 (static) ▪ IP address / Netmask: 192.168.1.110 / 255.255.255.0
▪ IP WAN port: DHCP ▪ Username: admin
▪ Wireless LAN: Disabled ▪ Password: Weidmueller
▪ Mobile Interface: Disabled (only available for LTE/4G models) ▪ Connect the PC to the Ethernet port of the Converter/Gateway and set the PC’s IP address
▪ Username: admin to a free one of range 192.168.1.0 / 255.255.255.0.
▪ Password: Weidmueller ▪ Start a web browser and enter the IP address of the connected device into the browser’s
▪ Web Access: HTTPS via LAN port address line (https://192.168.1.110).
▪ After the appearance of the prompt (login) enter the login credentials. After successful input
3.3 General Device Access and Configuration of username and password home page ‘System Overview’ will be displayed.
▪ IE-SR-2TX-WL-xx devices needs to be configured via the configuration pages of the
Note: If the Router configuration is set to factory defaults, any HTTP access attempt to the
integrated Web server.
website (via LAN port) will be redirected automatically to HTTPS.
▪ For Linux respectively OpenWRT-skilled users the Router additionally can be released for
low-level root access via SSH or Telnet by enabling related checkboxes in section ‘Access
3.5 Console Access via Telnet or SSH
Settings’ of configuration page ‘Administration → System Settings’ (Goto chapter ‘4.36 ▪ The device root level can be accessed by Telnet or SSH console login (eg. using tool
Administration → System Settings’ for more detailed information). PuTTY). Use for access user 'root' and same password as set for user 'admin’.
▪ For using the Serial-to-Ethernet converter function ‘Virtual Com Port’, applicable to the
RS232/485 interface, the software ‘ComServer / Modbus Gateway Utility’ can be used to Note: When doing a device access at root level of the Linux operating system, be aware that
install a virtual COM-Port driver on a Windows PC as counterpart to the Router configuration changes can have a severe impact on the functionality of the running
(downloadable from the Weidmüller Online Product Catalogue). Router application (configured via the web interface). Any change is in the user’s
responsibility and risk if the web-based Router application fails due to the intervention.
For recovering the designed functionality based on the installed firmware reset the device
to factory default settings (e.g., press external reset button larger 5 secs).
▪ Subsequent slides provide a detailed description about the menu structure and configuration
pages of the Router’s Web interface in terms of functional settings and parameter definitions.
Note: This behavior (Apply without saving parallel saving to Flash memory) can be very helpful in case
of applying an incorrect configuration which can result, for example, in an access blocking to the
Picture 1: Login page
Router. By reboot via power down and up, the last saved configuration will be active again not
having the applied misconfiguration.
Default Gateway:
Can be configured if both interfaces LAN and WAN port are set to static IP assignment. If at least one of
both interfaces is set to DHCP then this parameter is locked because default gateway will be retrieved by
DHCP.
DNS:
Used for configuration of DNS settings. Two static DNS servers can be configured, additional to a DNS
entry retrieved by an interface with DHCP-based IP assignment.
Consider: Ensure that the Router's DHCP Server function is enabled and properly configured (Menu Network Service →
DHCP → DHCP Service). If DHCP service is not configured, the WLAN clients connect to the 'Access Point'
but do not get any IP address assignment.
Consider: It is highly recommended to activate 'Masquerading (NAT)' for the WLAN interface. This ensures that
responses of outgoing traffic - initiated from LAN side - can be routed back to LAN devices without setting any
routes in the associated 'Access Point'.
Note: If mode 'Wireless Client' will be applied, then this mode immediately becomes the current Internet/WAN
connection. The previously selected interface ('WAN Port' or 'Mobile Interface' for LTE/4G models) will be
replaced automatically. This behavior is caused by technical design.
Picture 12: Wireless LAN factory default settings (disabled) Picture 14: Example of operation mode ‘Wireless Client’
2022-11-25 / Edition 1.0 Page 15
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
Advanced WLAN Settings (valid for operating modes ‘Access Point’ and ‘Wireless Client’)
A beacon is a broadcast packet sent by the 'Access Point' to synchronize wireless
devices. The beacon interval value defines the frequency interval how often the beacon
Beacon Interval is broadcast by the Router. Increasing this value reduces the number of beacons and the
overhead associated with synchronization process. The default value is 100, but 50 is
recommended for a reception.
This value indicates the interval of the Delivery Traffic Indication Message (DTIM). A
DTIM field is a countdown Message (DTIM) informing clients about the next window for
listening to broadcast and multicast messages. When the ‘Access Point’ has buffered
DTIM Period broadcast or multicast messages for associated clients, it sends the next DTIM with a
DTIM Interval value. The associated clients hear the beacons and awaken to receive the
broadcast and multicast messages.
The factory default value is 2 milliseconds (Range: 1 to 255 msecs).
The value specifies the maximum size of a packet before it is fragmented into multiple
ones. It ranges from packet size 256 bytes up to 2346, it is recommended to remain at
Fragmentation
the default size of 2346 bytes. If you experience a high packet error rate, you may slightly
Threshold
decrease the value. Setting the value too low may result in poor network performance.
Only minor modifications of this value are recommended..
The RTS (Request to Send) threshold is the amount of time a wireless device,
Picture 15: Factory default settings of advanced wireless parameters
attempting to send, will wait for a recipient to acknowledge that it is ready. Normally, an
access point sends a RTS frame to a station and negotiates the sending of data. After
receiving RTS frame, the station responds with a CTS (Clear to Send) frame to When doing a wireless transmission, RF signals can reach the receiving antenna by two or
RTS Threshold
acknowledge the right to begin transmission. To ensure communication, the maximum more paths resulting in an interference and degradation of the signal. Parameter 'Guard
value should be used, which is the default value 2347 (Range: 0 to 2347 bytes). If a Interval' is intended to avoid signal loss from multipath effect, the value can be set to 'short' or
network packet is smaller than the preset RTS threshold size, the RTS/CTS mechanism HT Guard Interval 'long'. By default, a short 'HT Guard Interval' is active, it can increase the data rate by roughly
will not be enabled. 10%.
This parameter allows you to change the power output level. Default value is 12 dBm Note: This parameter is only valid for wireless standard 802.11n (HT is equivalent to 802.11n
(Range: 3 dBm to 20 dBm). A 'Maximum Transmission Power' value of 12 dBm (around and means High Throughput).
Maximum
60% of maximum) is probably suitable for most user applications. Higher power settings
Transmission Power Specific Client Mode Settings
are not recommended for users due to excess heat generated by the radio chipset, which
can affect the life of the device. For operation mode 'Wireless Client' parameter 'X-Roaming' can be enabled to shorten the time
Two different preamble types (long or short) can be selected. A long preamble uses X-Roaming for handover from a connected access point to another one.
additional data header strings to check data transmission errors. A short preamble is This feature is disabled by default.
faster because it adds less data when checking transmission errors. If 'X-Roaming' is enabled, this parameter determines when to start looking for new access point
Preamble
Default setting is a short preamble enabling an increased overall throughput. However, if Signal Threshold for candidates. If the current connection quality (Signal Strength) is lower than the specified
any wireless device does not support short preamble, then it will not be able to Roaming threshold, the Router will start background scanning and look for the next-hop candidate.
communicate within the wireless network. In this case select a long preamble. Default signal threshold for roaming is 55 dBm (Range: -40 to -65 dBm).
2022-11-25 / Edition 1.0 Page 16
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
If MAC Filter is enabled, WLAN client connections either are allowed or rejected dependent on
the selected policy and if being a member of the MAC filter table.
Consider:
1. Function 'Add associated client' can be used for an easy MAC address takeover of already connected clients
into the MAC filter table. The preferred method is to do this as long the Router is running with disabled MAC
Filter because only this status lists connected clients (still not controlled by MAC filter) in the drop-down
selection box for take-over (Copy to).
2. When starting to configure, first set parameter ‘MAC Filter’ to enabled. Next select an associated client and then
select the table slot (Number 1 to 32) via the drop-down list box. When clicking on the desired table slot, the
MAC address automatically will be copied to the MAC filter table.
3. Please keep in mind that this method only is reasonable for policy setting 'Only allow MAC address(es) listed in
filter table to connect to AP'. Otherwise, already connected clients which just have been added to the MAC filter
table, will be rejected for access immediately if the configuration will be applied.
2022-11-25 / Edition 1.0 Page 17
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
Selection of the network interface (connection type) to be used for Internet/WAN connection.
Via this configuration page the connectivity to the Internet or to an upper-level network (WAN) will
be defined.
By factory default the RJ45 WAN port is selected as the active Internet / WAN connection.
2. Interfaces 'Mobile Interface’ or 'Wireless Client' cannot be selected for the Internet / WAN
connection as long the interface is not enabled or not yet configured (Error message is
displayed). Before selection, you need to enable and configure the desired interface in
section 'Interface Configuration' to be useable for Internet / WAN connectivity.
3. If WLAN interface (Mode ‘Wireless Client’) will be configured (Menu Interface Configuration
→ Wireless LAN → Operation Mode), then after applying mode ‘Wireless Client’
immediately and automatically becomes the active Internet/WAN connection (replacing Picture 18: Example of an established Internet / WAN connection via ‘Mobile Interface’.
previous setting ‘WAN Port’ or ‘Mobile Interface’). This is caused by technical design.
4. 'Mobile Interface' can be configured independent of the selected interface for Internet / WAN
Selectable combinations for Internet / WAN connectivity:
connection and needs to be set as active Internet / WAN connection explicitly.
Primary connection Configurable Fallback Connection Restrictions / Limitations / Impact
WAN Port (wired) Mobile Interface (Active SIM profile) WLAN can only be used in mode Access Point.
5. If either 'Wireless Client' or 'Mobile Interface' is selected for Internet / WAN connectivity, then
the wired WAN port either is disabled or can be configured as additional (switched) LAN port. Connecting clients will be assigned to LAN network.
In this condition the WAN port related configuration parameters (Interface Configuration → WLAN Interface (Mode Wireless Mobile Interface (Active SIM profile) WAN port (wired) either disabled or useable as
LAN/WAN Port) are locked. If WAN port shall be used again for Internet / WAN connectivity, Client) additional LAN port.
then select 'WAN Port' as active Internet / WAN connection. Mobile Interface (Active SIM Mobile Interface (Backup SIM profile) WAN port (wired) either disabled or useable as
profile) additional LAN port.
Examples of selection of a network interface (connection type) to be used for Internet / WAN connection.
Selectable connection
types
Picture 21: Example of WLAN interface (Mode ‘Wireless Client’) selected for Internet / WAN
connection. No connection failover to ‘Mobile Interface’ (Backup) configured.
Picture 19: Example of WAN Port selected for Internet / WAN connection. No connection failover to
‘Mobile Interface’ (Backup) configured.
Picture 22: Example of mobile interface selected for Internet / WAN connection and currently connected (Online)
to the operator via profile ‘SIM 1’.
Note: If - for example - profile ‘SIM 2’ also is activated and configured for failover (backup), then in
Picture 20: Example of WAN Port selected for Internet / WAN connection. ‘Mobile Interface’ is case of a connection changeover profile ‘SIM 2’ would be displayed here as active connection.
configured as failover connection (Backup).
The 'Default Routing Table' lists the default network routes based on the active
router interfaces.
Via the “Static Routing Table” additional routes can be configured manually. A static
route will become active immediately after adding and applying. Several static
routes can be added before clicking 'Apply' button to activate them.
The default metric for static routes is zero (0) having the highest priority. If
necessary for any reason, change the metric to a higher value to decrease the
priority of this entry.
Picture 23: Example of routing entries for an Internet / WAN connection via WLAN Interface (Operation mode
‘Wireless Client’)
Picture 24: Example of routing entries for an Internet / WAN connection via Mobile Interface (4G/LTE modem)
and one additionally configured static route.
DHCP Server
Provides IP data assignment for DHCP clients when connecting to the LAN
interface. The DHCP service operates on the wired LAN port and for connecting
WLAN clients if the Router’s WLAN interface is running in operation mode ‘Access
Point’.
IP address data for DHCP clients will be assigned according to the configurable
Picture 25: Example for disabled DHCP service
parameters, for Gateway and DNS current Router settings will be provided to
clients.
DHCP Relay
In this mode the Router acts as a gateway between a requesting DHCP client at
LAN side (wired LAN port or WLAN Client) and a remote DHCP server accessible
by the configured ‘Target DHCP Server IP’.
2022-11-25 / Edition 1.0 Picture 27: Example for an enabled DHCP relay service Page 22
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
Listed DHCP clients either are devices connected to the wired LAN port or WLAN
clients (also members of the LAN network) if the Router is configured running
operation mode 'Access Point'.
Picture 28: Example showing 2 DHCP clients which have been received IP data from the Router’s DHCP service.
Note: Currently the Router only supports provider 'DynDNS.org' for dynamic DNS
service. Prerequisite for using this function is having an existing account at
'DynDNS.org'.
Picture 30: Enabled Dynamic DNS. Currently only provider ‘DynDNS.org’ is supported.
Note: The Router is equipped with an internal clock (not battery buffered) which needs to be
set when powered-up or rebooted to show correct date and time values. At power-up
or if the Router will be rebooted, the system time always starts with date 01 January
2022 and time 00:00:00 plus offset (from UTC) related to the configured time zone.
Note: Button 'Set System Time' updates the system time exactly according to the input
fields. The setting of the time zone will not be considered.
For manual date / time setting it is recommended to select first the right time zone,
then click button Apply, then click button 'Get Browser Data' and finally click “Set
System Time’.
Note: If the time zone has been changed and button 'Apply' will be clicked, then the system
time will be adapted with the offset between previous and selected time zone.
For example, typical applications for definitions of ‘Local Access’ rules can be:
- Allow access to the Web interface only for specific IP addresses.
- Allow use of Ethernet/Serial converter functions only for specific (source) IP
addresses.
Note: Rules for device access like Web interface access via HTTP(S), Telnet,
SSH Console or Ping to WAN port IP, do not need to be configured as
special local access rule. These access settings can be configured
easily via checkbox settings in configuration menu 'Administration →
System Settings'.
A DNAT rule replaces the original target data of an incoming IP packet (Destination
IP and Destination Port) by a new IP address / Port of the rule that it can be
forwarded to the device having the replaced IP address.
A well known SNAT rule is 'Masquerading (NAT)' which replaces the source IP
of any outgoing IP packet by the outgoing interface IP hiding the original
sender. It can be enabled/disabled when configuring the interface settings
(checkbox 'Masquerade (NAT)' in menu 'Interface Configuration → LAN/WAN
Port').
Add / Edit a Source NAT rule Picture 36: Source NAT configuration window (default settings).
This section is used to create / adapt specific SNAT rules for outgoing packets
Hint about configuration of a '1:1 NAT' application (hiding LAN IP addresses completely with virtual ‘public’ IP):
with definition of filter criteria, on which packets the rules shall be applied and
1:1 NAT means that IP addresses of a local (LAN) network will be substituted (hidden) by virtual IP addresses
how the IP source data shall be changed. In case of matching the rule criteria that only these addresses will be used for bidirectional communication with (public) WAN devices and it doesn't
the ‘Source IP’ and possibly the ‘Destination Port’ of the passing packet will be matter who starts the TCP/IP communication. Effectively ‘1:1 NAT’ is a combination of one SNAT and one
replaced with the specified data (SNAT IP / Port for a host respectively SNAT DNAT rule. The SNAT rule replaces the (real) source IP by the virtual IP when the packet exits the Router
IP/ Netmask for a subnet). interface, the DNAT rule forwards an incoming packet addressed to the virtual IP to the LAN device with real
IP. But only one will be applied at time dependent who initiates the TCP/IP communication (from LAN or WAN
Active SNAT Table side). After establishing a new TCP connection either via a SNAT rule for outgoing from a LAN device or via
This table contains the defined Source NAT rules. Active rules will be checked DNAT incoming from the WAN side a bidirectional communication via the TCP connection always can be done Application hint:
from top to bottom. If a rule matches, the original source IP data will be due to stateful firewall behavior.
For more detailed information
replaced by the specified SNAT IP, and the rule check will be canceled how to use DNAT and SNAT
Notes: If a TCP/IP communication always and only will be initiated by private LAN device – for example
immediately. The IP packet remains untouched if no rule criterion applies. features please refer to
requesting any data from WAN sided device(s) - then only the SNAT rule needs to be configured to
appear with virtual (public) IP addresses at WAN side. If the TCP connection has been established a appendix A1 (Network
Note: SNAT rules will be applied (as last action) immediately before the IP bidirectional communication via the TCP socket is possible due to stateful firewall behavior. In this case Address Translation: Use
packet exits an interface. Firewall rules defined in IP Filter (Local there is no need to configure any related DNAT rule. cases and how to configure
Access) and IP Filter (Forwarding) applies before processing SNAT. If a TCP/IP communication also needs to be initiated by a public WAN device addressing the virtual IP of Source NAT and Destination
the LAN device, then the appropriate DNAT rule must be configured additionally . NAT).
The configuration for both instances can be done either via predefined
selection fields or by entering the well-known OpenVPN options directly
into a text input mask.
If checkbox ‘Configure via OpenVPN options’ is disabled, the server configuration can be done
by entering data and/or value selection of the predefined fields.
Connection Type
Selection of one of three predefined connection types how an OpenVPN client can connect to
the Router (being the OpenVPN server).
• Bridged Ethernet Connection Picture 41: Webpage showing tab ‘Server’ with activated
This mode allows connecting OpenVPN clients becoming a member of the Routers LAN checkbox for configuration via direct input of
OpenVPN options.
network like being directly connected to the Router LAN port. The bridging mode uses
interface type ‘TAP’ providing a secured Ethernet-based connection at Layer 2. For Picture 40: OpenVPN webpage showing tab ‘Server’
communication with devices connected at Router LAN port a ‘bridged’ client must have (Configuration via predefined OpenVPN parameters).
an IP of the Router LAN subnet. Note, that via a bridged connection also any broadcast
traffic will be transferred like in a switching network. Notes:
- For selection of necessary certificate files (CA, Server, Key) when doing a configuration via predefined
Other listed (predefined) OpenVPN options (for data input or drop-down selection) parameters (left picture), the files must be uploaded before selecting via menu VPN → Files / Certificates.
When selecting a ‘Connection Type’ some values of the parameter list (options) will be set - For referencing of any entered file names when configuring via text-based input mask (right picture) those
automatically. Most of these settings are intended to be a proposal. They can be adapted as files needs to be uploaded via menu VPN → Files / Certificates either in /etc/certs-keys or directory
needed for the application. Only options ‘Interface Type’ and ‘Authentication’ do have a fixed /etc/files before applying.
assignment related to the selectable connection types. - After applying of the configured settings, the resulting OpenVPN options can be checked via button ‘Show
Config file’”.
2022-11-25 / Edition 1.0 Page 32
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
If checkbox ‘Configure via OpenVPN options’ is disabled, the client configuration can be done
by entering data and/or value selection of the predefined fields.
Connection Type
Selection of one of three predefined connection types how the Router - being an OpenVPN
client - can connect to a remote OpenVPN server.
• Routed Point-to-Point Connection:
This connection type is intended to establish a simple peer-to-peer VPN connection
between two devices using predefined (but changeable) parameters. In terms of security
a static key file or a certificate-based SSL/TLS authentication can be used. This
connection type uses default OpenVPN topology ‘Net30’ also suitable for a peer-to-peer
connection to a Windows-based OpenVPN server.
Other listed (predefined) OpenVPN options (for data input or drop-down selection) Notes:
When selecting a ‘Connection Type’ some values of the parameter list (options) will be set - For selection of necessary certificate files (CA, Client, Key) when doing a configuration via predefined parameters (left picture),
automatically. Most of these settings are intended to be a proposal. They can be adapted as the files must be uploaded before selecting via menu VPN → Files / Certificates.
needed for the application. Only options ‘Interface Type’ and ‘Authentication’ do have a fixed - For referencing of any entered file names when configuring via text-based input mask (right picture) those files needs to be
assignment related to the selectable connection types. uploaded via menu VPN → Files / Certificates either in /etc/certs-keys or directory /etc/files before applying.
- After applying of the configured settings, the resulting OpenVPN options can be checked via button ‘Show Config file’”.
Additionally, this page provides information about the connection status and the OpenVPN log..
Notes:
- A defined instance behavior only works if the client or server instance is configured and enabled.
- Both windows ‘Connection Status’ and ‘OpenVPN Log’ provide information about OpenVPN instance
status. If no status and log data is displayed, which can happen if the OpenVPN instance cannot be
started due to a severe misconfiguration. In this case, please check ‘System Log’ for any OpenVPN
related message. Picture 45: Selectable instance behaviors for a
client and server instance.
Picture 46: Information windows that IPsec currently is still under construction.
Via this section certificate and key files can be uploaded to be used for
OpenVPN and IPsec applications. Each file which is uploaded to this directory
(/etc/certs-keys), can be selected when configuring any file-related OpenVPN
or IPsec parameter providing a drop-down selection.
This directory can be helpful to upload files to be used for individual OpenVPN
applications which are configured by the text-based input (same as for an
OpenVPN config file) and having any file references. For example, this file
directory can be used as CCD directory containing the client specific files if the
Router is running as OpenVPN server with ‘client-config-dir’ option (client-
config-dir /etc/files).
Picture 47: Example screenshot, showing uploaded certificate and key files in the upper section. Lower section ‘Other Files’ contains VPN
client configuration files to be used if the Router is running as OpenVPN server and refers via option client-config-dir /etc/files to
files Client1, Client2 and Client3 (being the common names of connecting clients).
These modes will be configured on webpage 'Serial Port Settings → Service Mode'.
Parameter Settings
General hint: If the serial interface is not used for the application, it is recommended to disable the port (via
parameter 'Serial Port') to release some CPU resources.
If necessary, the behavior of data processing and buffering can be adapted for
Serial-to-Ethernet data transmission using parameters
• 'Force TX Interval Time’,
• 'Delimiter' characters and
• 'Flush Data Buffer After’.
4.28 Serial Port Settings → Data Processing → Behavior of Serial-to-Ethernet interface data flow (2 / 3)
Generally, the overall data flow from receiving data at serial interface (Port 1) and sending out to the Ethernet
interface depends on parameters
- Delimiter (Byte value) [1]
- S2E Flush Data Buffer After (Timer) [2 refer to picture]
- Force TX Interval Time (Timer) [3]
which control the behavior of Serial-to-Ethernet-Input-Buffer [1 2] and Transmit-to-Ethernet-Output-Buffer [3].
Behavior of Serial-to-Ethernet-Input-Buffer:
If Delimiter byte(s) are set to 00 then input buffering always is disabled independent of setting of timer
parameter “S2E Flush Data Buffer After“. In this case each incoming byte from serial port will be forwarded
immediately to the Transmit Buffer.
Note: If Delimiter(s) shall be applied then always use first Delimiter 1 (being not 00) followed by Delimiter 2, 3
or 4 if necessary.
If Delimiter byte(s) do have a value other than 00 AND ‘S2E Flush Data Buffer After‘ is set to 0 (ms), then Picture 50: Parameters to be used for Serial-to-Ethernet data transmission.
incoming bytes will be buffered as long as no Delimiter(s) will be received and match. If the delimiter condition
match or if the buffer is full (4 kBytes) then data of input buffer will be forwarded to Transmit Buffer.
If Delimiter byte(s) do have a value other than 00 AND “S2E Flush Data Buffer After“ is set > 0 (ms) then
incoming bytes will be buffered as long
- delimiter settings do not match or 1 3
- elapsed time since first received byte < defined “S2E Flush Data Buffer After“ time. 2
If one of the conditions triggers, then the buffer content will be forwarded to transmit buffer immediately.
Note: Timer parameter ‚S2E Flush Data Buffer After‘ only can be used in combination with delimiter settings. If
Delimiter byte(s) are set to 00 (disabled) then ‚S2E Flush Data Buffer After‘ does not have any effect.
Independent of parameter settings the data always will be forwarded if the buffer is full (4kByte).
Behavior of Transmit Buffer: Picture 51: Diagram of data processing and buffering for a Serial-to-Ethernet data transmission.
If timer parameter ‚Force TX Interval Time‘ is set to 0, then output buffering is disabled. Each incoming byte or
byte block received from S2E Input Buffer will be sent out immediately as an IP packet via Ethernet interface.
Note: Parameter ‘Force TX Interval Time‘ can be used to increase the payload of an Ethernet
If ‚Force TX Interval Time‘ is set 0, then buffering is enabled. In this case the ComServer periodically sends frame by gathering more bytes of the serial input stream. But consider a possible impact on
out each defined ‘Force TX Interval Time‘ the content of the Transmit buffer as IP packet(s) via Ethernet timing requirements regarding the serial application behind the Ethernet side . Independent
interface. of this parameter the data always will be sent out if the buffer is full (4kByte).
2022-11-25 / Edition 1.0 Page 39
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
4.28 Serial Port Settings → Data Processing → Behavior of Serial-to-Ethernet interface data flow (3 / 3)
General the overall data flow from receiving the payload of an Ethernet frame and sending out at serial
interface (Port 1) depends on parameters
- Delimiter (Byte value) [1 refer to picture]
- S2E Flush Data Buffer After (Timer) [2]
which control the behavior of Ethernet-to-Serial-Input-Buffer.
Behavior of Ethernet-to-Serial-Input-Buffer:
If Delimiter byte(s) are set to 00 then input buffering always is disabled independent of setting of timer
parameter ‘E2S Flush Data Buffer After‘. In this case the payload of each incoming IP packet immediately
will be send to the serial interface.
Note: If Delimiter(s) shall be applied then always use first Delimiter 1 (being not 00) followed by Delimiter 2,
3 or 4 if necessary.
If Delimiter byte(s) do have a value other than 00 AND ‘E2S Flush Data Buffer After‘ is set to 0 (ms), then
the payload of incoming IP packet(s) will be buffered as long as no delimiter byte(s) will be received and
match. If the delimiter condition match or if the buffer is full (4 kBytes), then buffer data will be sent out at Picture 52: Parameters to be used for Ethernet-to-Serial data transmission.
serial interface.
If Delimiter byte(s) do have a value other than 00 AND ‘E2S Flush Data Buffer After‘ is set > 0 (ms), then the
payload of incoming IP packet(s) will be buffered as long
- the delimiter settings do not match or
- the elapsed time since first received byte/payload has not reached defined ‘E2S Flush Data Buffer
After‘ time.
If one of the conditions triggers, then the buffer content will be sent out at the serial interface immediately.
1
Note: Parameter ‚E2S Flush Data Buffer After‘ only can be used in combination with delimiter settings. If 2
Delimiter byte(s) are set to 00 (disabled) then ‘E2S Flush Data Buffer After‘ does not have any effect.
Independent of parameter settings the data always will be sent out if the buffer is full (4kByte).
Picture 53: Diagram of data processing and buffering for a Ethernet-to-Serial data transmission.
Notes:
- To run one of these service modes the serial port
generally needs to be enabled on webpage ‘Serial Picture 54: Service mode ‘Virtual Com Port’ (Factory Default)
Settings →Interface Configuration → Parameter
‘Serial Port’.
Description of parameter settings: Picture 58: Service mode ‘Virtual Com Port’ selected.
Disables or enables an SSL/TLS encrypted TCP/IP
Data Encryption communication between PC’s Virtual COM Port driver and the Note about connection between a Windows PC and the Router using service mode Virtual COM Port:
Router. • For installation of a virtual COM port driver on the Windows PC same software (Weidmueller CS-MBGW
Port number on which the Router exchanges the connection Utility, Version 3.4 and later) can be used which primarily is intended for Virtual Com Port communication
TCP Data Port
payload. between a Windows PC and Weidmueller ComServer/Modbus Gateway IE-CS-MBGW-2TX-1COM
Port number on which the Router is listening for communication
TCP Control Port (Article number 2682600000).
establishment and exchange of control data.
• When creating / mapping a virtual COM Port on the PC the software establishes - based on the
Disconnects established TCP/IP connection(s) after defined
configured communication parameters - a TCP connection to the Router.
Idle time (seconds) if there is no further data transmission on
Idle Timeout the serial interface (due to Inactivity). If Idle Timeout = 0
seconds the Router never will terminate a consisting TCP/IP General configuration hint:
connection.
• It is not necessary to define an interface explicitly on which the Router is listening for establishing a
The Router sends according to the defined interval time
virtual COM Port connection. The Router is accepting an incoming connection request having the
(seconds) periodically TCP alive check packages to the remote
Alive Check configured TCP Data and Control ports on each interface as long these TCP ports are not blocked by
host(s) to evaluate the TCP connection. If the TCP connection
is no longer alive, the connection will be closed. firewall rules.
Defines the maximum number of simultaneous TCP/IP host • For communication with a Virtual COM Port driver running on a remote PC, the configured TCP ports
Max Connections 'Data Port', 'Control Port' and 'Management Port' may not be blocked by any firewall rule.
connections.
• The 'Management Port’ – used for internal communication with tool 'Weidmueller CS-MBGW Utility’ - is
set to 600 and cannot be configured via the webpage.
Note: The behavior of data processing (Latency, Buffering, etc.) between the Routers
Ethernet and serial interface and vice versa can be adapted via parameters ‘Force
TX Interval Time’, ‘Delimiter’ and ‘Flush Data Buffer After’ in menu Serial Port
Setting → Data Processing.
In mode ‘TCP Client’ the Router establishes a TCP/IP connection to specified host(s)
(TCP Server) to exchange data with the connected serial device. Any incoming serial
data will be converted and sent as payload of a TCP packet to the defined TCP
Server(s). Up to 5 simultaneous connections are supported, allowing multiple hosts to
exchange data with the serial device.
Note: The behavior of data processing (Latency, Buffering, etc.) between Ethernet and
serial interface and vice versa can be adapted via parameters ‘Force TX Interval
Time’, ‘Delimiter’ and ‘Flush Data Buffer After’ in menu Serial Port Setting →
Data Processing.
In mode ‘UDP Server/Client’ the Router can act as UDP Client and UDP Server
simultaneously.
If mode ‘UDP Server’ is activated, the Router listens to incoming UDP packets at the
defined port and forwards the payload to the connected serial device.
If mode ‘UDP Client’ is activated, any incoming serial data will be sent as payload of an
UDP packet(s) to the defined Server range(s).
Note: The behavior of data processing (Latency, Buffering, etc.) between Ethernet and
serial interface and vice versa can be adapted via parameters ‘Force TX Interval
Time’, ‘Delimiter’ and ‘Flush Data Buffer After’ in menu Serial Port Setting → Data
Processing.
Selectable action
Digital Input → Status and Parameter settings
types for DI
Shows current input status. ON if digital input is powered from 5 to 30
Current State
VDC, OFF if not connected or for power input 0 to 2 VDC.
Selection of one of following actions triggered by a DI signal change
Select Action Type
from OFF to ON or vice versa.
- Disabled No action assigned to DI signal change
- Start / Stop Starts or Stops the OpenVPN Server process if configured and
OpenVPN Server enabled.
- Connect /
Establishes or cancels a VPN connection to a remote OpenVPN server
Disconnect
if the OpenVPN Client is configured and enabled.
OpenVPN Client
Note: If for DI an action is selected, and a trigger event is assigned but the associated action type
is neither configured nor enabled then a DI signal change does not have any effect. Selectable event
types for DO
Note: If for DO an event is selected but the trigger event is neither configured nor enabled then a
DO signal change never happens.
Event Types
The Router supports following event types triggering a mail delivery to the defined mail
receivers. The subject of an alert mail is same as the event naming except for DI/DO
events, for which an individual subject can be configured.
Event Types
The Router supports below listed event types triggering an SNMP trap to the defined
SNMP server. The trap message content is same as the event naming except for DI/DO
events, for which an individual message can be configured.
Notes: 1. Control messages - except the password - are not case sensitive.
2. Replace ‚password‘ with the configured password.
Attention: When doing a device access at root level of the Linux operating system, be aware that configuration
changes can have a severe impact on the functionality of the running Router application (configured
via the web interface). Any change is in the risk and responsibility of the user if the web-based
Router application fails due to the intervention. For recovering the designed functionality based on
the installed firmware reset the device to factory default settings (e.g., press external reset button
larger 5 secs).
Picture 71: Factory defaults of ‘System Settings’.
Section Admin Password Settings
Via this section a new password can be set for the administrative user account, currently being the
only available user account. For password change you need to confirm the current password Note:
before setting a new one. The checkboxes of section ‘Access Settings’ are related to specific firewall rules (IPtables Filter). If enabled, the
corresponding rules allow the action, if disabled it will be rejected. These rules are independent of the settings of default
Section System Logging filter policies ‘Input LAN’ and ‘Input WAN’ of configuration page ‘Firewall Settings → IP Filter (Local Access)’. Means, if
This section defines the logging level of the 'System Log' for diagnostic purposes. you allow a general access (Accept) via policies ‘Input LAN’ and ‘Input WAN’, for example you cannot access the Router
Additionally, the forwarding of system log data to a remote 'Syslog' server can be configured. as long the corresponding ‘access’ checkbox is not enabled.
By default, device model name with extension “cfg” is preset as backup file name. It
is reasonable to adapt the file name having a unique reference to the device from
which it will be exported. Pressing button ‘Export’ stores the backup file into the
browsers download directory.
Note: The backup file is saved in a binary format which is not readable.
Select the file for import to restore the configuration which originally was exported as
backup file.
After clicking button ‘Import Configuration’ the Router will be configured with content
of selected import file followed by a system reboot.
Picture 72: Application window for backup and restore of a configuration file.
The Router is equipped with two firmware storage sections. One contains the running
version the other section is used for firmware fallback if any error occurs during the
upload and update process.
In normal operation the running firmware will be saved for backup and the uploaded
firmware becomes the running one.
In case of any update problem then at reboot time the original version will be
reactivated again as the running version.
Note: If you have enabled checkbox 'Set factory defaults after upgrade', you need to
open a new browser window with factory default IP for web access if IP
address has been changed due to factory default settings..
Manual Reboot
Pressing button ‘Reboot Now’ reboots the device immediately (Warm Start).
Automatic Reboot
Click on button ‘Reset to factory defaults’ immediately initiates the reboot process of the
device coming-up with factory default settings. The duration until the device is ready
again is about 60 seconds.
Consider: After setting to factory defaults, the Router only can be accessed by HTTPS-
Picture 76: Application window for reset to factory default settings.
secured Web interface via the wired LAN Port. All other access modes
(HTTP, Telnet, SSH) and any access from other interfaces are not allowed by
default.
Note: Alternatively, the external reset button can be used for setting factory defaults.
Pressing < 5 seconds: Reboots the device (Warm Start) and sets IP of LAN
port to factory default IP.
Pressing >= 5 seconds: Resets the device completely to factory default settings.
Picture 77: After initiation of the reset process a time counter is displayed counting from 60 to 0 seconds.
Additionally, a beep signalizes that the reboot process almost has been finished and the device
becomes ready again.
2022-11-25 / Edition 1.0 Page 57
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
For evaluation enter IP address or a DNS host name and select the desired
network utility. After pressing ‘Apply’ button a window will be displayed showing the
result.
Note: Some diagnostic tests like 'TraceRoute' can take a longer time and cannot be
interrupted.
Applying any setting resulting in a difference between the running and the saved
configuration triggers the display of blue-colored message 'Configuration changed
and applied but not saved!’ below the headline, signalizing that the running
configuration still needs to be saved. The message disappears after clicking button
'Save Configuration to Device' indicating identical running and saved configurations.
Note: If the device will be rebooted or powered down and the message is still
displayed, then all applied but not saved changes will be lost at next start-up.
Picture 80: Example of notice display and status message that any change has been done and applied but not
saved to Flash memory.
Picture 81: Status message after saving the configuration to Flash memory. The blue-colored notice is disappeared.
2022-11-25 / Edition 1.0 Page 60
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A. Appendix
A1- Network Address Translation: Use cases and how to configure Source NAT and Destination NAT.
A1-1 Network Address Translation: Overview about NAT application types configurable by destination and source NAT rules (1 / 2)
1. Destination NAT Protocol / An IP packet – typically addressed to Routers (WAN) Interface IP – will be forwarded to a local (LAN) Access to a service of a local device (LAN) via Router’s “public”
Port (DNAT) device dependent on protocol and destination port. WAN interface IP. For example, access to a Modbus/TCP slave by
forwarding protocol TCP and port 502.
2. Destination NAT IP (DNAT) An IP packet - incoming at Routers WAN port and addressed to a “virtual” IP – will be forwarded to a
local (LAN) device based on protocol and destination port. Hiding a local host (LAN) by a virtual “public” IP. Can be applied for a
Each incoming IP packet (typically at WAN port) and having the configured virtual “public” IP as full host NAT (use of virtual IP for incoming and outgoing
destination IP, will be forwarded to the configured target IP (real device at LAN side). communication) in combination with NAT type “Source NAT IP/Port”
Consider: The sending device only can send a packet to the “virtual” IP via the Router’s interface, if (No. 6).
either the Router’s IP is the default gateway on the sending device, or if a route is configured on the
sender device that the “virtual” IP can be reached via the Router’s interface IP.
3. Destination NAT Alias IP An IP packet - addressed to an additionally created Router IP (WAN port Alias IP) - will be Easy access from outside network (WAN) to a local LAN host without
(DNAT) forwarded to a local (LAN) device based on protocol and destination port. Typically, as ‘Alias IP’ a having any knowledge of the LAN network. No routing information is
free (unused) IP of the WAN network will be configured which easily can be addressed from WAN necessary for WAN devices because they are addressing devices
devices resulting in accessing devices at Routers LAN port without having a route to the LAN network. which seem to be in their own IP subnet.
Effectively, the Router can have multiple IP addresses, the configured WAN port IP and virtual ‘Alias IPs’
to be used as forwarding IPs to real LAN devices. The additional ‘Alias IP’ will be defined and created as
part of the rule configuration.
Hiding a LAN subnet (private) by a virtual “public” IP range when
4. Destination NAT IP Subnet IP packets - incoming at Routers Interface and addressed to a “virtual” IP range – will be forwarded to accessed from outside network (WAN). Can be applied to setup a full
(NETMAP) an identical subnet of local (LAN) devices based on used protocol (Any, TCP or UDP). The behavior “1:1 NAT” (use virtual public IPs for communication instead of real
of this function is similar as “Destination NAT IP (No. 2)” but with the difference that using this DNAT LAN IPs) in combination with NAT type “Source NAT IP Subnet” (No.
type multiple IP addresses (subnet) can be defined for forwarding instead of a single host IP. 7) which replaces real source IP by the virtual “public“ IP for outgoing
traffic.
5. Destination NAT Alias IP IP packets - addressed to additionally created Router IPs (Alias IPs on WAN port) – will be
Subnet (NETMAP) forwarded to an identical subnet of local (LAN) devices based on used protocol (Any, TCP or UDP). Easy access from the outside network (WAN) to a local LAN IP
The behavior of this function is similar as “Destination NAT Alias IP (No. 3)” but with the difference that subnet (multiple devices) without having any knowledge of the LAN
using this DNAT type multiple IP addresses (subnet) can be created for forwarding instead of a single network (WAN devices do not need any routing information).
‘Alias IP’ when using NAT type “Destination NAT Alias IP (No. 3)”.
2022-11-25 / Edition 1.0 Page 63
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A1-1 Network address translation: Overview about NAT application types configurable by destination and source NAT rules (2 / 2)
6. Source NAT IP / Port (SNAT) Replacement of the source IP of a host by a virtual “public” IP when the host device (typically a LAN Hiding a private network device at LAN side by using the virtual
member) initiates an outgoing communication via the Router. When a host packet passes the Router, “public” IP for outside communication initiated by the private host.
the original source IP will be replaced by the configured IP of the SNAT rule when matching to defined
criteria. Can be used for a host 1:1 NAT in combination with NAT type
“Destination NAT IP” (No. 2). If both rules will be configured, the
virtual IP is used as source IP for outgoing traffic initiated by the
private LAN host as well as accessible destination IP if outside
network devices initiate a connection to the private LAN host .
7. Source NAT IP Subnet Replacement of the source IPs of a subnet (multiple devices) by a defined virtual “public” IP range Hiding a private subnet at LAN side by a virtual “public” IP range for
(NETMAP) (subnet). For any host (device) of the defined subnet the host source IP will be replaced for outgoing outside communication initiated by the private host (belonging to this
communication passing the Router. subnet).
Can be used for a subnet 1:1 NAT (both directions) in combination
with NAT type “Destination NAT Subnet” (No. 5).
• Destination NAT replaces the destination IP of an IP packet immediately when it arrives at a defined or any Router interface.
Any firewall rules applied to the IP packet when passing the Router will be done, if referred, to the new destination IP.
A1-2 Example of NAT type (1) ‘DNAT Protocol/Port’ → IP forwarding based on used protocol/port to a local (private) host via Router’s interface IP (1 / 3)
Task Condition Solution
• Control device (Modbus/TCP Master using Protocol TCP / Port • Gateway of control device is set to company router • Configure a DNAT rule on Router 1 that each incoming IP
502) ) shall have access to Modbus/TCP slaves Device 1.1 at (172.16.0.1). packet with destination IP 172.16.1.21 (Router‘s WAN IP) and
machine network 1 and Device 2.1 at machine network 2. • No routes can be configured on the control device to access having protocol TCP / Port 502 will be forwarded to LAN IP
Modbus Slave devices connected at Routers LAN side. 192.168.1.10.
• Configure a DNAT rule on Router 2 (WLAN) that each
incoming IP packet with destination IP 172.16.1.23 (Router‘s
WLAN IP) and having protocol TCP / Port 502 will be forwarded
to LAN IP 192.168.1.10.
Device 1.1 Device 1.2 Device 1.3 Device 2.1 Device 2.N
192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.10 192.168.1.nn
***
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
A1-2 Example of NAT type (1) ‘DNAT Protocol/Port’ → IP forwarding based on used protocol/port to a local (private) host via Router’s interface IP (2 / 3)
Configuration of rule „DNAT Protocol/Port” on Router 1 according to illustrated application.
Result: Modbus/TCP communication to Device 1.1 (real IP 192.168.1.10) can be established from WAN
network via Router‘s IP 172.16.1.21.
Each IP packet incoming at WAN interface with (Router‘s) destination IP 172.16.1.21, protocol TCP
and port number 502 will be forwarded to device with IP address 192.168.1.10.
A1-2 Example of NAT type (1) ‘DNAT Protocol/Port’ → IP forwarding based on used protocol/port to a local (private) host via Router’s interface IP (3 / 3)
Configuration of DNAT Rule on Router 2 (WLAN) according to illustrated application.
Result: Modbus/TCP communication to Device 2.1 (real IP 192.168.1.10) can be established from WAN
network via Router‘s IP 172.16.1.22.
Each IP packet incoming at WLAN interface with (Router‘s) destination IP 172.16.1.22, protocol TCP
and port number 502 to will be forwarded to device with IP address 192.168.1.10.
2022-11-25 / Edition 1.0 Page 67
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A1-3 Example of NAT type (2) ‘DNAT IP’ → IP forwarding (independent of used protocol/port) to a local (private) host via a virtual ‘public’ IP (1 / 3)
Task Condition Solution
• Control device shall have access to hidden • Devices 1.1 and 2.1, both having same IP • Configure a DNAT rule on Router 1 that each incoming packet with destination IP
(private) devices Device 1.1 at machine network address 192.168.1.10, must be accessible via 192.168.100.10 (any free unused IP) and independent of used ‚Protocol‘ and ‚Destination port‘
1 and Device 2.1 at machine network 2. unique IP addresses. will be forwarded to IP address 192.168.1.10 of the LAN network.
• Configure a DNAT rule on Router 2 that each incoming packet with destination IP
192.168.200.10 (any free unused IP) and independent of used ‚Protocol‘ and ‚Destination port‘
will be forwarded to IP address 192.168.1.10 of the LAN network.
Note: This use case requires 2 routes configured on the control device or needs any other routing
information that IP 192.168.100.10 is reachable via IP 172.16.1.21 and IP 192.168.200.10
accessible via IP 172.16.1.23.
Device 1.1 Device 1.2 Device 1.3 Device 2.1 Device 2.N
192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.10 192.168.1.nn
***
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
Machine network 1 192.168.1.0 / 255.255.255.0 Machine network 2 192.168.1.0 / 255.255.255.0
A1-3 Example of NAT type (2) ‘DNAT IP’ → IP forwarding (independent of used protocol/port) to a local (private) host via a virtual ‘public’ IP (2 / 3)
Configuration of rule „DNAT IP“ on Router 1 according to illustrated application.
Result: Device 1.1 (real IP 192.168.1.10) can be accessed from WAN network via IP 192.168.100.10.
Each IP packet incoming at WAN interface with destination IP 192.168.100.10 will be forwarded
independent of used protocol and port number to IP address 192.168.1.10.
A1-3 Example of NAT type (2) ‘DNAT IP’ → IP forwarding (independent of used protocol/port) to a local (private) host via a virtual ‘public’ IP (3 / 3)
Configuration of rule „DNAT IP“ on Router 2 (WLAN) according to illustrated application:
Result: Device 2.1 (real IP 192.168.1.10) can be accessed from WAN network via IP 192.168.200.10.
Each IP packet incoming at WLAN interface with destination IP 192.168.200.10 will be forwarded
independent of used protocol and port number to IP address 192.168.1.10.
A1-4 Example of NAT type (3) ‘DNAT Alias IP’ → IP Forwarding to local (private) host based on additional Router IP (Alias IP) (1 / 3)
Task Condition(s) Solution
• Control device shall request data from hidden • Gateway of control device is set to company • Configure first DNAT rule on Router 1 including creation of an (additional) Alias IP 172.16.1.31
(private) devices router (172.16.0.1). at WAN port that each incoming packet with destination IP 172.16.1.31 will be forwarded to LAN
o Device 1.1, Device 1.2 at machine network 1 • No routes can be configured on control device. IP 192.168.1.10, independent of used protocol‘ and (destination) port.
and • IP address range 172.16.1.30 to 40 is not used • Configure second DNAT rule on Router 1 including creation of an (additional) Alias IP
o Device 2.1 at machine network 2. inside of class B production network 172.16.1.0 172.16.1.32 at WAN port that each incoming packet with destination IP 172.16.1.32 will be
/ 16. forwarded to LAN IP 192.168.1.11, independent of used protocol‘ and (destination) port..
• Configure one DNAT rule on Router 2 including creation of an (additional) IP 172.16.1.33 at
WLAN interface that each incoming packet with destination IP 172.16.1.33 will be forwarded to
LAN IP 192.168.1.10, independent of used protocol‘ and (destination) port.
Device 1.1 Device 1.2 Device 1.3 Device 2.1 Device 2.N
192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.10 192.168.1.nn
***
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
Machine network 1 192.168.1.0 / 255.255.255.0 Machine network 2 192.168.1.0 / 255.255.255.0
A1-4 Example of NAT type (3) ‘DNAT Alias IP’ → IP Forwarding to local (private) host based on additional Router IP (Alias IP) (2 / 3)
Configuration of first rule type „DNAT Alias IP“ on Router 1 according to illustrated application:
Result: Device 1.1 (real IP 192.168.1.10) can be accessed from WAN network via additional Router IP 172.16.1.31.
Device 1.2 (real IP 192.168.1.11) can be accessed from WAN network via additional Router IP 172.16.1.32
No routing information is necessary for WAN devices because they can address these devices like being in their own IP subnet.
2022-11-25 / Edition 1.0 Page 72
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A1-4 Example of NAT type (3) ‘DNAT Alias IP’ → IP Forwarding to local (private) host based on additional Router IP (Alias IP) (3 / 3)
Configuration of rule type „DNAT Alias IP“ on Router 2 (WLAN) according to illustrated application:
Result: Device 1.1 (real IP 192.168.1.10) can be accessed from WAN network via additional Router‘s Alias IP 172.16.1.33 (assigned to
WLAN interface).
No routing information is necessary for WAN devices because this device can be addressed like being in their own IP subnet..
A1-5 Example of NAT type (4) ‘DNAT IP Subnet’ → IP subnet forwarding to a local (private) subnet via a virtual “public” IP range (1 / 3)
Task Condition(s) Solution
• Control device shall request data from hidden • Devices of networks 1 and 2 - partly having • Create a DNAT rule on Router 1 that each incoming packet with a destination IP of subnet
(private) devices same IP addresses - must be accessible via 192.168.100.8 / 29 (Range 192.168.100.9 - .14) and based on used protocol (Any, TCP or UDP)
− Device 1.1 (192.168.1.10), 1.2 unique IP addresses. will be forwarded to corresponding IP subnet 192.168.1.10 / 29 (IP addresses 192.168.1.9 - 14)
(192.168.1.11) and 1.3 (192.168.1.12) of of the LAN network.
machine network 1 and • Create a DNAT rule on Router 2 that each incoming packet with destination IP subnet
− all devices 2.1 to 2.N (192.168.1.1 to 253) 192.168.200.0 / 24 (Range 192.168.200.1 to 254) and based on used protocol (Any, TCP or
of machine network 2. UDP) will be forwarded to corresponding IP range 192.168.1.0 / 24 (Range 192.168.1.1 to 254)
of the LAN network .
Note: This use case requires 2 routes configured on the control device or needs any other routing
information that subnet 192.168.100.8 / 29 is reachable via WAN IP 172.16.1.21 and IP
192.168.200.0 / 24 is accessible via WAN IP 172.16.1.23.
Device 1.1 Device 1.2 Device 1.3 Device 2.1 Device 2.N
192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.1 192.168.1.253
***
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
Machine network 1 192.168.1.0 / 255.255.255.0 Machine network 2 192.168.1.0 / 255.255.255.0
A1-5 Example of NAT type (4) ‘DNAT IP Subnet’ → IP subnet forwarding to a local (private) subnet via a virtual “public” IP range (2 / 3)
Configuration of rule type „DNAT IP Subnet“ on Router 1 according to illustrated application:
Definition of criteria
for the incoming
packet that have to
match in order to be
forwarded.
Result: Device 1.1 (real IP 192.168.1.10) can be addressed from WAN network by virtual IP 192.168.100.10. Device 1.2 (real IP 192.168.1.11)
can be addressed from WAN network by virtual IP 192.168.100.11.
Device 1.3 (real IP 192.168.1.12) can be addressed from WAN network by virtual IP 192.168.100.12.
Note: WAN devices need a route information that IP addresses 192.168.100.10/11/12 are accessible via Router‘s WAN IP 172.16.1.21.
A1-5 Example of NAT type (4) ‘DNAT IP Subnet’ → IP subnet forwarding to a local (private) subnet via a virtual “public” IP range (3 / 3)
Configuration of rule type „DNAT IP Subnet“ on Router 2 (WLAN) according to illustrated application:
Result: Each device of machine network 2 with real IP 192.168.1.xx can be accessed from WAN network via corresponding virtual IP 192.168.200.xx.
Note: WAN devices need a route information that IP subnet 192.168.200.0 is accessible via Router‘s WAN IP 172.16.1.23.
A1-6 Example of NAT type (5) ‘DNAT Alias IP Subnet’ → Forwarding of IP packets - addressed to virtual Router Alias IPs - to a real IP subnet (1 / 2)
Task Condition(s) Solution
• Control device shall access units Device 49 to • Gateway of control device is set to company • Configure a DNAT rule on Router 1 including creation of Alias IPs of subnet 172.16.1.80 / 28 (IP
Device 62 of machine network 1. router (172.16.0.1). range 172.16.1.81 - 94) additional at WAN port that each incoming packet having a destination
• No routes can be configured on the control IP of this Alias IP subnet will be forwarded to the corresponding IP address of subnet
device to access Router‘s LAN network 192.168.1.48 / 28 inside of the LAN network.
devices.
• IP address range 172.16.1.80 to 172.16.1.99 is Note: This example scenario forwards IP packets independent of used protocol (Any, TCP or
not used inside of class B production network UDP) but can be configured as additional criterion if necessary. .
172.16.1.0 / 16.
A1-6 Example of NAT type (5) ‘DNAT Alias IP Subnet’ → Forwarding of IP packets - addressed to virtual Router Alias IPs - to a real IP subnet (2 / 2)
Configuration of rule type „DNAT Alias IP Subnet“ on Router 1 according to illustrated application:
Result: Device 49 (real IP 192.168.1.49) can be accessed from WAN network via Router‘s Alias IP 172.16.1.81.
Device 50 (real IP 192.168.1.50) can be accessed from WAN network via Router‘s Alias IP 172.16.1.82.
…
Device 62 (real IP 192.168.1.62) can be accessed from WAN network via Router‘s Alias IP 172.16.1.94.
A1-7 Example of NAT type (6) ‘SNAT IP Address’ → Hiding a (local) host IP by a virtual ‘public’ IP for outgoing traffic (1 / 4)
Task Condition(s) Solution
• Device 1.1, 1.2, 2.2 and Device • Due to network security • Create on Router 1 two SNAT rules that replaces for each outgoing IP packet (at WAN port) - having source IP 192.168.1.10 respectively
3.1 located at different machine reasons each device sending 192.168.1.11, protocol UDP and destination port 4000 - the source IP by 192.168.10.10 respectively IP 192.168.10.11 (any free unused
networks shall push any data to a data to the database server IPs). New IPs 192.168.10.10/11 will now become the „public“ IPs for communication with the addressed database server.
database server located in the shall be identified by a unique • Create on Router 2 an SNAT rule that replaces for each outgoing IP packet (at WAN port) - having source IP 192.168.1.11, protocol TCP
upper-level production network. IP address (for example for and destination port 4001 - the source IP by 192.168.10.12 (any free unused IP). If the TCP connection has been established, the
• Devices 1.1, 1.2 and 3.1 push evaluation by a Firewall in the replacement IP 192.168.10.12 becomes the „public“ IP for the bidirectional communication between the devices.
their data via protocol UDP / port communication path). • Create on Router 3 an SNAT rule that replaces for each outgoing IP packet (at WAN port) - having source IP 192.168.1.10, protocol UDP
4000. • For this reason, masquerading and destination port 4000 - the source IP by 192.168.10.13 (any free unused IP). If the TCP connection has been established, the
• Device 2.2 establishes a TCP / at WAN port of the Routers replacement IP 192.168.10.13 becomes the „public“ IP for the bidirectional communication between the devices.
4001 socket and sends its data may not be used.
via this connection type. Note: These rules - hiding private (local) IP addresses by virtual public IP addresses - only can be applied for outgoing communication
initiated by the LAN devices. If a local LAN device also shall be accessible via the configured virtual public IP - initiated from
external devices - an IP DNAT rule (No. 2) needs to be configured additionally which forwards incoming IP packets addressed to the
virtual public IP to the real device of the LAN network. Also consider that external devices need to have the routing information that
virtual IPs are accessible via the Router‘s WAN interface IP.
Device 1.1 Device 1.2 Device 1.3 Device 2.1 Device 2.2 Device 2.3 Device 3.1 Device N.N
192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.10 192.168.1.nn
***
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
Machine network 1 192.168.1.0 / 255.255.255.0 Machine network 2 192.168.1.0 / 255.255.255.0 Machine network 3 192.168.1.0 / 255.255.255.0
2022-11-25 / Edition 1.0 Page 79
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A1-7 Example of NAT type (6) ‘SNAT IP Address’ → Hiding a (local) host IP by a virtual ‘public’ IP for outgoing traffic (2 / 4)
Configuration of rule type „SNAT IP Address“ at Router 1 according to illustrated application:
Result: When Device 1.1 (real IP 192.168.1.10) sends any data using protocol UDP and port 4000 it will be identified by the receiver via IP address 192.168.10.10.
When Device 1.2 (real IP 192.168.1.11) sends any data using protocol UDP and port 4000 it will be identified by the receiver via IP address 192.168.10.11.
A1-7 Example of NAT type (6) ‘SNAT IP Address’ → Hiding a (local) host IP by a virtual ‘public’ IP for outgoing traffic (3 / 4)
Configuration of rule type „SNAT IP Address“ at Router 2 according to illustrated application:
Result: When Device 2.2 (real IP 192.168.1.11) initiates a TCP connection to any WAN device using port 4001 then it will be identified by the
counterpart of the TCP socket by IP address 192.168.10.12 allowing a bidrectional socket data exchange.
Consider: An addressed WAN device needs a route information that a request from IP 192.168.10.12 has to be replied via Router‘s WAN
IP 172.16.1.22.
A1-7 Example of NAT type (6) ‘SNAT IP Address’ → Hiding a (local) host IP by a virtual ‘public’ IP for outgoing traffic (4 / 4)
Configuration of rule type „SNAT IP Address“ at Router 3 (WLAN) according to illustrated application:
Result: When Device 3.1 (real IP 192.168.1.10) sends any data using protocol UDP and port 4000 it will be identified by the receiver via
IP address 192.168.10.13.
A1-8 Example of NAT type (7) ‘SNAT IP Subnet’ → Hiding a (local) IP subnet by a virtual “public” IP subnet for outgoing traffic (1 / 3)
Task Condition(s) Solution
• All devices of machine network 1 • Due to network security reasons • Configure an SNAT rule on Router 1 that replaces for each incoming IP packet at LAN port - having a source IP of subnet
(Class C) shall push any data to each device sending data to the 192.168.1.0/24 and protocol UDP - the source IP with corresponding IP of virtual public IP subnet 192.168.10.0 / 24. (any free unused
the database server located in the database server shall be IP range). Note: Subnet masks for replacing original source IPs to a new virtual IP range must be identical.
upper-level production network identified by a unique IP address • Configure an SNAT rule on Router 2 that replaces for an incoming IP packet at LAN port - having a source IP of subnet 192.168.1.0 /
via protocol UDP. (for example for evaluation by a 29 (IP range 192.168.1.1 to 1.6) and protocol TCP - the source IP with corresponding IP of subnet 192.168.11.0 / 29.
• Devices 2.2 to 2.6 of machine Firewall in between of the o Consider: For establishing a TCP connection initiated from a device of machine network 2 to the database server using the SNAT
network 2 (Class C) shall send communication path). rule, a route needs to be set on the database server that virtual IPs 192.168.11.1 to 192.168.11.6 are accessible via Router‘s WAN
their data to the database server • For this reason, masquerading IP 172.16.1.22.
via connection type TCP. (N:1 NAT) at WAN port of a Note: These rules - intended to hide private (local) IP addresses by virtual public IP addresses - only can be applied for an IP
Router may not be used. communication which is initated by a (local) LAN device. If an IP communication also shall be initiated from external devices by
addressing a configured virtual public IP, then an IP DNAT rule (No. 2) needs to be configured additionally which forwards
incoming IP packets - addressed to the virtual public IP - to the real device of the LAN network.
Device 1.1 Device 1.2 Device 1.250 Device 2.1 Device 2.2 Device 2.6 Device 2.7 Device 2.8
192.168.1.1 192.168.1.2 *** 192.168.1.250 192.168.1.1 192.168.1.2 *** 192.168.1.6 192.168.1.7 192.168.1.8
GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254 GW 192.168.1.254
Machine network 1 192.168.1.0 / 255.255.255.0 Machine network 2 192.168.1.0 / 255.255.255.0
A1-8 Example of NAT type (7) ‘SNAT IP Subnet’ → Hiding a (local) IP subnet by a virtual “public” IP subnet for outgoing traffic (2 / 3)
Configuration of rule type „SNAT IP Subnet“ at Router 1 according to illustrated application:
Result: For each device connected to LAN port the original source IP (any IP of subnet 192.168.1.0 / 24) will be replaced
by the corresponding „virtual“ IP of subnet 192.168.10.0 / 24 for outging IP packets sent by the LAN devices.
A1-8 Example of NAT type (7) ‘SNAT IP Subnet’ → Hiding a (local) IP subnet by a virtual “public” IP subnet for outgoing traffic (3 / 3)
Configuration of rule type „SNAT IP Subnet“ at Router 2 according to illustrated application:
Result: For outgoing IP packets sent by LAN devices of IP range 192.168.1.1 to 192.168.1.6 the original source IP will be replaced by the
corresponding „virtual“ IP of range 192.168.11.1 to 192.168.11.6.
Note: If one of these LAN devices initiates a TCP connection to an outside target device a route needs to be configured on the target device
that requests coming from a virtual IP of range 192.168.11.1 to 192.168.11.6 can be replied via Router‘s WAN IP 172.16.1.22.
2022-11-25 / Edition 1.0 Page 85
User Manual - Industrial Security Router IE-SR-2TX-WL(-4G-EU/-4G-US-V)
A1-9 Example of full 1:1 NAT applied for an IP subnet → Hiding a local IP subnet by a virtual ‘public’ IP subnet for any traffic with external devices (1 / 2)
Task Solution Result
• Control device shall request data from (private) devices of • Configure a DNAT rule on Router 1 that each incoming packet at WAN port with destination • Each device of the machine
machine network 1. The communication will be initiated by the IP of subnet 192.168.100.0 / 24 (Range 192.168.100.1 - 254) independent of used protocol network is accessible by its
control device, either via UDP or by establishing a TCP and port will be forwarded to corresponding IP of range 192.168.1.0 / 24 (Range 192.168.1.1 virtual (public) IP address
connection. - 254) of the LAN network. • Each machine network device is
• The database server is acting as passive device and will be • Configure an SNAT rule on Router 1 that replaces for each incoming IP packet at LAN port - identified by its virtual (public) IP
requested by machine network devices (communication having a source IP of subnet 192.168.1.0 / 24 - the source IP with corresponding IP of virtual for both communication
initiators), either via UDP or by establishing a TCP connection. public IP subnet 192.168.100.0 / 24. (any free unused IP range). Note: Subnet masks for directions.
• Due to future planned expansions – adding identical machines replacing original source IPs to a new virtual IP range must be identical. • The use of the DNAT/SNAT rule
having same device IP addresses – virtual IP addresses shall be combination allows the initiation
used for machine network devices for communication with the Note: For addressing the machine network devices via their virtual (public) IP addresses the of a communication from both
production network. This ensures, that after expansion realization control device must have configured a route that subnet 192.168.100.0 / 24 is reachable sides, the local LAN and outside
each device can be accessed and identified by a unique „virtual“ via WAN IP 172.16.1.21. WAN network.
IP address.
Router 1
WAN 172.16.1.21 / GW 172.16.0.1
Internet/WAN connection = WAN Port
DNAT IP Subnet (Rule type 4) SNAT IP subnet (Rule type 7)
Forwards IP packets incoming at WAN port Replaces for IP packets the source IP
with destination IP of subnet 192.168.100.0 / 24 if member of subnet 192.168.1.0 / 24 by
to LAN devices of subnet 192.168.1.0 / 24 . the corresponding IP of subnet 192.168.100.0 / 24
(Range 192.168.1.1-.254) when outgoing at WAN port.
(Any Protocol) (Any Protocol)
LAN
192.168.1.254
A1-9 Example of full 1:1 NAT applied for an IP subnet → Hiding a local IP subnet by a virtual ‘public’ IP subnet for any traffic with external devices (2 / 2)
Configuration of rule type „DNAT IP Subnet“ at Router 1 according to illustrated application:
Result: Each device of the machine network is accessible from outside by its
virtual (public) IP address and is identified by its virtual (public) IP for
communication initiated by the machine network device.
Configuration of rule type „SNAT IP Subnet“ at Router 1 according to illustrated application:
Note: If one of the LAN devices initiates a TCP connection to an outside target
device a route needs to be configured on the target device that requests
coming from an IP of subnet 192.168.100.0/24 can be replied via
Router‘s WAN IP 172.16.1.21.