APulsar Technologies

Boundary vs. LAN Industrial Firewalls Explained

christine — Thu, 10 Apr 2025 09:50:27 +0000

What Are They, When to Use Them, and How to Choose

Most people using personal computers have at least heard the word “firewall” in an IT context. For those not deeply familiar with cybersecurity, a firewall might seem like some mysterious tool running quietly in the background, magically protecting your PC from cyber threats. While this description contains some truth, the concept of a firewall is usually more nuanced—especially when it comes to industrial applications.

In this article, we’ll explore industrial firewalls step by step:

Step 1: Difference between hardware and software firewalls
Step 2: Difference between industrial and commercial hardware firewalls
Step 3: Difference between boundary and LAN industrial hardware firewalls
Step 4: Selection guide for MOXA industrial firewall types

Let’s begin our journey!

What Is a Network Firewall, and What’s the Difference Between Software and Hardware Versions?

A firewall, in general terms, is a network security system that monitors, filters, and controls incoming and outgoing network traffic based on predefined security rules. It functions as a barrier between trusted and untrusted networks. Imagine a cyber threat as a fire in an adjacent building, and your firewall as a fire-resistant wall — this visualization neatly explains the role of a firewall in cybersecurity.

In typical scenarios, a “trusted” network refers to internal networks (such as home or enterprise), while an “untrusted” network usually means the Internet. However, in more complex environments, such as industrial applications (factories or smart grids), even neighbouring local networks can pose threats. Thus, firewalls often act as barriers even between VLANs within a single internal network.

From a conceptual and functional standpoint, there is no fundamental difference between hardware and software firewall implementations; the distinction lies in their deployment. A software firewall is an application installed directly on your computer, typically running as a background service. A hardware firewall, by contrast, is a standalone physical device resembling an Ethernet switch or router.

In simple terms, a software firewall is ideal for individual computers or small groups of powerful computers since firewall applications can consume considerable computing resources.
In industrial environments, however, most devices aren’t traditional computers but rather network remote I/O, controllers, IoT gateways, and embedded systems with limited computational resources. For these environments, hardware firewalls are typically more practical and widely used. The reasons include:

Cost-efficiency and simplicity: Deploying one hardware firewall between a router and a large network of devices is far easier and more economical than installing dedicated software firewalls on every device.
Resource limitations: Most industrial devices simply can’t handle the computational demands of a firewall application, making external hardware solutions a necessity.

Since APulsar specialises in cybersecurity solutions for industrial applications, we will focus exclusively on hardware firewalls for the remainder of this article.

Difference Between Industrial and Commercial Hardware Firewalls

Previously, we mentioned that a firewall “monitors, filters, and controls incoming and outgoing network traffic based on predefined security rules.” These rules determine whether to permit or deny traffic based on criteria such as source and destination IP addresses, port numbers, and protocol types. More advanced firewalls can inspect packets deeply — up to the application layer (Layer 7 of the OSI model) — to perform filtering, threat detection, and policy enforcement at a granular level.

It would be misleading to claim that industrial-grade firewalls are inherently “better” than commercial firewalls. Both types often feature advanced capabilities like Deep Packet Inspection (DPI) and Intrusion Prevention Systems (IPS). However, industrial firewalls are designed with specialized cybersecurity functions specifically tailored for operational technology (OT) environments — functions that would be redundant in most commercial IT use cases.

As discussed in our article Defense-in-Depth Security Architecture, industrial firewalls such as those from MOXA provide capabilities like OT protocol inspection for Modbus, DNP3, IEC-104, and others. The ability to inspect the payloads of industrial protocols is critical in OT environments but unnecessary for typical IT infrastructure.

Industrial Protocol Support for DPI in MOXA Firewalls

Protocol	Vertical Market	Available Now
DNP3	Power/Water	✓
EtherNet/IP	Automation	✓
IEC 60870-5-104	Power/Water	✓
IEC 61850 MMS	Power	✓
MELSEC	Automation	✓
Modbus TCP	General	✓
Modbus UDP	General	✓
Omron FINS	Automation	✓
OPC UA	Automation	✓
Siemens S7 Comm.	Automation	✓
Siemens S7 Comm. Plus	Automation	✓

For the most up-to-date list of supported industrial protocols, please visit MOXA’s Network Security Appliance section on their official website.

Additionally, industrial firewalls like MOXA’s offer virtual patching — a feature that mitigates vulnerabilities directly at the firewall level without requiring updates to the protected devices behind it. This functionality is not always present in commercial firewalls. Furthermore, a specific product category like the “LAN firewall”, which we’ll explore later, doesn’t exist in the commercial firewall space at all.

Industrial firewalls also offer features like extended warranties, wide operating temperature ranges, resistance to dust and humidity, industry certifications, and support for DIN-rail mounting — all critical for industrial environments but unnecessary in most commercial settings. Additionally, MOXA’s firewalls feature simplified user interfaces tailored for OT engineers and integrate with centralized management platforms like MXsecurity, simplifying both deployment and compliance.

Difference Between Boundary and LAN Industrial Hardware Firewalls

Now that we understand the use and benefits of industrial hardware firewalls, we can move on to the two main categories MOXA offers: Boundary Firewalls and LAN Firewalls.

A boundary industrial firewall incorporates all the features mentioned earlier: IPS, DPI with OT-protocol support, and core functionalities like NAT. What distinguishes it is its placement and role. Boundary firewalls are deployed between private and public networks, or at the edge of internal zones. If your goal is to protect the network from external access or create a DMZ for secure data exchange, a boundary firewall is the right choice. Much of what we’ve covered in this article so far refers to boundary firewall functionality.

LAN firewalls, on the other hand, are where things get more interesting — and more unique to MOXA. These devices are designed to operate within a single subnet, which is not typical for traditional firewall deployments. LAN Firewalls are meant to safeguard important assets and clusters of field devices inside a control network, where traffic is exchanged over a single VLAN. One of their key benefits: they don’t require IP reconfiguration. You simply drop it into the network, and it’s good to go — almost plug-and-play.

For example, you can place one directly between two critical devices, or insert it just in front of a network switch inside a control cabinet — protecting field controllers, onboard AGVs, or other small groups of devices sharing that switch. But don’t be fooled by the simplicity: LAN firewalls still feature Deep Packet Inspection (DPI) and IPS/IDS, which are enabled by default. Sure, they don’t offer NAT or routing functions — but by now, you can probably guess why. Simply put, a LAN firewall is like a shepherd dog guarding a flock: you place it in the network segment, and it quietly watches over everything, ensuring nothing harmful slips through.

