- A bug in subnet6 parsing where options contained in subnet6 clauses would

not be applied to clients addressed within that network was repaired.

- When configuring a "subnet {}" or "subnet6 {}" without an explicit
  shared-network enclosing it, the DHCP software would synthesize a
  shared-network to contain the subnet.  However, all configuration
  parameters within the subnet more intuitively belong "to any client
  on that interface", or rather the synthesized shared-network.  So,
  when a shared-network is synthesized, it is used to contain the
  configuration present inside the subnet {} clause.  This means that
  the configuration will be valid for all clients on that network, not
  just those addressed out of the stated subnet.  If you intended the
  opposite, the workaround is to explicitly configure an empty
  shared-network.

- A bug was fixed where Information-Request processing was not sourcing
  configured option values.

- A warning was added since the DHCPv6 processing software does not yet
  support class statements.

  [ISC-Bugs #17638b]

includes/dhcpd.h

@@ -807,6 +807,10 @@ struct shared_network {
 	OMAPI_OBJECT_PREAMBLE;
 	struct shared_network *next;
 	char *name;
+
+#define SHARED_IMPLICIT	  1 /* This network was synthesized. */
+	int flags;
+
 	struct subnet *subnets;
 	struct interface_info *interface;
 	struct pool *pools;
@@ -1395,6 +1399,7 @@ struct ipv6_pool {
 						   released leases */
 	struct shared_network *shared_network;	/* shared_network for 
 						   this pool */
+	struct subnet *subnet;			/* subnet for this pool */
 };
 
 extern struct ipv6_pool **pools;