To allow secure router access for multiple remote hosts located behind a NAT device,
the router supports a set of IETF standards collectively known as NAT Traversal (NAT-T).
For a list of the individual standards that NAT-T comprises, see “References” on page 276
.
How NAT-T Works
By default, NAT-T is enabled on every virtual router configured on the system. With NAT-T
enabled, IPSec traffic flows transparently through a NAT device, thereby allowing one
or more remote hosts located behind the NAT device to use secure L2TP/IPSec tunnel
connections to access the router.
After NAT-T is enabled on a specific virtual router, either by default or by using the
ipsec
option nat-t
command, the router performs the following actions, in this order:
1.
The router monitors the exchange of private vendor ID (VID) payloads between the
client PC and the E Series router during the IKE SA negotiation to determine whether
both sides of the negotiation support NAT-T.
2.
If both sides of the negotiation support NAT-T, the router detects whether a NAT
device resides between the IPSec remote peers.
3.
If a NAT device is detected between the remote peers, the router negotiates the
appropriate type of UDP encapsulation as part of the IKE SA and uses this
encapsulation method to process the IPSec traffic.
The
ipsec option nat-t
command affects only those IKE SAs negotiated on the virtual
router
after
the command is issued. The command has no effect on IKE SAs that were
previously negotiated.
UDP Encapsulation
As part of the IKE SA negotiation process, the router automatically negotiates UDP
encapsulation for L2TP/IPSec control and data frames
.
When NAT-T is enabled, L2TP/IPSec control frames and data frames are wrapped in an
additional NAT-T UDP header that enables data to flow transparently through the NAT
device. The NAT device can translate the IP address of the source port associated with
the NAT-T UDP header, whereas the IPSec ESP header does not have a source port that
the NAT device can translate.
Figure 26 on page 281 shows an L2TP control frame encapsulated with a NAT-T UDP
header. The shaded area shows the portion of the frame that is encrypted by IPSec.
Figure 26: L2TP Control Frame with NAT-T UDP Encapsulation
281
Copyright © 2010, Juniper Networks, Inc.
Chapter 12: Securing L2TP and IP Tunnels with IPSec
Содержание JUNOSE 11.2.X IP SERVICES
Страница 6: ...Copyright 2010 Juniper Networks Inc vi...
Страница 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x IP Services Configuration Guide...
Страница 18: ...Copyright 2010 Juniper Networks Inc xviii JunosE 11 2 x IP Services Configuration Guide...
Страница 22: ...Copyright 2010 Juniper Networks Inc xxii JunosE 11 2 x IP Services Configuration Guide...
Страница 28: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x IP Services Configuration Guide...
Страница 116: ...Copyright 2010 Juniper Networks Inc 90 JunosE 11 2 x IP Services Configuration Guide...
Страница 144: ...Copyright 2010 Juniper Networks Inc 118 JunosE 11 2 x IP Services Configuration Guide...
Страница 230: ...Copyright 2010 Juniper Networks Inc 204 JunosE 11 2 x IP Services Configuration Guide...
Страница 262: ...Copyright 2010 Juniper Networks Inc 236 JunosE 11 2 x IP Services Configuration Guide...
Страница 294: ...Copyright 2010 Juniper Networks Inc 268 JunosE 11 2 x IP Services Configuration Guide...
Страница 328: ...Copyright 2010 Juniper Networks Inc 302 JunosE 11 2 x IP Services Configuration Guide...
Страница 345: ...PART 2 Index Index on page 321 319 Copyright 2010 Juniper Networks Inc...
Страница 346: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x IP Services Configuration Guide...
Страница 356: ...Copyright 2010 Juniper Networks Inc 330 JunosE 11 2 x IP Services Configuration Guide...