8.
The E Series PPP processes the proxy authentication data, if it is present, and
passes the data to AAA for verification. (If the data is not present, E Series PPP
requests the data from the remote system.)
9.
The router passes the authentication results to the remote system.
Packet Fragmentation
The E Series router supports the reassembly of IP-fragmented L2TP packets. (For
more information, see the
IP Reassembly for Tunnels
chapter in
JUNOSe IP Services
Configuration Guide
.) However, it is preferable to prevent fragmentation within L2TP
tunnels because of the effects of fragmentation and reassembly on performance.
To prevent fragmentation, PPP LCP negotiation of the maximum receive unit (MRU)
may be used to determine a proper maximum transmission unit (MTU). However,
the normal automatic method of determining the proper MRU to negotiate (by
evaluating the MRU of all lower layers in the interface stack) is not adequate for L2TP.
The initial LCP negotiation between PPP in the client and the LAC is inadequate
because it does not cover the entire extent of the eventual PPP session that travels
all the way from the client to the LNS. Furthermore, even if PPP in the LNS chooses
to renegotiate the MRU, it has no way to determine the proper MRU, since it does
not know the minimum MRU on all of the intervening links between it and the LAC.
To overcome the inadequacy of normal determination of the MRU under such
circumstances, you can configure the PPP MRU size by using the
ppp mru
command
in Profile Configuration mode, Interface Configuration mode, or Subinterface
Configuration mode. Use Profile Configuration mode for dynamic PPP interfaces,
and Interface Configuration mode or Subinterface Configuration mode for static PPP
interfaces.
When you specify the size, you need to take into account the MRU for all possible
links between the LAC and the LNS. You must also take into account the L2TP
encapsulation that is added to all packets entering the tunnel.
For example, if the link between the LAC and LNS with the lowest MRU were an
Ethernet link, the following calculation applies:
1500
-20
-8
-30
Minimum link MRU
L2TP encapsulating IP header
L2TP encapsulating UDP header
Maximum L2TP header (assumes a maximum of
16 bytes of Offset Pad)
1442
MRU size to specify
If the smallest intervening link is an Ethernet link, specifying
ppp mru 1442
at either
the LAC or LNS guarantees that no fragmentation will occur within the L2TP tunnel.
Packet Fragmentation
■
333
Chapter 11: L2TP Overview
Summary of Contents for JUNOSE 11.0.X MULTICAST ROUTING
Page 6: ...vi...
Page 28: ...xxviii Table of Contents JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 36: ...xxxvi List of Tables JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 42: ...2 Managing Remote Access JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 204: ...164 Managing RADIUS and TACACS JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 292: ...252 Monitoring RADIUS Relay Server JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 336: ...296 RADIUS Client Terminate Reasons JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 368: ...328 Managing L2TP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 444: ...404 PPP Accounting Statistics JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 494: ...454 Managing DHCP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 510: ...470 DHCP Local Server Configuration Tasks JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 556: ...516 Configuring DHCP Relay Proxy JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 616: ...576 Managing the Subscriber Environment JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 674: ...634 Managing Subscriber Services JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 767: ...Part 7 Index Index on page 729 Index 727...
Page 768: ...728 Index JUNOSe 11 0 x Broadband Access Configuration Guide...