In this specific form — compact, rugged, and designed to operate within a single network segment without IP reconfiguration — the LAN firewall is a rare solution on the market. And in this field-ready format, MOXA is one of the very few vendors offering it.

Selection guide for MOXA industrial firewall types

Now that we’ve covered everything you need to know about the types of industrial firewalls, let’s wrap up with a quick selection guide.

Here’s a simple rule of thumb:

If you need to route traffic between VLANs, require NAT or VPN, need redundancy protocols, or want multiple ports — go for a boundary firewall.
If you need to protect a group of devices (especially legacy ones) within a single network segment, or want to filter traffic between just two devices — go for a LAN firewall.

Let’s do a quick recap and compare Boundary and LAN firewalls in the table below:

MOXA Industrial Firewall Types: Boundary vs. LAN

Category	Boundary Firewall	LAN Firewall
Position	Inside or Between LANs	Inside one LAN
Traffic	South–North traffic	East–West traffic
Networks	Intranet, Internet, DMZ	Intranet
Network Operation	Layer 3 Routing / NAT / Redundancy	Layer 2 Bridge (Transparent)
IP Reconfiguration Needed	Yes	No
IPS/IDS	Yes	Yes
Firewall with DPI	Yes	Yes
VPN, NAT	Yes	No
Number of Ports	4–10	Only 2 Ports, In-and-Out
Applications	Routing and filtering between network segments, IT and OT, Intranet and Internet DMZ creation and filtering	Micro-segmentation and protection of critical assets (PLCs, HMIs, SCADA) Protection of edge devices in isolated segments
MOXA Solutions	EDR-G9010 EDR-G9004 EDR-8010	EDF-G1002BP

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

At APulsar, we don’t just provide cutting-edge products; we offer end-to-end engineering services to design, plan, and implement robust industrial networks and security solutions tailored to your unique needs. Our expertise spans from creating secure architectures using firewalls to deploying technologies that ensure compliance with standards like IEC 62443.

Whether you need assistance with network segmentation, implementing firewalls and IDS/IPS, or integrating centralized management platforms like MXsecurity, our engineers provide hands-on support to ensure every layer of your network is optimized for both performance and security. With years of experience in industrial automation and OT cybersecurity, APulsar is your trusted partner for building secure, resilient infrastructures.

The post Boundary vs. LAN Industrial Firewalls Explained first appeared on APulsar Technologies.

The post Boundary vs. LAN Industrial Firewalls Explained appeared first on APulsar Technologies.

MOXA Smart Switches Explained

christine — Thu, 27 Feb 2025 03:37:08 +0000

SDS-3000/G3000 Series by MOXA: What Are They, When to Use Them, and How to Choose

Managed and unmanaged Ethernet switches have been around since the late 20th century, but the term “smart switch” emerged in the 2000s. While not yet widespread in industrial automation, now is a great time for this type of networking equipment to find its niche in the market. Let’s explore why.

What is an Ethernet Smart Switch?

An Ethernet smart switch sits between unmanaged and managed switches. Unmanaged switches are simple plug-and-play devices with no configuration options, where all connected devices share the same VLAN. Managed switches, even at Layer 2, offer extensive functionality: VLANs, DHCP, redundancy protocols, multicast, security, and much more. To fully utilize these, you typically need a solid networking background — something OT engineers don’t always have.

This is where smart switches come in. Designed to be nearly as simple as unmanaged switches while retaining essential managed switch features, they prioritize a “plug-and-play” approach. They offer a basic web UI and include only the most necessary functions, such as time settings (e.g., time zone, NTP) for accurate log timestamps, VLAN configuration for network segmentation, port mirroring for diagnostics, and redundancy protocols for network reliability.

The key advantage of smart switches is reducing the amount of networking knowledge required to set up basic network segments while retaining essential features. Learning managed switch configurations can take months of training (like a standard networking fundamentals course), while setting up a smart switch might take just a few hours of reading a manual, using a search engine, or asking a knowledgeable colleague.

Now that we understand what a smart switch is, let’s explore what makes MOXA’s SDS-3000/G3000 series truly special.

MOXA SDS-3000/G3000 Smart Switches: The Basics

At first glance, the MOXA SDS-3000/G3000 series looks like an unmanaged switch. It’s compact (20mm or 36mm wide, depending on the number of ports) and works out of the box. If you don’t touch the DIP switch (which we’ll discuss later), it behaves like an unmanaged switch with two-sided LED indicators that allow you to place it either front-facing or sideways while still being able to check active port statuses.

But the moment you log into the web interface, the real advantage of a smart switch becomes clear. Unlike MOXA’s fully managed switches, the SDS-3000/G3000 series doesn’t overwhelm you with dozens of configuration pages. Instead, it offers a one-page web UI, where separate pages are replaced with a “Management Bar” and “Management Buttons.”

Most functions are accessed by clicking a button and entering required data into a pop-up window — simple and efficient. The list of available configurations is intentionally limited to essentials, keeping things user-friendly.

Available Functions:

Language selection (English, Traditional/Simplified Chinese, Japanese, German, French)
Switch Locator (blinks LEDs to identify the device)
Statistics (usage info)
Fiber Check (fiber connector diagnostics)
Factory Default Reset
System Restart
Management Interface Configuration (HTTP, HTTPS, TCP ports)
Port Mirroring (traffic sniffing)
Trusted Access (list of allowed IP addresses)
Inventory Report Download (switch summary)
Log File Backup
Configuration Backup & Restore
Firmware Upgrade
User Account Management
Logout

This is more or less what you’d expect from a typical smart switch. But what makes the SDS-3000/G3000 series stand out?

Network Security and Redundancy

In addition to management buttons, the web UI includes a “Configuration Panels” area, where settings like the switch name and IP address can be configured. However, the most notable feature here is the “Switch Profile” section, which provides essential functions for cybersecurity and network redundancy.

Key Features:

Port Settings: Control access, speed, flow control, and MDI/MDIX mode
Static Port Lock: Restrict access to specific MAC addresses
IP-Port Binding: Restrict access to specific IP addresses
Redundancy Protocols: Supports RSTP, STP, and MRP (manager + client)
VLAN Configuration: IEEE 802.1Q VLAN support

