Viper User
Manual (001-5008-000 Rev6)
Page
68
Figure 7.12 shows a Viper configuration protecting Viper (2) RF interface
and
Viper (1)
Ethernet interface from hosts located on a public network.
Figure 7.12 NAT on Viper: Private RF interface and Private Eth interface
An IP packet whose source IP address originates from the RF network and is sent towards
the Ethernet network will have its source IP address replaced by the Ethernet IP address of
Viper (2). Notice in this configuration the Ethernet IP address for Viper (1) is considered
private
and
the RF IP address for Viper (2) is considered private. Figure 7.13 shows how
the packets will be modified as the packets pass through the network.
Figure 7.13 Packet flow Private Eth and RF interface
In example Figure 7.14, the RF interface of Viper (2) is considered private. NAT is disabled
for Viper (1).
Eth: 172.31.5.1
RF: 10.0.14.203
RF: 10.0.14.186
Eth: 192.168.205.1
Host 2
Eth: 172.31.5.2
Viper (1)
(NAT enabled,
Ethernet Interface is private)
Viper (2)
(NAT enabled,
RF interface private)
Private Network
Host 1
Eth: 192.168.205.2
Public Network
Pubic
Network
RF Private Network
Packet (1)
Source Address 192.168.205.2
Destination Address 172.31.5.2
Packet (1)
Source Address 10.0.14.203
Destination Address 172.31.5.2
Packet (1)
Source Address 172.31.5.1
Destination Address 172.31.5.2
Host 1
192.168.205.2
Host 2
172.31.5.2
Viper 1
NAT enabled, Eth is private
Viper 2
NAT enabled, RF is private
Private Network
Private RF Network
Public Network