Spirent Avalanche 5.46 February 29, 2024
Use the PPP Group window to configure Point-to-Point Protocol (PPP) parameters. Avalanche supports the following capabilities:
The PPP Group window includes the following panes:
Field | Description | |
---|---|---|
PPP Group Name | The name of the PPP group that you are creating or editing. | |
Parameters Fields: | ||
Maximum Receive Unit | Size of the Maximum Receive Unit (MRU). | |
Maximum Configure Requests | Number of times Avalanche sends a Configure Request message without receiving a response. | |
Maximum Configure NACKs | Number of times an incorrect Configure Request from the device under test (DUT) is NACKed before it is ignored. | |
Maximum Termination Requests | Number of times Avalanche sends a PPP session termination message without receiving a valid acknowledgement. | |
Restart Timer | Time in seconds between Configure Request messages. | |
Maximum Link Retry | Number of retry attempts if negotiation of the link fails. | |
Session Timeout | Inactivity timeout for the PPP session. | |
Users per Session | Number of simulated users per PPP session. | |
Echo Interval | Frequency in seconds to send LCP keep-alive requests. | |
Echo Request | Select to enable the sending of LCP keep-alive requests. | |
Echo Reply | Select to enable the responses to echo requests. | |
IP Negotiation (IPv4 only) | Select to enable the IP negotiation. If enabled, Avalanche
uses IPCP to obtain the IP address from the device under test
(DUT). If disabled, Avalanche uses the IP address range established
in the Client Subnets tab.
Regardless whether this checkbox is enabled or disabled, you must
enter a value in the IP Address Range field in the Client Subnets
tab. Avalanche uses this information to specify the number of
hosts that are in the test.
|
|
Magic Number | Select to enable the automatic generation of the magic number. | |
Two Way Authentication | Applies to Password Authentication Protocol (PAP) and Challenge-Handshake Authentication Protocol (CHAP) authentication. Select to enable authentication in both directions simultaneously. That is, the client authenticates with the Access Concentrator (AC) using a username/password, and the AC authenticates with the client using a username/password. The client automatically accepts the username/password supplied by the AC. If you don't select this checkbox, then Avalanche performs only client authentication with the Access Concentrator (AC) |
|
Authorization Fields: | ||
Authorization | Select to enable the authentication feature. After you select the checkbox, the authorization fields become available for editing. You can select to use a forms database or user defined data based on wild card usernames and passwords. | |
Authentication Type | Type of authentication. None: No authentication is performed. PAP: Password Authentication Protocol CHAP MD5: Challenge-Handshake Authentication Protocol
|
|
Use Forms Database | Select to enable the Forms Database feature. Use a forms database to specify outgoing usernames and passwords. If you select this option, you must also select a forms database as described in the next description, and you do not select the User Defined Data option. | |
Select a File | Lists available forms databases. To access the list, you must
first select the Use Forms Database radio button. You can also
create a new forms
database using the New icon .
|
|
User Defined Data | Select to generate outgoing usernames and passwords based on wild card replacements. The # character represents a counter. For example, define a counter to start at 1000 (Start Count Inner Loop), run to 9999 (End Count Inner Loop), and increment by 1 (Inc Count Inner Loop). Then, in the Wild Card Username field, specify user#, which would be replaced with user1000, user1001, and so on, when the test executes. If you select this option, you must also enter information in the following fields. If you select this option, do not select the Use Form Database option. |
|
Wild Card Username | Wild card username, such as user#. | |
Wild Card Password | The wildcard password, such as pwd#. | |
Start Count Inner Loop | Starting value of the first (inner) counter. | |
End Count Inner Loop | Ending value of the first (inner) counter. | |
Inc Count Inner Loop | Value by which the first (inner) counter is incremented. | |
Start Count Outer Loop | Starting value of the second (outer) counter. | |
End Count Outer Loop | Ending value of the second (outer) counter. | |
Inc Count Outer Loop | Value by which the second (outer) counter is incremented. | |
Inc Second Count | Select on/off to activate/deactivate the second (outer) counter. |
© 2024 Spirent Communications, Inc. All Rights Reserved.