dhcp-relay
ipv6/dhcp-relay
Type: Directory
The DHCPv6 relay forwards DHCPv6 messages from clients on its interface to DHCPv6 servers, wrapped in Relay-Forward messages, and delivers the servers' Relay-Reply messages back to the clients. For an overview, see DHCP Relay.
| Flag | Name | Description |
|---|---|---|
| X | disabled | The relay is disabled. |
| I | invalid | The relay configuration is invalid. |
| Argument | Type | Description |
|---|---|---|
| name ( mandatory ) | string | Name of the relay. |
| interface ( mandatory ) | iface_enum | Interface on which the relay listens for messages from clients. |
| dhcp-server ( mandatory ) | object { server: alt { interface-address: composite { address6: ip6Addr , interface: iface_enum } , address6: ip6Addr } } | DHCPv6 servers to forward Relay-Forward messages to. A link-local address is given with its interface, for example fe80::1%ether1. |
| dhcp-options | multi { array-id, option: enum } | Options (/ipv6/dhcp-relay/option) added to Relay-Forward messages. The Interface-ID option (18) is always added. Default: client_mac, the client link-layer address (option 79). |
| link-address | ip6Addr | Address sent in the link-address field of Relay-Forward messages, which a server can use to identify the client's link. With ::, no address is sent. Default: ::. |
| delay-threshold | alt { const: enum (none) { none:0 } , time: time } | Minimum value of the elapsed-time field a message must have to be forwarded. With none, all messages are forwarded. Default: none. |
| store-relayed-bindings | bool | Whether to keep the bindings found in the servers' replies and add routes to them through the client, so traffic to delegated prefixes behind the relay is routed. The bindings are listed in /ipv6/dhcp-relay/routes. Default: no. |