Viper User
Manual (001-5008-000 Rev6)
Page
69
Figure 7.14 NAT on Viper: RF interface considered private
Notice in Figure 7.15 that when Host 1 sends a packet, the source IP address is not changed
by Viper (2) because the source does not originate from the private RF network.
Figure 7.15 Packet flow, RF interface considered private
In the previous example, Viper (1) was changing the source IP address of the packet,
making the Viper (2) believe that the packet was originating from the RF network.
1.1.45
User NAT Entries
The user can add three USER IP addresses that will be considered private. Figure 7.16
shows USER1 192.168.205.125 and USER2 192.168.205 will be considered private. If
USER3 192.168.205.87 is connected to the Viper, but not added to the table, USER3
192.168.205.87 would not be considered private.
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 disabled)
Viper (2)
(NAT enabled,
RF interface private)
Network
Host 1
Eth: 192.168.205.2
Public Network
Private RF Network
Packet (1)
Source Address 192.168.205.2
Destination Address 172.31.5.2
Packet (1)
Source Address 192.168.205.2
Destination Address 172.31.5.2
Packet (1)
Source Address 192.168.205.2
Destination Address 172.31.5.2
Host 1
192.168.205.2
Host 2
172.31.5.2
Viper 1
NAT disabled,
Viper 2
NAT enabled, RF is private
Public Network
Private RF Network
