9.3 Second interface on same subnet, cannot add from GUI

[Vijay]

When try to configure second network interface which is connected to the same subnet, GUI show a error. On the command line (text-based) menu, It can be created. (Work around is to use the text-based console menu.

Ex.
Interface 1 IP is 192.168.1.10
Cannot add 192.168.1.11 to interface 2 from GUI.

(While this seems not a normal use case, it may be useful to increase the bandwidth, by assigning 2 n/w interfaces in the same network.)

 

[gpsguy]

Just because Windows lets you do it, FreeNAS doesn't.

See: https://forums.freenas.org/index.php?threads/nics-on-the-same-network.12608/

 

[cyberjock]

https://forums.freenas.org/index.php?threads/multiple-network-interfaces-on-a-single-subnet.20204/

What you are doing is bad networking practices and shouldn't be done, but you are doing it. Expect a "we told ya so" when you create a thread later with some totally unexplainable network problem. :)

 

[Vijay]

Thank you. Look like FreeNAS decided it is bad practice. So be it.

However in real world, if you have 2 interfaces, you can bind, nfs to one interface, iscsi to another and use successfully, no issues. I can see how they can become bad practice in a appliance type interface.

(I thought it is a bug, as Command line menu still let you do it. Should the command line be fixed then?)

 

[gpsguy]

Even in your last example, I would separate the traffic onto different subnets.

For my production VMware (ESXi) cluster, I have at least 3 subnets. One for LAN, another for iSCSI, and yet another for vMotion traffic.


Sent from my phone

 

[Vijay]

Agreed.