Cisco Cisco Packet Data Interworking Function (PDIF)
Context Configuration Mode Commands N-R
ppp ▀
Command Line Interface Reference, StarOS Release 17 ▄
2659
This keyword specifies whether to allow Address and Control Field Compressed PPP packets received from
the Peer. During LCP negotiation, the local PPP side indicates whether it can handle ACFC compressed PPP
packets. Default:
the Peer. During LCP negotiation, the local PPP side indicates whether it can handle ACFC compressed PPP
packets. Default:
allow
When allow is specified, the local PPP side indicates that it can process ACFC compressed PPP packets and
compressed packets are allowed. When deny is specified, the local PPP side indicates that it cannot handle
ACFC compressed packets and compressed packets are not allowed.
compressed packets are allowed. When deny is specified, the local PPP side indicates that it cannot handle
ACFC compressed packets and compressed packets are not allowed.
transmit { apply | ignore | reject }
Specifies how Address and Control Field Compression should be applied for PPP packets transmitted to the
Peer. During LCP negotiation, the Peer indicates whether it can handle ACFC compressed PPP packets.
Default:
Peer. During LCP negotiation, the Peer indicates whether it can handle ACFC compressed PPP packets.
Default:
ignore
When apply is specified, if the peer requests ACFC, the request is accepted and ACFC is applied for
transmitted PPP packets. When ignore is specified, if the peer requests ACFC, the request is accepted, but
ACFC is not applied for transmitted PPP packets. When reject is specified, if the peer requests ACFC, the
request is rejected and ACFC is not applied to transmitted packets.
transmitted PPP packets. When ignore is specified, if the peer requests ACFC, the request is accepted, but
ACFC is not applied for transmitted PPP packets. When reject is specified, if the peer requests ACFC, the
request is rejected and ACFC is not applied to transmitted packets.
auth-retry suppress-aaa-auth
This option does not allow PPP authentication retries to the AAA server after the AAA server has already
authenticated a session. PPP locally stores the username and password, or challenge response, after a
successful PPP authentication. If the Mobile Node retries the PAP request or CHAP-Response packet to the
PDSN, PPP locally compares the incoming username, password or Challenge Response with the information
stored from the previous successful authentication. If it matches, PAP ACK or CHAP Success is sent back to
the Mobile Node, without performing AAA authentication. If the incoming information does not match with
what is stored locally, then AAA authentication is attempted. The locally stored PPP authentication
information is cleared once the session reaches a connected state.
Default:
authenticated a session. PPP locally stores the username and password, or challenge response, after a
successful PPP authentication. If the Mobile Node retries the PAP request or CHAP-Response packet to the
PDSN, PPP locally compares the incoming username, password or Challenge Response with the information
stored from the previous successful authentication. If it matches, PAP ACK or CHAP Success is sent back to
the Mobile Node, without performing AAA authentication. If the incoming information does not match with
what is stored locally, then AAA authentication is attempted. The locally stored PPP authentication
information is cleared once the session reaches a connected state.
Default:
no auth-retry suppress-aaa-auth
Important:
This option is not supported in conjunction with the GGSN product.
chap fixed-challenge-length length
Normally PPP CHAP use sa random challenge length from 17 to 32 bytes. This command allows you to
configure a specific fixed challenge length of from 4 through 32 bytes.
configure a specific fixed challenge length of from 4 through 32 bytes.
length
must be an integer from 4
through 32.
Default: Disabled. PAPCHAP uses a random challenge length.
Default: Disabled. PAPCHAP uses a random challenge length.
dormant send-lcp-terminate
Indicates a link control protocol (LCP) terminate message is enabled for dormant sessions.
Important:
This option is not supported in conjunction with the GGSN product.
echo-max-retransmissions num_retries
Configures the maximum number of retransmissions of LCP ECHO_REQ before a session is terminated in an
always-on session.
always-on session.
num_retries
must be an integer from 1 through 16. Default: 3
echo-retransmit-timeout msec
Configures the timeout (in milliseconds) before trying LCP ECHO_REQ for an always-on session.
msec
must be an integer from 100 through 5000. Default: 3000