Hovering over a port displays a table summarizing its current TX/RX statistics, including link status, speed, RSTP role, VLAN type, and even PD consumption in watts (for PoE models).

Additional features like an NTP client, unused port lock, and relay output for warnings further enhance security and reliability. But what truly sets these switches apart for industrial automation?

Industrial Automation Protocols

MOXA has a strong presence in industrial automation, and their smart switches are designed specifically for OT applications. The standout feature of the SDS-3000/G3000 series is its support for industrial automation protocols: EtherNet/IP, PROFINET, and Modbus TCP.

In the web UI, there’s a dedicated “Configuration Panels” section where these protocols can be enabled with a single click.

Once enabled, PROFINET, Modbus TCP, and EtherNet/IP statuses are transmitted and instructions received from connected devices. This allows SCADA/HMI systems to display real-time network data.

Even better, you don’t need to access the web UI to configure these protocols. The MOXA SDS-3000/G3000 features a DIP switch with 10 positions, each corresponding to different industrial protocol settings, including options with and without DHCP.

For example, if you want to enable the EtherNet/IP profile, simply set the DIP switch to position 3. If you need Modbus TCP with DHCP client enabled, set it to position 6; without DHCP, switch it back to 5. This straightforward configuration makes deployment quick and hassle-free.

In practical terms, this means you can take an MOXA SDS-3000/G3000 out of the box, set the DIP switch to the desired protocol, and immediately start using it with default IP addresses and VLANs — or log into the web UI for quick adjustments.

Smart PoE, SNMP, and Additional Features

Industrial automation isn’t the only application for these switches—video surveillance is another major use case. To support this, the MOXA SDS-3000/G3000 offers up to 8 PoE+ ports, each supplying up to 36W per port. The built-in Smart PoE software allows engineers to monitor PD status and set automatic recovery actions for failed devices.

Additionally, these switches support SNMP, including SNMPv3 for enhanced security, alongside other cybersecurity features like port lock, IP binding, and trusted access to align with IEC 62443 standards. Since the switch is a MOXA product, it can also be monitored in MOXA’s management software, MxView, making monitoring and deployment even easier.

With 34 models available, including up to 16 full Gigabit ports, SFP uplink ports, and PoE+ models, the SDS-3000/G3000 series offers flexibility for various industrial and surveillance applications.

Additionally, the MOXA SDS-3000/G3000 series supports the ABC-02-USB automatic backup configuration tool, enabling hassle-free system configuration backup, restoration, and firmware upgrades. The series also offers multiple mounting options — DIN-rail, wall mount, or rackmount (with an optional kit) — completing the list of features that MOXA has managed to pack into these compact devices.

Conclusion

Who should consider using MOXA’s smart switches?

When basic managed switch functions are needed—without the complexity or cost of full management.
When industrial protocols are required—many managed switches lack built-in OT protocol support.
For fast, easy deployment or replacements—without needing deep networking expertise.

From automated optical inspection in PCB manufacturing to bottling production lines and remote video surveillance, the MOXA SDS-3000/G3000 series is a reliable and cost-effective solution for industrial networking. Your project may add up to this list!

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

At APulsar, we don’t just provide cutting-edge products; we offer end-to-end engineering services to design, plan, and implement robust industrial networks. Whether you need help selecting the right switch, configuring OT protocols, or ensuring cybersecurity compliance, our experts are here to support you. Contact us today to optimize your industrial network for performance and security.

The post MOXA Smart Switches Explained first appeared on APulsar Technologies.

The post MOXA Smart Switches Explained appeared first on APulsar Technologies.

Top 5 Neousys x86 Computers Recommended by APulsar

christine — Thu, 06 Feb 2025 02:56:27 +0000

As we move into 2025, we highlight the innovative industrial computers from Neousys that have demonstrated exceptional performance and reliability across the industry. At APulsar, we’ve combined our expertise with customer feedback to create a list of the Top 5 Neousys x86 computers of 2024.

Here are our top picks, tailored for industrial automation and performance-driven applications.

What Do These 5 Have in Common?

All five computers in this list share the essential features that make them stand out in industrial automation:

Industrial-grade components
Wide operating temperature ranges
Flexible DC input voltage support
Fanless design for compact size and high reliability

These devices have gained customer trust and attention throughout the year for their reliability and versatility. Let’s take a closer look at their standout features.

1. Neousys POC-715

This ultra-compact Intel® Core i3-N305 embedded computer measures just 64 x 116 x 176mm, making it perfect for confined space applications. With an i3-N305 CPU, it offers comparable multi-threaded performance to the i7-6700, with significantly lower power consumption, making it ideal for fanless, embedded applications.

Best Feature: 1.3x CPU performance compared to the POC-500 series, powered by Intel® Alder Lake with DDR5-4800 memory for enhanced bandwidth.
I/O Connectivity: Four USB 3.2 Gen 2 ports, four GigE PoE+ ports, and HDMI/DP outputs for industrial cameras and displays.
Industrial Use: Perfect for machine vision and smart city applications.

2. Neousys Nuvo-2822

The Nuvo-2822 combines a compact design with expandability, powered by an Intel® Alder Lake N97 CPU. With two PCIe and two PCI slots, this system supports versatile industrial applications like motion control and data acquisition.

Best Feature: Super Power Saving Mode minimizes energy consumption in standby (S4/S5), reducing electricity usage.
I/O Connectivity: Two Ethernet ports, two USB 3.2 Gen 2 ports, and four COM ports for secure industrial communication.
Industrial Use: Ideal for machine automation and industrial control.

3. Neousys Nuvo-10000 Series

The Nuvo-10000 series offers flexible and powerful solutions for industrial automation. Powered by Intel® 14th/13th/12th-Gen Core i9/i7/i5/i3 processors, the series includes models such as the Nuvo-10003 and Nuvo-10007/10034, delivering exceptional computing power and up to seven PCIe/PCI slots for unmatched expandability. With support for NVIDIA® 115W TDP GPUs and a compact form factor, the Nuvo-10000 series is built to meet the demands of modern industrial applications.

Best Feature: Exceptional expandability with up to seven PCIe/PCI slots and support for NVIDIA GPUs, making it ideal for AI-driven applications.
I/O Connectivity: Eight USB 3.2 ports, five COM ports, one 2.5GbE port, and flexible SATA storage options.
Industrial Use: Perfect for vision inspection, machine automation, and industrial IoT solutions

