catch-22 with OPNsense 26.1.7_3-amd64: (opnsense) Interfaces not created at boot

[euclid]

Hi,

I updated opnsense to 26.1.7 and after the update, I see a few issues with how the *soft interfaces* (/interfaces_assign.php) are started.

Host with 2 physical interfaces, and some VLANs + wireguard interfaces.

I have an interface that is using the [legacy] ISC DHCPv4 (OPT1). because of that it is not registered in the UI. then, all the consecutive interfaces OPT2, OPT3, ... do not appear because I assume the process to start the soft interfaces at boot stops immediately on the first error [I consider this bug #1 - because one interface failed, the following interfaces are not even registered]. There is a bug #1.1 additionally, because all the interfaces were marked as enabled and prevent interface removal.

Now because I don't have these soft interfaces, my [legacy] ISC DHCPv4 does not show me the configured interfaces to move the DHCP configuration, so I cannot really solve this unless I touch the system [I consider this bug #2 - this is the catch-22]

In general the user ergonomics of the transition of deprecating DHCPv4 and move some of its parts (for better or worse) as part of the interface UI, is not well thought, and I consider this bug #3. User Interface experience lacks.

Because the interface didn't start as expected, my gateways did random things I had a system that some things work, but without me having any possibility to modify from the UI.

I've been using opnsense for 6 years. This release must have been the least quality assured release I remember.

[euclid]

Also applies in 26.1.8_5

[euclid]

looking at the configuration some interface definitions live under
```
<opnsense>
  <interfaces>
    <wan>
...
    </wan>
    <lan>
...
```
But I don't see the vlan interfaces <vlanif> mapping to <optX>. Where should this happen?

 

[euclid]

ok for some reason the <opt> entries under xml:/opnsense/interfaces were deleted. it seems it happened 4 weeks ago, but can it happen without user intervention? I don't see anything in the logs?

the plot thickens

[franco]

Interfaces not locked and reset at boot due to VM not providing the right interfaces required at boot time?

You also invent the term "soft interface" but make no effort to explain it. There's not much magic involved in interface management.


Cheers,
Franco

[euclid]

Apologies for the confusion I spent about 3 hours on my day off tracking down this issue. To clarify (my misnomer); by "soft-interfaces" I meant the logocal interfaces that OPNSense is mapping   for already existing interfaces devices/interfaces and is using for configuration (eg a VLAN to OPTx). OPNSense is calling those plain interfaces, from the top of my head, the description is not precise because some of the items that it lists under Device can be interfaces.