Juniper JUNOSE SOFTWARE 11.0.X - LINK LAYER CONFIGURATION GUIDE 4-1-2010 Configuration Manual page 561

ppp chap-challenge-length
CAUTION: Do not use the ppp chap-challenge-length command; increasing the
minimum length (from the default 16 bytes) or decreasing the maximum length
(from the default 32 bytes) reduces the security of your router.
ppp fragmentation
ppp hash-link-selection
Use the no version to specify that the router does not require authentication.
See ppp authentication.
Use to modify the length of the CHAP challenge by specifying the minimum
length and maximum length.
Specify the minimum and maximum lengths in bytes in the range 8–63.
The maximum length must be greater than or equal to the minimum length.
Example
host1(config-profile)#ppp chap-challenge-length 24 28
Use the no version to restore the default minimum 16 bytes and default
maximum 32 bytes.
See ppp chap-challenge-length.
Use to enable fragmentation on an MLPPP link interface and optionally specify
the maximum fragment size, in octets, to be used on the link.
Example
host1(config-profile)#ppp fragmentation 128
Use the no version to disable fragmentation on the link and restore the default
fragment size, which is the link's MTU.
See ppp fragmentation.
Use to enable use of a hash-based algorithm to select the link on which the router
transmits non-best-effort (high-priority) packets, such as voice or video, on the
dynamic MLPPP interfaces created by this profile.
Hash-based MLPPP link selection is available only for non-best-effort traffic. For
best-effort traffic, the router uses a round-robin algorithm for link selection.
Using hash-based link selection instead of the default round-robin link selection
for non-best-effort traffic ensures that the router maintains the proper packet
order when transmitting high-priority packets.
When you configure hash-based link selection, the router uses the IP source
address and IP destination address of the packet as a hash to select the MLPPP
member link on which to transmit the packet.
Chapter 15: Configuring Dynamic Interfaces
Configuring a Dynamic Interface from a Profile
531