4. Neousys Nuvo-9501

Compact yet cost-effective, the Nuvo-9501 is built for essential industrial applications. Featuring Intel® 14th/13th12th-Gen Core i9/i7/i5/i3 processors, it delivers reliable performance while maintaining affordability.

Best Feature: Gen4 x4 M.2 NVMe slot for high-speed storage and dual 2.5GbE ports for enhanced connectivity.
I/O Connectivity: Two display ports, four USB 3.2 ports, and optional 2.5”/3.5” HDD support for high-capacity storage.
Industrial Use: Perfect for data collection, surveillance, and general industrial needs.

5. Neousys Nuvo-10108GC

The Nuvo-10108GC is an advanced Industrial Edge AI Computer Supporting Single 350W NVIDIA® RTX GPU, Intel® 14th/ 13th/ 12th-Gen Core Processor with Three Additional PCIe Slots.

Best Feature: Three additional PCIe slots paired with NVIDIA RTX 40 series GPUs, delivering up to 91 FLOPS for AI workloads.
I/O Connectivity: Six USB 3.2 Gen2 ports, three 2.5GbE/GbE ports, and one optional 10GbE for high-speed connectivity and versatile expansion options.
Industrial Use: Ideal for AI-powered factory automation, autonomous vehicles, and other advanced industrial applications requiring exceptional GPU and CPU performance.

Conclusion

Neousys continues to push the boundaries of industrial computing, and these five devices exemplify innovation, reliability, and versatility. Whether your focus is on machine vision, AI workloads, or industrial automation, these systems are ready to tackle your toughest challenges.

Explore more Neousys solutions at APulsar’s Rugged Industrial Computers section.

The post Top 5 Neousys x86 Computers Recommended by APulsar first appeared on APulsar Technologies.

The post Top 5 Neousys x86 Computers Recommended by APulsar appeared first on APulsar Technologies.

What is DMZ, and Why is It Important for Your Industrial Network?

christine — Wed, 15 Jan 2025 06:44:54 +0000

The broad idea

First things first: let’s unpack Moxa’s original diagram on setting up a Demilitarized Zone (DMZ).

What we see above:

Industrial Network – This is the operational core of a business, where manufacturing and control systems reside. It includes essential equipment like machines, robots, and production lines, which are critical for maintaining productivity and safety. Protecting this network is paramount, as it directly impacts the industrial process.
Enterprise Network – The enterprise network covers the administrative side of the organization, including servers, employee workstations, and communication systems. Often directly connected to the Internet or Cloud, it supports business functions like project management, HR, and finance. Separation from the industrial network is crucial to maintain both security and operational efficiency, as internet access increases exposure to potential threats.
DMZ (Demilitarized Zone) – The DMZ acts as a buffer between the industrial and enterprise networks, controlling and filtering the flow of data. Typically, it includes systems that need to communicate with both networks without holding critical operational data — such as data historians, SCADA gateways, and aggregation systems. By allowing controlled data exchange, the DMZ ensures only necessary information crosses between networks, keeping sensitive areas protected.

Key Questions About DMZ

Now that we understand the basic functionality of a DMZ, let’s explore some fundamental questions in more detail.

Question 1: Where Is the DMZ Physically Located?

The DMZ is not necessarily a physical location, such as a separate building, room, or floor. Instead, it’s a conceptual network segmentation.

For example, in a factory:

Industrial Network hosts machines, robots, conveyors, and other production equipment.
Enterprise Network hosts employee computers, HR, and financial systems.

The DMZ is the “buffer” between these two networks, reducing the likelihood of direct interaction between the enterprise network (or the Internet) and the industrial network. Physically, the DMZ might be implemented using a separate VLAN or isolated network segment, managed by industrial routers and firewalls.

Question 2: What Is Located Inside the DMZ, and Why Are Systems Like SCADA Gateways Placed There?

The DMZ typically hosts systems that need to interface with both the industrial and enterprise networks but are carefully designed to avoid exposing critical operational data.

For example:

Data historians or SCADA gateways: These systems aggregate and transmit operational data to enterprise applications without exposing sensitive control functionalities.
Data exchange: By locating data historians or gateways in the DMZ, critical production data can be securely shared with enterprise networks for reporting, monitoring, or analysis.

Why Not Place SCADA Systems Directly in the DMZ?

Placing SCADA systems directly in the DMZ is generally not recommended. Instead:

SCADA systems remain in the industrial network to maintain control over critical operations.
The DMZ serves as a secure zone for systems that interface with SCADA, ensuring operational data can be shared without risking exposure to external threats.

This approach enhances security by ensuring that critical systems are protected while enabling efficient data sharing.

Question 3: Why Is the DMZ Necessary, and What Happens Without It?

The DMZ is crucial for separating access levels and mitigating threats. Without a DMZ:

Higher Risk of Breach: If the enterprise network is compromised (e.g., via phishing or malware), attackers could gain direct access to production systems, disrupting operations or causing accidents.
Weaker Security Layers: A DMZ adds layers of security, making it much harder for attackers to reach critical systems.

In short, the DMZ acts as a “border zone,” protecting vital industrial systems while enabling secure data exchange.

Question 4: Complete Isolation vs. DMZ – Why Use a DMZ?

While full isolation might seem like the safest option, it’s not always practical or efficient. Here’s why:

Data Access and Sharing: Modern businesses need real-time access to production data for decision-making, forecasting, and process optimization.
Monitoring and Analytics: SCADA and monitoring systems need to transmit data safely without exposing industrial assets.
Remote Support: Secure remote access allows technical support without costly on-site visits.
Regulatory Compliance: Standards like IEC 62443 recommend DMZ implementation for network segmentation.
Scalability: The DMZ allows flexible access adjustments as business needs evolve, avoiding costly infrastructure changes required by full isolation.

In essence, the DMZ strikes a balance between isolation and connectivity, enabling secure data sharing without compromising critical assets.

How Can the DMZ Be Strengthened with Moxa’s Secure Routers?

Moxa’s EDR and EDF Series secure routers enhance the DMZ’s effectiveness while aligning with IEC 62443 standards for industrial cybersecurity.

Key Features Include:

Integrated Firewall: Controls data flow and enforces strict access policies.
VPN Support: Enables secure communication between trusted networks.
Advanced Traffic Management: Manages and monitors all data entering or leaving the DMZ.

