Port Forwarding

The Port Forwarding feature enables external clients to access services hosted on internal servers that are behind RUCKUS Edge. When configured, the RUCKUS Edge device forwards incoming traffic from a specified external port on its public IP (WAN) address to a designated private IP address and port within the LAN.

Feature Overview

The Port Forwarding feature provides controlled access to internal services by mapping external ports to internal IP/port pairs using static NAT44 endpoint-dependent mappings. This defines persistent translations between external and internal address-port pairs. These rules are installed on RUCKUS Edge and applied in the fast path for optimized performance. Each rule specifies:

  • External Port Range: Ports on the WAN interface (default range: 10000–19999 to avoid conflicts).
  • Internal IP Address and Port Range: The private server details within the LAN.
  • Protocol: TCP, UDP, or both.

Traffic flow is as follows:

  • Inbound (External → Internal): External client sends packets to the RUCKUS Edge WAN IP and configured port. The Edge device performs destination network address translation (DNAT) based on the static mapping, translating the destination to the internal server’s IP and port.
  • Outbound (Internal → External): The Edge device applies Source NAT (SNAT) to maintain session consistency, translating the source address back to the WAN IP and external port.

Some of the merits of Port Forwarding are:

  • Enables secure remote access to internal services
  • Reduces exposure of internal network
  • Supports granular control with up to 128 configurable rules

Requirements

This feature has no special hardware or software requirements for feature enablement or usage.

Considerations

Consider the following when configuring and using this feature:

  • Dual WAN is supported; rules are installed per WAN interface.
  • Failover requires external clients to know both the Active and Backup WAN addresses.
  • Overlapping external port ranges for the same protocol are disallowed.
  • Performance impact minimal; uses VPP fast path for established sessions.

Limitations

Note the following limitations regarding this feature:

  • Only up to 128 rules supported
  • Works only with IPv4; IPv6 traffic is not supported
  • Active-Backup HA supported; Active-Active HA not supported

Best Practices

Here are some implementation best practices for the feature:

  • Use non-conflicting external port ranges (10000–19999).
  • Avoid large port ranges to minimize rule count.

Prerequisites

Ensure the following prerequisites are met:

  • Edge device must be operational with WAN and LAN interfaces configured.
  • Internal servers should have static IP addresses.
  • Ensure no conflicting NAT or firewall rules exist.