Disable/Enable Checkbox for Network Interfaces in the UI

Problem/Justification
Please add a simple checkbox or toggle in the network interface configuration UI to administratively disable an interface without deleting its configuration.

Today, if an interface should temporarily not be used, the available options are often more disruptive or less intuitive than they need to be. A UI-level “Disable interface” option would make interface management safer, faster, and clearer, especially in systems with multiple NICs, VLANs, bridges, LAGGs, backup links, or temporary testing configurations.

This should ideally keep the interface configuration stored, while setting the interface to an administratively down state until it is enabled again.

Impact
This would improve usability, reduce configuration mistakes, and make troubleshooting and change management easier. It would be especially valuable for administrators who want to temporarily disable an interface without removing IP settings or other related configuration.

A disable/enable control would also help avoid unnecessary reconfiguration work and reduce the risk of mistakes when restoring a previously used interface.

User Story
As a TrueNAS administrator, I want to disable a network interface from the UI without deleting its configuration, so that I can safely perform troubleshooting, maintenance, failover testing, and temporary network changes with minimal risk and effort.

  1. Troubleshooting network issues without losing configuration
    When diagnosing routing problems, duplicate connectivity paths, VLAN issues, or link instability, it is very useful to temporarily disable one interface while keeping its full configuration intact. Recreating the interface settings afterward is unnecessary work and increases the risk of configuration mistakes.

  2. Safe maintenance and migration between NICs
    When replacing cables, switches, transceivers, or moving services from one NIC to another, administrators may want to disable the old interface temporarily while keeping it ready as a rollback option. A simple disable checkbox makes this much safer than deleting or manually rebuilding the interface later.

  3. Multi-NIC systems with backup or standby links
    Systems with more than one NIC often have interfaces configured for planned future use, backup connectivity, or staged migration. Being able to keep these interfaces configured but administratively down is operationally very practical.

  4. Preventing accidental traffic over the wrong interface
    Sometimes an interface should remain configured but must not participate in traffic until a maintenance window, switch-side change, or firewall rule is in place. A disable checkbox makes that intent explicit and reduces the risk of accidental use.

This is a small UI feature, but it would provide a very high practical value in day-to-day administration. It aligns with common network management expectations: administrators often need to keep interface settings saved while controlling whether the interface is administratively active.