system: service widget based on community feedback #10553
Tiles are still there but markup is more "native" to the dashboard.
Header is back. The columns have a bigger minimum size.
It all leads to being less readable, useful and compact. Not sure
about it.
modify the serializeToConfig to set the uuid of the new network ident… (#10600)
* modify the serializeToConfig to set the uuid of the new network identifier instead of the internal random generated uuid
* Update src/opnsense/mvc/app/models/OPNsense/Interfaces/NetworkInterface.php
Co-authored-by: Ad Schellevis <AdSchellevis at users.noreply.github.com>
* remove the exception if the node reference is not found
---------
Co-authored-by: kemoycampbell <ksc2650 at rit.edu>
Co-authored-by: Ad Schellevis <AdSchellevis at users.noreply.github.com>
interfaces: patch runInterfaceRegistration() into device applies
Note that configure should run before registration in order to pick up
additional runtime information in the assignment list cache (if applicable).
Deleting doesn't clear the cache, but that's a problem for later.
interfaces: patch runInterfaceRegistration() into device applies
Note that configure should run before registration in order to pick up
additional runtime information in the assignment list cache (if applicable).
mvc: create runInterfaceRegistation and use it from all required spots
1. Fix the stale cache after applying new interfaces/devices in existing paths
2. Allow to call it from controllers who do not use invokeInterfaceRegistration()
Needs to be patched into Device apply/reconfigures next.
MVC:UserException - add some exception types and handle them in the base template, closes https://github.com/opnsense/core/pull/10430
Although we can debate about the http status codes (kept the standard one at 500, warning and info as 200), the idea is to add some glue for the frontend so it knows what we mean and can represent the dialog based on its type.
mvc: create runInterfaceRegistation and use it from all required spots
1. Fix the stale cache after applying new interfaces/devices in existing paths
2. Allow to call it from controllers who do not use invokeInterfaceRegistration()
Needs to be patched into Device apply/reconfigures next.
interfaces: patch runInterfaceRegistration() into device applies
Note that configure should run before registration in order to pick up
additional runtime information in the assignment list cache (if applicable).
interfaces: permit a vlan device as bridge member, resolve VLAN devices indirectly via interfaces_configure() (#10584)
* interfaces: permit a vlan device as bridge member
* interfaces: resolve VLAN devices indirectly via interfaces_configure()
This also adds device creation for parents so that we ca naturally
resolve QinQ and VLANs on bridges.
---------
Co-authored-by: Franco Fichtner <franco at opnsense.org>
mvc: create runInterfaceRegistation and use it from all required spots
1. Fix the stale cache after applying new interfaces/devices in existing paths
2. Allow to call it from controllers who do not use invokeInterfaceRegistration()
Needs to be patched into Device apply/reconfigures next.
interfaces: resolve VLAN devices indirectly via interfaces_configure()
This also adds device creation for parents so that we ca naturally
resolve QinQ and VLANs on bridges.
firewall: pluginify filter_core_get_default_nat_outbound_networks() #10539
Bring a bit of structure into this legacy code: move the "plugin"
parts to its own "oubound_net" run target, collect it with the new
filter_auto_source_nat() and just iterate over it from the code
that needs this. We do all of this to provide a possible configd
target to expose the actual automatic rules skeleton to the MVC
source NAT GUI.
# pluginctl -r outbound_nat
{
"pf": {
"wan": {
"lan": "LAN networks",
"lo0": "Loopback networks",
"127.0.0.0/8": "127.0.0.0/8"
}
}
}
interfaces: defer vlan creation when dependant on bridge till after the bridge exists. This needs two separate vlan configuration runs to keep the old boot order unchanged.
