- Joined
- Oct 29, 2016
- Messages
- 1,506
technically SCALE isn't enterprise level yet. they currently recomend against using it for production.enterprise level software
technically SCALE isn't enterprise level yet. they currently recomend against using it for production.enterprise level software
I know how the system normally sets an alias. My issue is nothing is being set when attempting to do so.Folks, what are we discussing here? The OP correctly identified that one needs to create an alias for a static IP address and that nothing happens after clicking "save". So far so good.
The missing piece is that after that step you need to
- click "test settings" in the upper left region of the UI and then
- within 60 seconds reconnect and login to the UI using the new static IP address and then
- click on "save settings" in the dialog box presented after login
Worked perfectly well every time I tried it and is part of the anti lockout two step process of applying and saving changes to the network settings. This part of the UI in SCALE and in CORE is really pretty damn good! One can even change the 60 seconds timeout to e.g. 300 in case one wants an LACP setup and needs to reconfigure the switch after the NAS. That also worked way more than once, here.
Yeah, that does appear to be my issue. However, by using DHCP on one interface and an alias on another I am able to get it to do just that. The issue only arises when I try to turn off DHCP and set an alias on both interfaces.From an earlier reply it looks like you’re trying to configure multiple interfaces in the same subnet.
That’s generally a no in TrueNas.
My goal with this is some simple load balancing and allowing for redundant paths to manage the server. Mainly, to learn about what I can and can't do with a network really.Anyway even with DHCP this is an invalid configuration according to all IP standards. One subnet, one interface. You can put as many addresses as you like on one as aliases.
What are you trying to achieve with that configuration?
In which case, assuming you have a managed switch you can configure, LACP is what you’re looking for.My goal with this is some simple load balancing and allowing for redundant paths to manage the server. Mainly, to learn about what I can and can't do with a network really.
It's not "bad". It doesn't work. It violates IP addressing and routing standards. Simple as that. A host is supposed to pick one connected interface for any locally connected network.Does anyone have insight into why double interfaces to the same subnet is bad?
Thank you very much for the recommendation.For a solid background understanding of networking I can recommend "Computer Networks" by Andrew Tanenbaum. You should also be able to find a used older edition for cheap, which will likely be more than enough.
cli --menu
to clear the alias off eno1 and force one onto br50 and just stop using DHCP on it entirely. This decision came after plugging in my console cable to poke at the switch and my desktop suddenly getting a BSOD and the console cable getting crazy hot. Cheap piece of junk. New one on the way. Sign...