These purpose-built devices are designed for industrial environments, offering a robust defense against unauthorized access and cyber threats. Moxa’s secure routers ensure that the DMZ functions as a reliable bridge for secure data exchange, safeguarding both industrial and enterprise networks.

To explore Moxa’s full range of secure network solutions, visit our dedicated page.

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

At APulsar, we don’t just provide cutting-edge products; we offer end-to-end engineering services to design, plan, and implement robust industrial networks and security solutions tailored to your unique needs. Our expertise spans from creating secure architectures based on Defense-in-Depth principles to deploying technologies that ensure compliance with standards like IEC 62443.

The post What is DMZ, and Why is It Important for Your Industrial Network? first appeared on APulsar Technologies.

The post What is DMZ, and Why is It Important for Your Industrial Network? appeared first on APulsar Technologies.

Defense-in-depth Security Architecture

Yi Ying — Fri, 29 Nov 2024 07:54:01 +0000

Cybersecurity 101: A secure network infrastructure relies on a reliable defense-in-depth strategy. Discover how to construct layered network protection with our approach. Our secure networking solution offers a complete approach to ramp up your industrial network security.

Defense-in-Depth Security Architecture: A Key to Industrial Cybersecurity

In this article, we explore the concept of Defense-in-Depth Security Architecture, a cornerstone of modern industrial cybersecurity strategies. This approach emphasizes multiple layers of security mechanisms to protect industrial networks and critical assets. By adopting this layered defense strategy, organizations can effectively safeguard their operational technology (OT) environments from cyber threats.

Why Is Defense-in-Depth Security Architecture Important?

Industrial cybersecurity faces unique challenges compared to IT networks. OT systems often include legacy equipment, have minimal downtime tolerance, and operate in environments with high safety stakes.

Defense-in-Depth Security Architecture aligns with industry standards like IEC 62443, which advocate for layered security measures to address vulnerabilities at various levels of a system. This multi-layered strategy ensures that even if one defense mechanism fails, others continue to secure the network, minimizing risks to critical operations.

Core Components of Defense-in-Depth Security Architecture

Different sources present Defense-in-Depth Security Architecture from varied perspectives, reflecting their priorities and areas of expertise. Some divide security into administrative, physical, and technical controls, focusing on the types of measures applied. Others, prefer the functional approach, organize layers around what is being protected, such as data, applications, or infrastructure. MOXA, our key partner, simplifies the concept further, presenting four layers that align with their products: network segmentation, industrial firewalls, IPS/IDS, and critical asset protection.

These variations highlight the flexibility of the concept, as it can adapt to diverse industries, needs, and technologies. While no single division is standardized, frameworks like IEC 62443 emphasize the importance of layered defenses that combine physical, technical, and procedural controls to protect critical infrastructure.

In this article, we will focus on MOXA’s approach since it’s both simplified and aligns better with the solutions we provide at APulsar:

1. Network Segmentation
Network segmentation is the foundation of a secure industrial network. By dividing the network into smaller, isolated segments, organizations can prevent unauthorized access from spreading laterally across the infrastructure. Physical and virtual segmentation (e.g., VLANs, VPNs, NAT implementation) ensure that different zones within the facility are restricted and controlled, creating an essential first layer of security.

2. Industrial Firewalls
Industrial firewalls add another layer of protection by monitoring and filtering traffic between network zones. Unlike traditional firewalls, industrial firewalls are specifically designed to handle OT protocols and leverage features like Deep Packet Inspection (DPI) to analyze data packet payloads. This capability allows for precise threat detection and ensures the integrity of critical systems.

3. Industrial IPS/IDS
Intrusion Prevention Systems (IPS) and Intrusion Detection Systems (IDS) act as proactive defenders in the network. They monitor traffic for suspicious activity, alerting administrators to potential risks or automatically blocking malicious traffic.

IDS provides real-time alerts and monitors activity without interfering with network operations.
IPS goes further by actively blocking identified threats, reducing the risk of successful cyberattacks.

Industrial-grade IPS/IDS solutions are tailored to address the specific threats OT systems face, such as attacks on SCADA or PLC devices.

4. Critical Assets
At the core of the Defense-in-Depth model lie critical assets. These are the systems, devices, and data that require the highest level of protection. By securing these assets behind multiple layers of security, organizations ensure that even the most valuable parts of their infrastructure remain protected from threats.

One effective method for protecting critical assets in OT environments is Virtual Patching. This approach uses security mechanisms to monitor and block potential threats at the network or application layer without directly modifying the vulnerable system. By shielding systems from known and unknown threats, virtual patching eliminates the need for immediate software updates, which could disrupt operations. It serves as an additional defense mechanism, especially for legacy systems, ensuring critical assets remain secure even when traditional patching is not feasible.

MOXA’s Contribution to Defense-in-Depth Security Architecture
MOXA offers a range of industrial-grade solutions to support Defense-in-Depth strategies. Key offerings include:

EDR-G9010 Series Secure Routers : All-in-one devices that integrate firewall, NAT, VPN, and DPI capabilities to establish strong security perimeters. Combined with IDS/IPS functionalities, they provide robust protection against advanced cyber threats.
EDF-G1002-BP Series LAN Firewalls : These next-generation firewalls deliver IPS/IDS functionality with DPI for protocol-specific protection. Features like bump-in-the-wire installation and virtual patching make them ideal for securing mission-critical OT assets without disrupting operations.
NAT-102 Series : Simplifies IP configuration and provides access control in existing network infrastructures. With its compact design and rugged hardware, the NAT-102 series is perfect for environments requiring efficient and reliable NAT functionality.
MXsecurity Platform : A centralized network security management solution that provides real-time visibility into potential threats and simplifies compliance with standards like IEC 62443.

Conclusion

Defense-in-Depth Security Architecture is not just a theoretical concept but a practical necessity for any organization looking to protect its industrial operations from cyber threats. By implementing layered security measures, businesses can achieve compliance with industry standards and build resilient systems that withstand modern cybersecurity challenges.

APulsar: Your Partner in Industrial Network and Security Solutions

At APulsar, we don’t just provide cutting-edge products; we offer end-to-end engineering services to design, plan, and implement robust industrial networks and security solutions tailored to your unique needs. Our expertise spans from creating secure architectures based on Defense-in-Depth principles to deploying technologies that ensure compliance with standards like IEC 62443.

