To Next Page

To Previous Page

Case 1: The source address for the HTTP traffic is translated by another public address, for traffic that is

initiated from the same LAN host.

Topology: PC1 –– LAN[RV260W]WAN –– (Internet) –– PC2

• PC1: 192.168.1.111

• RV260W LAN: 192.168.1.1

• RV260W WAN: 172.16.1.1/24

• PC2: 172.16.1.100

Goal: The HTTP traffic is translated to a new public address (172.16.1.10) and the non-HTTP traffic is

translated to a WAN address for PC1.

Address Object: Configure the address on PC1 as a single IP of 192.168.1.111 and the wan_alias as the new

public address of 172.16.1.10

Result: The source address is translated to 172.16.1.10 when initiating HTTP traffic from PC1. When initiating

FTP traffic from PC1, the source address is translated to the original WAN address of 172.16.1.1.

Case 2

Topology PC1/PC10 –– LAN[RV260W]WAN –– (Internet) –– PC2

• PC1: 192.168.1.111

• PC10:192.168.1.10

• RV260W LAN: 192.168.1.1

• RV260W WAN: 172.16.1.1/24

• PC: 172.16.1.100

Goal: Use the source address to let the PC translate to a specific public address while the others will still

translate to a WAN address.

Address Object: Configure the address on PC1 to 192.168.1.111, PC10 to 192.168.1.10, wan_alias to

172.16.1.10 and wan_alias2 to 172.16.1.11.

Result: Initiate traffic from PC1, PC10, and the other PC. The traffic from PC1 and PC10 is translated to

172.16.1.10 and 172.16.1.11 respectively. The traffic from the other PC is translated to the WAN address of

172.16.1.1.

Case 3

The VLAN2 subnet runs NAT while the VLAN1 and the other subnet runs on routing mode.

Topology PC1/PC10 –– LAN[RV260W]WAN –– (Intranet) –– PC2

• PC1: 192.168.1.111, in VLAN1

• PC10: 192.168.2.10, in VLAN2

• RV260W LAN: 192.168.1.1 (VLAN1), 192.168.2.1 (VLAN2)

• RV260W WAN: 172.16.1.1/24

• PC2: 172.16.1.100

RV260x Administration Guide

Firewall

Policy NAT Use Cases

Cisco RV260 series User Manual

Questions and Answers: