BIND 10 #2783: Using -n<x> to speifcy number of exhanges always yields x-1 exchanges, with 1 drop

[BIND 10 Development]

#2783: Using -n<x> to speifcy number of exhanges always yields x-1 exchanges, with
1 drop
-------------------------------------+-------------------------------------
                   Reporter:  tmark  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP
                   Priority:         |  Outstanding Tasks
  medium                             |              Keywords:
                  Component:         |             Sensitive:  0
  perfdhcp                           |           Sub-Project:  DNS
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 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>.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2783>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development