Whether you need assistance with network segmentation, implementing firewalls and IDS/IPS, or integrating centralized management platforms like MXsecurity, our engineers provide hands-on support to ensure every layer of your network is optimized for both performance and security. With years of experience in industrial automation and OT cybersecurity, APulsar is your trusted partner for building secure, resilient infrastructures.

The post Defense-in-depth Security Architecture first appeared on APulsar Technologies.

The post Defense-in-depth Security Architecture appeared first on APulsar Technologies.

10 Things You Can Do to Enhance Security for Connected Legacy Systems

general — Sat, 16 Dec 2023 06:26:50 +0000

With increasing demands on OT/IT integration, data security is at the forefront of our concerns more than ever. In fact, according to an IDC survey, security is considered the top barrier to OT/IT integration. At the same time, it is also considered a top-five motivator, meaning enhanced OT security is one of the means to bring about successful OT/IT integration. However, when integrating OT and IT systems from traditionally closed to open data systems, unwanted access may be given to an organization’s private operation data.

“If we look closer to why security is the largest barrier, we will find that in the OT environment one of the top security concerns is maintaining legacy systems safely and reliably,” said Helen Chiang, general manager at IDC Taiwan, in the Security Talks Show. “On an OT site, you’ll find many legacy systems and applications. They are not only isolated but also agentless, meaning the asset has limited resources to run the security solution that we usually execute in an IT environment.”

To connect unconnected legacy systems, several steps can be taken to enhance connectivity security and reduce security concerns for your OT/IT integration projects.

Tip 1: Change default passwords for your networking devices

Because your legacy systems are connected through networking devices, the first thing you can do to enhance connectivity security is to replace default passwords. The security strength of default passwords is usually low and easy to find in a public user manual. Don’t take this risk when you can easily prevent it.

Tip 2: Disable unused yet connected ports and services

When you deploy a networking device, some unused ports or unnecessary services may open the door to cyberthreats in your application. You can disable these ports and services to block the available paths to unwanted access.

Tip 3: Verify firmware source before update

When your networking devices require firmware update, make sure you have a mechanism to verify the firmware source. Checking the CRC code is one way to ensure the firmware you are about to use comes from the original source. Another way to verify the firmware source is through secure boot design. It’s a feature that ensures the integrity of firmware running on your platform.

Tip 4: Use secure communication protocols

It’s important to use a secure protocol (i.e., TLS 1.2 support in HTTPS and SNMPv3) for your connected legacy systems. It can reduce the chances of unwanted access while you are managing networking devices, and it can enhance data integrity while you are transmitting data. Also, when you deploy your networking devices, disable unsecure protocols to minimize the chances of a manual error.

Tip 5: Only allow authorized users to access your devices and network

Prioritize your critical assets and validate network segmentation. Then, you will have a clearer picture about what authority can be granted to what specific segment. Furthermore, deploy trust-listing such as listing only permitted IP addresses to keep unwanted access out of your legacy systems. Other advanced functions are also available to limit unwanted access. For example, you can define a specific protocol format or command that can access your devices and network.

Tip 6: Encrypt critical data before transmissions

In OT environments, critical data leakage can cause operation downtime, thus impacting operational efficiency. For connected legacy systems, you can encrypt critical data during transmissions to enhance your data confidentiality and reduce the chances of negatively impacting your daily operation.

Tip 7: Constantly monitor if your networking devices are at your desired security level

When you get your legacy systems connected, you should define the security measures based on your application’s demands so that you can easily monitor and manage your networking devices. When the system networks are up and running, constantly monitor whether the security status of your devices meets the requirements you defined from the onset.

Tip 8: Periodically scan vulnerabilities for potential threats

It’s essential to know what potential threats your legacy systems are facing. Scheduling a vulnerability scan periodically gives you a better idea of the security status of the overall system, helping you to take necessary actions when needed.

Tip 9: Perform security patches for your networking devices to reduce vulnerabilities

We all know that security patching is important. However, it is not always so easy in field sites. From a business perspective, it can lead to tremendous costs when you pause operations to test and perform patches. On the other hand, risks and costs are also involved when you are doing nothing about it. A more sustainable approach is finding a balance midway by performing acceptable batches of security patching for critical field systems.

Tip 10: Use virtual patching for known vulnerability of your legacy systems

In certain situations, security patching is not always an option. Furthermore, some legacy systems are not able to perform patching. For these type of situations, virtual patching is an efficient alternative. You can deploy the virtual patch in the network connected to your legacy systems to eliminate known vulnerabilities and protect the devices against certain exploits. Virtual patching is also a good way to reserve a buffer time while the system is waiting for the next maintenance period to get patched.

Take the above 10 tips into consideration when connecting your legacy systems—it can help you enhance connectivity security and minimize security threats to your legacy systems. Moxa provides a comprehensive security product portfolio for your edge connectivity security. Visit our website to learn more.

The post 10 Things You Can Do to Enhance Security for Connected Legacy Systems first appeared on APulsar Technologies.

The post 10 Things You Can Do to Enhance Security for Connected Legacy Systems appeared first on APulsar Technologies.

HARDWARE FAQ “MOXA INDUSTRIAL SWITCHES”

general — Thu, 16 Nov 2023 07:26:46 +0000

1. TYPES OF SWITCHES

Unmanaged – A switch without management features. It is used when it is necessary to combine several Ethernet devices into a single system. Moxa unmanaged switches are presented in seriesEDS-200, EDS-300 andEDS-2000. Configurable (Smart) – a switch with basic management functions. Can be used in small systems that do not require complex network settings.SDS-3008– smart switches from Moxa. Managed – a switch that supports the functionality of Layer 2 networks. Used to create reliable scalable systems within the same subnet. In the Moxa manufacturer’s catalog, managed switches are presented EDS-400 series and above (on a DIN rail), as well as in series IKS and ICS in a 19″” rack. Layer 3 managed switch is a managed switch that supports routing functions. It is used to create complex secure networks with several segments. Layer 3 switches from Moxa are IKS-G6824A series and ICS-G7826A/G7828A series.

2. WHAT ARE COMBO PORTS?

The combo port of the Ethernet switch is one logical port with two physical connectors: one copper for twisted pair 10/100/1000 BaseTx, the second for the fiber-optic SFP module Fast/Gigabit Ethernet. At the same time, only one of these two connectors can be active at a time: when installing an SFP transceiver, it will be impossible to transmit data over twisted pair.

