73c8ced784
```
21.16. Vendor Class Option
This option is used by a client to identify the vendor that
manufactured the hardware on which the client is running. The
information contained in the data area of this option is contained in
one or more opaque fields that identify details of the hardware
configuration. The format of the Vendor Class option is:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_VENDOR_CLASS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. vendor-class-data .
. . . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 28: Vendor Class Option Format
option-code OPTION_VENDOR_CLASS (16).
option-len 4 + length of vendor-class-data field.
enterprise-number The vendor's registered Enterprise Number as
maintained by IANA [IANA-PEN]. A 4-octet
field containing an unsigned integer.
vendor-class-data The hardware configuration of the node on
which the client is running. A
variable-length field (4 octets less than the
value in the option-len field).
The vendor-class-data field is composed of a series of separate
items, each of which describes some characteristic of the client's
hardware configuration. Examples of vendor-class-data instances
might include the version of the operating system the client is
running or the amount of memory installed on the client.
Each instance of vendor-class-data is formatted as follows:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
| vendor-class-len | opaque-data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+
Figure 29: Format of vendor-class-data Field
The vendor-class-len field is 2 octets long and specifies the length
of the opaque vendor-class-data in network byte order.
Servers and clients MUST NOT include more than one instance of
OPTION_VENDOR_CLASS with the same Enterprise Number. Each instance
of OPTION_VENDOR_CLASS can carry multiple vendor-class-data
instances.
```
63 lines
2.1 KiB
C
63 lines
2.1 KiB
C
/* SPDX-License-Identifier: LGPL-2.1+ */
|
|
#pragma once
|
|
|
|
#include "sd-id128.h"
|
|
|
|
#include "macro.h"
|
|
#include "sparse-endian.h"
|
|
#include "time-util.h"
|
|
#include "unaligned.h"
|
|
|
|
#define SYSTEMD_PEN 43793
|
|
|
|
typedef enum DUIDType {
|
|
DUID_TYPE_LLT = 1,
|
|
DUID_TYPE_EN = 2,
|
|
DUID_TYPE_LL = 3,
|
|
DUID_TYPE_UUID = 4,
|
|
_DUID_TYPE_MAX,
|
|
_DUID_TYPE_INVALID = -1,
|
|
} DUIDType;
|
|
|
|
/* RFC 3315 section 9.1:
|
|
* A DUID can be no more than 128 octets long (not including the type code).
|
|
*/
|
|
#define MAX_DUID_LEN 128
|
|
|
|
/* https://tools.ietf.org/html/rfc3315#section-9.1 */
|
|
struct duid {
|
|
be16_t type;
|
|
union {
|
|
struct {
|
|
/* DUID_TYPE_LLT */
|
|
be16_t htype;
|
|
be32_t time;
|
|
uint8_t haddr[0];
|
|
} _packed_ llt;
|
|
struct {
|
|
/* DUID_TYPE_EN */
|
|
be32_t pen;
|
|
uint8_t id[8];
|
|
} _packed_ en;
|
|
struct {
|
|
/* DUID_TYPE_LL */
|
|
be16_t htype;
|
|
uint8_t haddr[0];
|
|
} _packed_ ll;
|
|
struct {
|
|
/* DUID_TYPE_UUID */
|
|
sd_id128_t uuid;
|
|
} _packed_ uuid;
|
|
struct {
|
|
uint8_t data[MAX_DUID_LEN];
|
|
} _packed_ raw;
|
|
};
|
|
} _packed_;
|
|
|
|
int dhcp_validate_duid_len(uint16_t duid_type, size_t duid_len, bool strict);
|
|
int dhcp_identifier_set_duid_llt(struct duid *duid, usec_t t, const uint8_t *addr, size_t addr_len, uint16_t arp_type, size_t *len);
|
|
int dhcp_identifier_set_duid_ll(struct duid *duid, const uint8_t *addr, size_t addr_len, uint16_t arp_type, size_t *len);
|
|
int dhcp_identifier_set_duid_en(struct duid *duid, size_t *len);
|
|
int dhcp_identifier_set_duid_uuid(struct duid *duid, size_t *len);
|
|
int dhcp_identifier_set_iaid(int ifindex, const uint8_t *mac, size_t mac_len, bool legacy_unstable_byteorder, void *_id);
|