Hi, just did the jump from core to scale (following the recommended path through the gui along versions, finally arrived at 25.10.2.1).
Everything smooth so far, set up a few apps, assigned the old jail IPs as additional ones to the nic and containers, everything worked.
But after a reboot, truenas could not connect to the update or app catalog.
Digged a bit deeper, just to find out the order of IP addresses was mixed up. My main IP was on top in config screen, but IP addr showed it as secondary and a random other one as primary. Same for the state aliases view in console config. This leads to missing default gateway and the connection seems broken.
Removed all addresses through console setup except the main one, everything working again.
Added a second address, working until reboot and mix-up again.
May I have found a bug there?
Yes, I know about the macvlan path, but I would assume, that the behavior is neither intended, nor expected.
Judging from a short (non professional) research the order seems to be not correct to set the IPs, I don’t know why. My expectation would be, that the first IP in the list is set as first and main IP.
Are you adding these aliases through the command line or using the UI?
The order of IPs listed as aliases for a single interface should not matter.
Given the partially masked long IP ending with 64 in your GUI screenshot I am guessing you’re also using IPv6, I admit I do not have a lot of experience with that, but it should not cause issues like you describe.
It really sounds like you do not have a gateway properly defined, none of your screenshots show what the status of that (or DNS) is.
Again, a screenshot of your network screen showing at least the Interfaces and the Network Configuration elements would be helpful. Mask any internet facing IPs if you must.
If you want to ask the developers to consider the order the IPs are in you can make a feature request post here in the forum, it’s a special type of post that adds a voting button and lets the developers judge what the general interest in the feature is, to better allocate resources. Make sure you include a good reason.
Try adding the primary address with a /24 and all alias addresses with a /32 netmask. That’s the recommended way for multiple addresses in a single subnet with FreeBSD. Maybe Linux works the same.
