Scale is still rather buggyThe last time i wanted to change the IP of a secondary card it also resetted the primary connection. So, i never could confirm the change. So, i am not suprised about this issue.
But maybe you can add the ticket number here.
What, specifically, is the issue? Setting a static IP on an interface is simple enough, if not very intuitive: you'd set it as an alias for the interface in question, complete with its netmask, e.g.,Having a Similar Issue here
10.10.0.50/24
.Did you watch the video example of the issue in the OP ?What, specifically, is the issue? Setting a static IP on an interface is simple enough, if not very intuitive: you'd set it as an alias for the interface in question, complete with its netmask, e.g.,10.10.0.50/24
.
But you're right, the TrueNAS (especially SCALE, but also CORE) docs suck. And what's sad is that they've gone to having about the best docs around in the era of 8.x and 9.x, to a pretty-but-useless "documentation hub".
Clicking "Save" just hangs and does nothing. Likely (another) SCALE GUI bug.What, specifically, is the issue?
I've rebooted a couple times and it's still working.Just so as it doesn't catch you unawares, this will not persist and will go away when you reboot the system.
I've rebooted a couple times and it's still working.
You seem to be trying to put 2 NICs on the same logical network - something which is very bad practise. I wonder if thats the issue and that TN is getting confused bu the "bad" networking
Agree that this is not the preferred method of configuring a static IP but doing it through TN Scale's web console wasn't working.Fine, then I'll go with a more general "Thar be dragons here", because this is not the authoritative source for this information, and there are definitely things that will cause this file to be regenerated from the configuration database's settings.
I did try to do it while first installing the system via the installer's CLI and that wasn't working either. I'm wondering if doing that may have caused issues with the system after it was fully installed and up and running?
editing the /etc/networking/interfaces file is a valid way to set a static IP via Debian
I would have liked to configure it through the setup app or web app but it didn't work (There are some other posts attesting to the same issue on the board as well).Anything done via the console's netcli should be safe; it's part of the system firmware and has access to the configuration database.
Only problem with that logic is that this isn't Debian. TrueNAS is not some weird Debian "distro"; it's an appliance firmware, and is not expected to work like Debian, even though Debian might be the original basis for large parts of it.
Noob here... I was able to create a static IP from the console. Was not able to make it stick via the web GUI. Thanks for all of the advice and replies.Hi Guys
I've opened a bug report (NAS-120187) regarding the attached example video highlighting issues with setting a static IP address
If I am doing something wrong a pointer would be greatly appreciated
View attachment 63233