Opened 7 years ago
Last modified 4 years ago
#2783 new defect
Using -n<x> to speifcy number of exhanges always yields x-1 exchanges, with 1 drop
Reported by: | tmark | Owned by: | |
---|---|---|---|
Priority: | medium | Milestone: | Outstanding Tasks |
Component: | perfdhcp | Version: | |
Keywords: | Cc: | ||
CVSS Scoring: | Parent Tickets: | ||
Sensitive: | no | Defect Severity: | N/A |
Sub-Project: | DNS | Feature Depending on Ticket: | |
Estimated Difficulty: | 0 | Add Hours to Ticket: | 0 |
Total Hours: | 0 | Internal?: | no |
Description
The -n<x> command line argument determines how many exchanges perfdhcp should execute. What one gets is always x-1 exchanges, and 1 drop. The following excerpt from stdout:
Running: perfdhcp -6 -l eth1 -R 105 -n 105 -r 1 -x aeistT fe80::20c:29ff:fea5:954a
IPv6
rate[1/s]=1
clients=105
num-request[0]=105
drop-time[0]=1
drop-time[1]=1
aggressivity=1
:
:
*Statistics for: SOLICIT-ADVERTISE*
sent packets: 105
received packets: 104
drops: 1
orphans: 0
It seems as though it is not waiting for the last exchange to complete. Behavior is very consistent, happens for 2-packet or 4-packet, -4 or -6, for any value of <x>.
Subtickets
Change History (1)
comment:1 Changed 4 years ago by tomek
- Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks
Note: See
TracTickets for help on using
tickets.
Milestone renamed