Hi forum!
2 years using OMV and first post!
...here we go:
I got an old install box, upgraded from 0.5 to 2.0 up and running in production.
Being Debian experienced, and coming from 0.5, all network setup has always being done via cli /etc/network/interfaces... that included a LACP bondwith a CISCO switch.
Recently that box was put into less stressing load and put in a simple, single nic, setup... although it retains 3 its Gb NICs.
So I though: "what does the gui offers to play with with 3 NICs?" .... being the answer: nothing.
Out of the 3 NICs (1 layer1 down, 2 layer2 up, of which only one is layer3 set up and running) only 1 interface appears on the GUI: the one up without layer3 setup...
By looking around other boxes, I realice That GUI seems to apear disabled/locked to setup some interfaces, or when opening it up (for instance, opening form for a bond interface) it shows empty.
So I suspect and feel I'm doing things WRONG, relying too much on the classical cli, and creating a gap between OMV "database" setup and currently running setup.
I do not find anywhere on the forum a clue on what can be happening... (most entries are about non-working scenarios, whereas here it all works)
What am I missing? Is OMV using something similar to early Debian/Ubuntu cli conflictive network-Manager? Why seem interfaces at GUI to be uneditable/locked?
I would like to do things as OMV developers seem to have designed: using full GUI, being able to manage and control networking from it in order to have "good practices" OMV usage.
Thank you for your patiece....
and best regards!