mirror of
https://github.com/kernelkit/infix.git
synced 2026-07-30 04:33:00 +02:00
Joachim Wiberg
cb5d804a88
A valid DHCP server setup for a subnet is one of pool and/or at least one static host entry/lease. If pool is enabled the pool must have a start and an end address. To allow setting up a DHCP server with no pool and at least one static host entry/lease, we make the pool a presence container, otherwise the pool will always be set and trigger the below inference. When an interactive CLI/Web user enables the address pool we infer a default range .100-.250, but only for /24, C-class networks. This is what most users know and expect. The YANG model now validates that: - If an address pool is created, both start-address and end-address must be set - Each subnet must have either a pool or at least one static host entry - The pool container is now a presence container, so "no pool" fully deletes it Fixes #1121 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Welcome to Infix, your immutable, friendly, and secure operating system! On these pages you can find both user and developer documentation.
Most topics on configuring the system include CLI examples, but every setting, as well as status read-back from the operational datastore, is also possible to perform using NETCONF or RESTCONF. In fact, the Infix regression test system solely relies on NETCONF and RESTCONF.
Tip
The CLI documentation is also available from inside the CLI itself using the
helpcommand in admin-exec mode.
- CLI Topics
- Infix User Guide
- Infix In-Depth
- Developer Topics