TrueNAS 12.0 Bug - DHCP Setup Issue with Multiple Network Interfaces

This issue makes the whole NAS unreachable from the network after a couple of hours.

Here is the detailed traceback for search indexing:
```
Error: Traceback (most recent call last):
return await f(*args, **kwargs)
await self.__check_dhcp_or_aliases()
raise CallError(
```

[Burrski]

Bug is still around in TrueNAS-13.0-U3.1. Glad to know I'm not crazy or doing something wrong. Thanks for the video!!!

[SoapNSuds_]

super simple. just change all the interfaces BEFORE hitting test and it will work. just tried on a fresh install TrueNAS-13.0-U4

[BitWords]

Is it concerning that your submitted bug was marked: "Engineering Closed". This seems counter to the jira discussion which addresses how it can easily occur to new installations. The the hover definition of Engineering Closed reads: "This feature could not be added to our roadmap at this time."

[Larryt]

been fighting an issue trying to setup my 2nd NIC and running into this. I was able to resolve the problem by deleting the settings for both of my interfaces in the console. setup my first interface as dchp for the web gui. back in the gui i set a static ip for my 2nd NIC ( i use this as a direct connection to virtualization server via 10gbe). after a reboot both ip's show up on the console and the change in settings seems to be permanant.

[raphaelcarrier]

its completely stupid, they need to change that behavior

[nanoman]

This is still an issue for me...in 2022. Bummer