DHCPv4 and DHCPv6 share some values in common for the architecture- specific options (such as the client system architecture type), but use different encapsulations: DHCPv4 has a single byte for the option length while DHCPv6 has a 16-bit field for the option length. Move the containing DHCP_OPTION() and related wrappers from the individual dhcp_arch.h files to dhcp.c, thus allowing for the architecture-specific values to be reused in dhcpv6.c. Signed-off-by: Michael Brown <mcb30@ipxe.org>tags/v1.20.1
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
33 | 33 |
|
34 | 34 |
|
35 | 35 |
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
36 |
|
|
37 |
|
|
38 |
|
|
39 |
|
|
40 | 40 |
|
41 |
|
|
42 |
|
|
41 |
|
|
43 | 42 |
|
44 |
|
|
43 |
|
|
45 | 44 |
|
46 | 45 |
|
|
||
82 | 82 |
|
83 | 83 |
|
84 | 84 |
|
85 |
|
|
86 |
|
|
87 |
|
|
85 |
|
|
86 |
|
|
87 |
|
|
88 | 88 |
|
89 | 89 |
|
90 | 90 |
|