3. DIFFERENCES BETWEEN EDS-400A, EDS-500A, EDS-500E, EDS-4000 AND EDS-G4000 MANAGED SWITCHES

4. COMPARISON OF MOXA POE SWITCHES

5. RESERVED POWER INPUT

EDS switches have two power inputs PWR1 and PWR2 (see picture on the right). This means that the power inputs are redundant, while there is only one power supply in the switch. This is necessary to power the switch from several external sources; if one of them fails, the switch will be powered from the second. It is not necessary to connect power to both inputs at the same time.

6. DEFAULT SETTINGS

“IP address: 192.168.127.253
Login: admin

Password: moxa (password is empty on some firmware versions)”

7. DO MOXA SWITCHES SUPPORT THIRD PARTY SFP MODULES?

No, Moxa switches are only compatible with SFP modules.

8. HOW TO CHOOSE THE RIGHT SFP MODULE FOR THE SWITCH/MEDIA CONVERTER?

Moxa switches are only compatible with Moxa SFP modules, but there may be equipment from another manufacturer on the other side of the optical line. In order for the connection to be established, the following optical parameters of the devices must be similar on both sides:
Transfer rate
Supported fiber type
Wavelength

9. RESET PASSWORD

In switches of the seriesEDS-500E, IKS-6000A andICSresetting the password is possible with a full reset of the device to factory settings. This is done using the Reset button on the device. To reset the settings, hold down the button for 5 seconds and release, after which the device will reboot with the default settings. Recall that the default password for most devices is moxa or blank.

For other models of managed switches, a specific reset procedure is required, available only when contacting technical support – support@moxa.ru.

10. RING COMMUNICATION RESERVATION

Moxa managed switches support Turbo Ring/Chain and STP/RSTP redundancy technologies. You can get acquainted with the technologies, their features and configuration in the corresponding instructions: Turbo Ring– ring redundancy of switches, recovery time 20ms. Turbo Chain– flexible switch redundancy, recovery time 20ms. RSTP- redundant links redundancy in complex topologies, recovery time over 5 seconds.

11. CAN I USE UNMANAGED OR 3rd party SWITCHES IN THE TURBO RING/CHAIN?

Turbo Ring/Chain redundancy technologies are built only on Moxa managed switches. The use of third party equipment is not allowed.

12. CONFIGURATION USING THE COMMAND LINE

For those who are accustomed to using the command line to configure devices, Moxa has provided such an opportunity. The serial and Telnet consoles of managed switches initially look like Menu. To replace it with the CLI command line, go to the Login Mode/Basic Settings section and press Y to activate the command line mode:

13. CONSOLE CABLE PIN ASSIGNMENT FOR SERIES SWITCHESEDS-400AAndEDS-500A

The post HARDWARE FAQ “MOXA INDUSTRIAL SWITCHES” first appeared on APulsar Technologies.

The post HARDWARE FAQ “MOXA INDUSTRIAL SWITCHES” appeared first on APulsar Technologies.

How to configure the MOXA Turbo Ring redundancy protocol?

general — Mon, 16 Oct 2023 07:25:25 +0000

This article shows how to configure the Turbo Ring V2 protocol for a ring topology through the switch’s web interface

Go to the Communication Redundancy section.

In the Redundancy Protocol field, specify the Turbo Ring V2 protocol type.

For ring topology, check the box Enable Ring 1.

In the Redundant Ports field, enter the port numbers used in the ring.

The post How to configure the MOXA Turbo Ring redundancy protocol? first appeared on APulsar Technologies.

The post How to configure the MOXA Turbo Ring redundancy protocol? appeared first on APulsar Technologies.

How to increase the transmission distance between two RS-232 devices over an Ethernet cable?

general — Sat, 16 Sep 2023 08:08:44 +0000

Increase Transmission Distance

The RS-232 interface provides information exchange between two devices at a distance of up to 15 meters. To overcome this limitation, MOXA offers two solutions: RS-232/422/485 to Ethernet converters or (NPort Series) RS-232 to RS-422/485 converters (TCC Series).

RS-232 – up to 15 meters, point-to-point operation mode
RS-422 and RS-485 – up to 1200 meters, point-to-point or multicast mode

The post How to increase the transmission distance between two RS-232 devices over an Ethernet cable? first appeared on APulsar Technologies.

The post How to increase the transmission distance between two RS-232 devices over an Ethernet cable? appeared first on APulsar Technologies.

How to connect a Modbus RTU device to an Ethernet network?

general — Wed, 16 Aug 2023 08:10:52 +0000

Determine the Modbus driver

First of all, you need to determine which Modbus driver on the SCADA host you want to use.

There are four possible options:

1. SCADA host with Modbus TCP driver
2. SCADA host with Modbus RTU driver – with built-in serial port
3. SCADA host with Modbus RTU driver – no built-in serial port
4. SCADA host with “Ethernet Encapsulation” driver

Option 1: SCADA host with Modbus TCP driver

This option requires an MGate protocol converter. You can use the Modbus TCP protocol to communicate with Modbus RTU devices through the gateway. There are many ” Modbus gateways ” available in the automation market that provide Modbus TCP connectivity for Modbus TCP slaves. When the gateway receives a Modbus TCP request, it converts the packet to Modbus RTU and immediately sends it to the Modbus RTU devices.

Option 2: SCADA host with Modbus RTU driver – with built-in serial port

This option is suitable if you just want to connect your existing SCADA host and Modbus RTU devices to an Ethernet network. If your SCADA host is equipped with a serial port, then a couple of gateways can solve this problem. As shown in the network diagram, MGate can convert Modbus RTU packet to Modbus TCP and vice versa. If there is no built-in serial port, this solution is not suitable for you, use option 3.

Option 3: SCADA host with Modbus RTU driver – no built-in serial port

If you want to use existing SCADA software and devices, but your SCADA host does not have a serial port, use a serial device serverto create a virtual COM port. This way you will be able to access remote serial devices through the server, and the functionality will correspond to the real COM port. To create a “virtual COM port”, the serial device server will install a virtual COM port driver on your SCADA host. To enable this port, set the serial device server to virtual COM port mode. All data transmitted through it will be sent to the remote serial port of the serial device server. Since the virtual COM is identical to the real one in terms of OS and SCADA, you can send a Modbus RTU request to it directly.

