Hi,
I ran into this problem quite a lot already, particularly when running opnsense as a VM and when changing underlying virtualized interfaces which is well why you run it virtualized ;)
For explanation let's assume I have 4 interfaces, 1 passthrough physical, 3 virtual ones (vtnet0-2).
Now we remove vtnet1:
How opnsense behaves today:
- opnsense forgets all interface assignments and starts randomly assigning interfaces similar like when on initial setup
--> In many cases you end up with a totally unusable opnsense installation unless you boot into console and start manual interface assignment again
How opnsense should imho behave:
- vtnet1 is removed assigned settings are deactivated (or removed best if it's asked somewhere) the remaining interfaces remain assigned as they were
--> Like this - one can deal with the specific changes only but opnsense remains usable if not the core LAN interface was removed
Thanks for considering. Though I'd write it down before I forget it again ;)
It's been discussed before. Search the forum for ethname.
Example: https://forum.opnsense.org/index.php?topic=27023.msg160714#msg160714
Short of it, is a shortcoming of the underlying OS. Ethname is a tool that could be used as a workaround.
If you want it considered to be included in base and integrate as part of the core, you might want to raise a suggestion in github.
Quote from: cookiemonster on January 15, 2024, 11:42:33 AM
It's been discussed before. Search the forum for ethname.
Example: https://forum.opnsense.org/index.php?topic=27023.msg160714#msg160714
Short of it, is a shortcoming of the underlying OS. Ethname is a tool that could be used as a workaround.
If you want it considered to be included in base and integrate as part of the core, you might want to raise a suggestion in github.
Thanks, didn't know. I will do that laters.
One of those, good to know tidbits.
IIRC there is ongoing or even completed work in the FreeBSD base system. I just can't find the reference right now.
Quote from: cookiemonster on January 15, 2024, 11:59:11 AM
One of those, good to know tidbits.
Yeah, it can cost you quite some headache when it hits you for the first time. After you know it you can resolve in due time. Behind the scenes though it seems to remain a bit messy since opnsense retains the settings but does not give you the means to change it from the UI. Some of the settings cause issues.
Quote from: Patrick M. Hausen on January 15, 2024, 12:00:00 PM
IIRC there is ongoing or even completed work in the FreeBSD base system. I just can't find the reference right now.
Thanks. It could help to mention that if you can find it again.
Found it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=118111
Unfortunately it looks like it's stalled. It came to my attention by the ticket state change by Mark Linimon last week.
Kind regards,
Patrick
Quote from: Patrick M. Hausen on January 15, 2024, 12:22:52 PM
Found it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=118111
Unfortunately it looks like it's stalled. It came to my attention by the ticket state change by Mark Linimon last week.
Thanks!
Here it is:
https://github.com/opnsense/core/issues/7141
Feel invited to add and comment to my attempt of feature request.