The following additional Network configurations are not mandatory for the operation of XigmaNAS, but may be required in some network configurations.
To configure advanced interface properties, go to the Network LAN Management page:
On this page you can configure IP addressing type: DHCP or static. Note: If you use DHCP the Gateway will be provided by your DHCP server. If you are not using DHCP you must set the Gateway manually and this should have been done during the initial server configuration at the console. In both situations(Static or DHCP) you must set the DNS manually.
MTU size: Useful for enabling Jumbo frame support (if your NIC support it). You can check if your NIC card supports jumbo frame from this web site (FreeBSD manpage): http://www.freebsd.org/cgi/man.cgi Just enter your interface name (go on the Interface: Assign page for display the name of your card: fxp for example).
In addition to the LAN interface, additional Ethernet Interfaces can be defined, if required. This can be either wired Ethernet interface or Wireless interfaces. See section 5.2.3 for more information relating to wireless LAN interfaces.
The additional interfaces may be used to administer XigmaNAS or to access the shares, so it can be a useful redundant interface to XigmaNAS for either function.
The additional Ethernet Interface can be within the existing LAN subnet or on a completely different subnet depending on your networks configuration. Where the additional interface is on a different subnet to that of the LAN interface, additional static routes may be required to facilitate connections to the other subnet, for example, the other subnet’s gateway and beyond.
Before adding an additional Ethernet Interface to XigmaNAS, ensure that the additional interfaces are installed when XigmaNAS is booted.
To add an additional interface, go to the Interfaces (assign) page. If your additional Ethernet interface is recognised, you will have a alongside the standard display, as shown below. If you do not have a on this display, your interface is either not correctly installed or not recognised by XigmaNAS.
OPT1 is the default name of the interface, and this can be customized. Once OPT1 is configured you will notice an additional level under Interfaces (assign) called OPT1.
Click Save and reboot XigmaNAS to ensure the additional interface is recognised. You can reboot XigmaNAS via the Diagnostics/Reboot System page.
Once XigmaNAS is again operational, you can configure the OPT1 interface and rename it to something more relevant to your network.
As per the display shown below, Click the Enable Optional 1 interface check box.
A reboot is not required.
Security Note on additional interfaces: XigmaNAS does not provide any routing between Ethernet interfaces, so any potential security risks of ‘joining’ two networks via XigmaNAS should be limited. But, there is always the potential for virus infected files stored on XigmaNAS to be accessible from either network, and so, it is important that a current and up to date anti-virus application is able to scan all files stored on XigmaNAS, from time to time. Is not a case of viruses ‘jumping’ from one network to another, its more likely that a user on one network will save a file on XigmaNAS and then that is access by another user on the other network.
In most LAN environments, a single LAN interface will be used (the LAN interface) and its default gateway will provide the interface to other networks. Where multiple LAN interfaces are configured in XigmaNAS, then additional static routes may be needed in XigmaNAS to permit network traffic to the other networks. Note: This configuration is usually not required unless you have to direct traffic from one subnet via another.
In the example below the interface ‘LAN’ has the IP Address of 192.168.80.130 and its default gateway is 192.168.80.254, my Internet router. I have another router with a local address of 192.168.80.2 that is connect to another network (10.1.1.0/24). In order for XigmaNAS to direct traffic to the 10.1.1.0/24 network, a static route is configured directing any 10.1.1.0/24 traffic to the 192.168.80.2 (local router to its remote network) via the LAN NIC.