BIND 10 #3337: perfdhcp wrong merge MAC to packet template

[BIND 10 Development]

#3337: perfdhcp wrong merge MAC to packet template
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  DHCP
  defect                             |  Outstanding Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DHCP
  perfdhcp                           |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:         |
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 This is a bug report regarding use of template packets in perfdhcp,
 submitted by Torsten Goehler:

 {{{
 Dear Sirs,
 I'm trying to factor template files for perfdhcp for DHCP performance
 testing.
 I factored a template file containing the required options.
 I used:
 perfdhcp -R 1000 -T discover.hex <serverIP>
 to start testing with 1000 simulated different MAC adresses.

 according to the bootp standart the Client MAC is directly positioned
 after the relay IP. The expection was perfdhcp to count up the client MAC,
 which starts w "00:0c:01:02:03:04" if I dont't give the "-b
 mac=xx:xx:xx:xx" starting value.

 This obviously works only if I dont't use a hex template file.
 In case I use the perfdhcp in conjunction w a template file as mentioned,
 the altering client MAC address is inserted into the packet w an off set
 of 2 bytes after the relay IP which is weird. Even if I try to use "-b
 mac=xx:xx:xx:xx" and template file together the given mac gets inserted w
 that 2 bytes offset which makes it impossible to control the client mac
 togehther with defining other options which are nessesary to simulate
 proper address scope selection.

 any ideas?
 point to patch the source and re-compile?

 Many thanks
 Torsten
 }}}

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