Unable to set "interface" for a subnet via remote-subnet4-set when such interface is not present in the system
The cb_cmds uses Kea parsers to parse the subnet information received via commands. The parsers were initially designed to parse local Kea configuration files. The subnet parser, for example, checks whether the interface set for a subnet is present in the system. If it is not, it spits out an error similar to this:
[ { "result": 1, "text": "subnet configuration failed: Specified network interface name vboxnet0 for subnet 192.168.50.0/24 is not present in the system (:0:0)" } ]This shouldn't be the case when setting the configuration via the CB, because a given server should be able to set the configuration for any DHCP server, not necessarily for itself.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information