Figure 20 Branch-To-Branch With A Firewall And A Router - Nortel Contivity 1100 Configuration Manual

Figure 20 Branch-to-branch with a firewall and a router

LAN
1
2
Nortel VPN Router
Private LAN
In the branch-to-branch illustration, the following interactions take place with a
Nortel VPN Router:
1
2
3
4
For a Nortel VPN Router that has a WAN link, actions 3 and 4 collapse together,
and the encapsulated data is directed to the remote server.
In a three-Nortel VPN Router topology, the two indirectly connected Nortel VPN
Routers can create tunnels at will as long as each Nortel VPN Router properly
includes all of the local and remote subnetworks and subnetwork masks as
accessible networks.
Nortel VPN Routers and the local and remote networks that must be configured
for each link to allow indirectly connected branch offices to bring up tunnels at
will. The New York Nortel VPN Router in the middle has two branch office
connections configured.
All connections must have identical encryption settings. However, only adjacent
connections are required to share keys. For example in the following figure, the
Boston − New York connection shares keys and the New York − Cleveland
connection shares keys. Boston and Cleveland are not required to share keys.
Public LAN
Firewall
3
The PC sends packets to the default route (the firewall).
The firewall redirects the packets to the local Nortel VPN Router branch
office connection.
The encapsulated data goes onto the public LAN.
The default public LAN route directs the encapsulated data to the remote
Nortel VPN Router branch office connection.
Figure 21 on page 122
Chapter 6 Configuring branch office tunnels 121
4
Router PDN
Public WAN
shows the relationship between three
Nortel VPN Router Configuration — Basic Features
Nortel VPN Router