Option 4: SCADA Host with “Ethernet Encapsulation” Driver

If your SCADA host does not have a serial port and you do not want to install a virtual COM port driver, then you can use the “Ethernet Encapsulation” driver instead. Please note that the SCADA software must support the “Ethernet Encapsulation” connection type. Using the Ethernet Encapsulation drivers is recommended if you have advanced knowledge of serial and TCP/IP protocols.

The serial device server must be switched to the “Raw Socket” or “tunneling” mode, in which when SCADA sends Modbus RTU packets to devices, the connection between the host and the serial device server is made through a transparent TCP / IP or UDP channel without protocol conversion. The serial device server must be configured correctly because The Modbus RTU protocol determines the end of a packet based on pauses in transmission. If the Modbus RTU packet is split into two or more TCP/IP or UDP packets, you may encounter some problems. If you cannot properly configure packet transmission between serial channels and Ethernet networks, it is recommended to use the option with a gateway (2) or virtual COM port (3).

Although serial device servers can be used to connect Modbus RTU devices to an Ethernet network, the gateway option (2) is the preferred option and will satisfy almost all system requirements. Your host must support the Modbus TCP protocol, but this rarely causes problems because this protocol is very popular and widespread. Here are a few situations in which you need to use the presented option with a gateway:

Multiple Masters or Network Redundancy

An Ethernet connection not only allows for remote access, but also supports multiple connections. Most gateways support up to 32 connections, ie. 32 SCADA hosts can simultaneously request data from Modbus RTU devices. In this situation, it is quite difficult to provide network redundancy using a serial device server, because most servers do not support multiple masters, on the other hand, using gateways will not cause any problems.

One connection for multiple Modbus RTU devices

Sometimes it is necessary to use a single connection on a SCADA host to poll multiple Modbus RTU devices connected to different serial ports. The gateway is the only solution that can implement such a routing mechanism. Gateways with multiple serial ports can be configured to send a Modbus request to the appropriate serial port based on the unique IDs of the slaves. Sever serial devices can’t handle such a complex task.

The post How to connect a Modbus RTU device to an Ethernet network? first appeared on APulsar Technologies.

The post How to connect a Modbus RTU device to an Ethernet network? appeared first on APulsar Technologies.

APulsar Technologies

Boundary vs. LAN Industrial Firewalls Explained

What Is a Network Firewall, and What’s the Difference Between Software and Hardware Versions?

Difference Between Industrial and Commercial Hardware Firewalls

Industrial Protocol Support for DPI in MOXA Firewalls

Difference Between Boundary and LAN Industrial Hardware Firewalls

Selection guide for MOXA industrial firewall types

MOXA Industrial Firewall Types: Boundary vs. LAN

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

This is the heading

MOXA Smart Switches Explained

What is an Ethernet Smart Switch?

MOXA SDS-3000/G3000 Smart Switches: The Basics

Network Security and Redundancy

Industrial Automation Protocols

Smart PoE, SNMP, and Additional Features

Conclusion

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

This is the heading

Top 5 Neousys x86 Computers Recommended by APulsar

What Do These 5 Have in Common?

1. Neousys POC-715

2. Neousys Nuvo-2822

3. Neousys Nuvo-10000 Series

4. Neousys Nuvo-9501

5. Neousys Nuvo-10108GC

Conclusion

This is the heading

What is DMZ, and Why is It Important for Your Industrial Network?

The broad idea

First things first: let’s unpack Moxa’s original diagram on setting up a Demilitarized Zone (DMZ).

Key Questions About DMZ

Question 1: Where Is the DMZ Physically Located?

Question 2: What Is Located Inside the DMZ, and Why Are Systems Like SCADA Gateways Placed There?

Why Not Place SCADA Systems Directly in the DMZ?

Question 3: Why Is the DMZ Necessary, and What Happens Without It?

Question 4: Complete Isolation vs. DMZ – Why Use a DMZ?

How Can the DMZ Be Strengthened with Moxa’s Secure Routers?

APulsar Technologies: Your Partner in Industrial Network and Security Solutions

This is the heading

Defense-in-depth Security Architecture

Defense-in-Depth Security Architecture: A Key to Industrial Cybersecurity

Why Is Defense-in-Depth Security Architecture Important?

Core Components of Defense-in-Depth Security Architecture

Conclusion

APulsar: Your Partner in Industrial Network and Security Solutions

This is the heading

10 Things You Can Do to Enhance Security for Connected Legacy Systems

Tip 1: Change default passwords for your networking devices

Tip 2: Disable unused yet connected ports and services

Tip 3: Verify firmware source before update

Tip 4: Use secure communication protocols

Tip 5: Only allow authorized users to access your devices and network

Tip 6: Encrypt critical data before transmissions

Tip 7: Constantly monitor if your networking devices are at your desired security level

Tip 8: Periodically scan vulnerabilities for potential threats

Tip 9: Perform security patches for your networking devices to reduce vulnerabilities

Tip 10: Use virtual patching for known vulnerability of your legacy systems

This is the heading

HARDWARE FAQ “MOXA INDUSTRIAL SWITCHES”

1. TYPES OF SWITCHES

2. WHAT ARE COMBO PORTS?

3. DIFFERENCES BETWEEN EDS-400A, EDS-500A, EDS-500E, EDS-4000 AND EDS-G4000 MANAGED SWITCHES

4. COMPARISON OF MOXA POE SWITCHES

5. RESERVED POWER INPUT

6. DEFAULT SETTINGS

7. DO MOXA SWITCHES SUPPORT THIRD PARTY SFP MODULES?

8. HOW TO CHOOSE THE RIGHT SFP MODULE FOR THE SWITCH/MEDIA CONVERTER?

9. RESET PASSWORD

10. RING COMMUNICATION RESERVATION

11. CAN I USE UNMANAGED OR 3rd party SWITCHES IN THE TURBO RING/CHAIN?

12. CONFIGURATION USING THE COMMAND LINE

13. CONSOLE CABLE PIN ASSIGNMENT FOR SERIES SWITCHESEDS-400AAndEDS-500A

This is the heading

How to configure the MOXA Turbo Ring redundancy protocol?

This article shows how to configure the Turbo Ring V2 protocol for a ring topology through the switch’s web interface

This is the heading

How to increase the transmission distance between two RS-232 devices over an Ethernet cable?

Increase Transmission Distance

This is the heading