Console setup not working

I agree, however for feature requests we ask users to create a Suggestion ticket so it can gather interest (voted up) from community.

Thanks!

Yep, we can assume it is working as expected.

Maybe as feature request, we can highlight the things I mentioned above, so let's recap:

• if you have access to console of the server, you will get access to the OS

• there is no easy way to take over the interface IP address, in case of lagg or bridge

• there is no way to create bridge from the console based menu

I guess i should close this ticket as behaves as intended then.

Let me know if I missed something.

So, you was right about selecting the option, I've tested that, and the console menu appeared immediately on the console.

Then I was able to set-up lagg interface. I will leave it as it is, which means, if I try to log in to the server via console, I directly got the menu, but if I use SSH I have to put my credentials, and no menu at all.

So this sounds logic, and if we can assume that, physical access to the server is monitored and restricted, this can be considered as secured option.

Maybe I'm a little bit confused because I know how pfSense do it, when the checkbox is selected, you have to enter credentials, to be able to access the menu, no matter you are in the console or via SSH.

Another thing appeared, I tried to create lagg interface by using web GUI, but without success. Let me explain you a bit more.

I have IP address like 192.168.0.12 which is set to my first interface. My second interface is plugged in, but unused, no IP address set.

So I decided to create lagg interface and assign second interface to this lag, when I tried to set IP address 192.168.0.24, I've got an error which says the IP address 192.168.0.0/24 is already in use, which is true, but I expect this configuration to be transferred from the first interface, and assign it to the lag interface. I've selected 192.168.0.24 just to avoid "address already in use" but it's looks like I cannot use the same network.

I did the same tests on my virtual machine which uses the last version of FreeNAS, and there I don't have such problem. I was able to create lagg interface in it.

So what do you think, is this is a bug or expected behavior? Because if it's expected this means, I have to use another VLAN, then access the box through it, then configure the rest of the interfaces in the vlan I want and remove this vlan. Which is a  bit over-complicating the things from my point of view.