Note interfaces are not re-detected during <command>config-test</command>.
</para>
+ <para>Usually loopback interfaces (e.g. the "lo" or "lo0" interface)
+ may not be configured but if a loopback interface is explicitely configured
+ and IP/UDP sockets are specified the loopback interface is accepted.
+ </para>
+
+ <para>It can be used for instance to run Kea in a FreeBSD jail having
+ only a loopback interface, servicing relayed DHCP request:
+
+ <screen>
+ "Dhcp4": {
+ "interfaces-config": {
+ "interfaces": [ <userinput>"lo0"</userinput> ],
+ "dhcp-socket-type": "udp"
+ },
+ ...
+ }</screen>
+ </para>
+
</section>
-<section id="dhcpinform-unicast-issues">
+<section xml:id="dhcpinform-unicast-issues">
<title>Issues with Unicast Responses to DHCPINFORM</title>
<para>The use of UDP sockets has certain benefits in deployments
where the server receives only relayed traffic; these benefits are
}
</screen>
+ <para>The loopback interfaces (i.e. the "lo" or "lo0" interface)
+ are not configured by default, unles explicitely mentioned in
+ the configration. Note Kea requires a link-local address which does
+ not exist on all systems, or a specified unicast address as in:
+ </para>
+
+ <screen>
+ "Dhcp6": {
+ "interfaces-config": {
+ "interfaces": [ <userinput>"lo/::1"</userinput> ]
+ },
+ ...
+ }
+ </screen>
+
</section>
- <section id="ipv6-subnet-id">
+ <section xml:id="ipv6-subnet-id">
<title>IPv6 Subnet Identifier</title>
<para>
The subnet identifier is a unique number associated with a particular subnet.