Since one interface can have multiple subnets in IPv6 its better to group them via interface. It also helps with dynamic pools since in the same interface you could have a static ULA pool as well.
ui: clean up useRequestHandlerOnGet usage
This has no use anymore with the current bootgrid code. If a
handler should be overridden, simply defining the function is enough
bootgrid: replace 'append' with 'replace' for ajax: false grids
Noticed while documenting.
replaceData() is a lot more performant through Tabulator, and since
there are only 3 callers and all of them expect a clear before
updating any data, use a replace instead.
In time these pages should use the default search endpoint anyway,
but this requires an API change.
make sure to keep the append() function for compatibility
Firewall: Rules [new] - fix unintended change in filtering logic caused by https://github.com/opnsense/core/commit/c4aefc08f41167b921595cd3f606aadc72b46730
When inspect mode is not selected, only full matches are expected when filtering specific interfaces.
This also means when selecting the inverse of an interface, it automatically belongs to the "floating" group for not being a direct match.
To explain the options a bit better, comments are inserted in the filtereing block.
bootgrid: clean up converter compatibility code
Only other consumer is Nginx in plugins, but worst case scenario
these timestamps will render as... timestamps, which in that form
are sortable anyway. It's likely this was throwing an error anyway
The "sorters" weren't actually accounted for in the compat
translation, so this wasn't overridable. Fix this here.
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm
(cherry picked from commit 9e7fad6c3188e148f5066e948cebba19f8682765)
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm
Services: Kea DHCPv4/6: Add decline_probation_period and set lower default to mitigate faulty client implementations to consume the whole pool (#10294)
* Services: Kea DHCPv4/6: Add decline_probation_period and set lower default to mitigate faulty client implementations to consume the whole pool.
* Use isSet() since 0 is allowed
