User Tools

Site Tools


This is an old revision of the document!

Network Settings

The following additional Network configurations are not mandatory for the operation of NAS4Free, but may be required in some network configurations.

Ethernet Interface properties

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: 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): Just enter your interface name (go on the Interface: Assign page for display the name of your card: fxp for example).

Additional Ethernet interfaces

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 NAS4Free or to access the shares, so it can be a useful redundant interface to NAS4Free 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 NAS4Free, ensure that the additional interfaces are installed when NAS4Free 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 NAS4Free.

Clicking on the to add the additional Interface called OPT1.

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 NAS4Free to ensure the additional interface is recognised. You can reboot NAS4Free via the Diagnostics/Reboot System page.

Once NAS4Free 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.

  • Enter a description for the interface.
  • Enter the IP Address and Subnet for the Interface and click Save.
  • Change the MTU size if you need/want to. We recommend leaving this blank unless you know what you are doing and have a requirement to change the MTU size.
  • This new Interface name in the Navigation Tree and other displays like ping/traceroute, etc will be updated.

A reboot is not required.

Security Note on additional interfaces: NAS4Free does not provide any routing between Ethernet interfaces, so any potential security risks of ‘joining’ two networks via NAS4Free should be limited. But, there is always the potential for virus infected files stored on NAS4Free 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 NAS4Free, 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 NAS4Free and then that is access by another user on the other network.

Wireless LAN interfaces

If a Wireless NIC is identified by the NAS4Free server, then you can configure this interface to access NAS4Free.

Note: Do not configure a wireless interface as Primary network interface for FreeNAS.

(More detail to follow here)

Default Gateway

If you have a Default Gateway in your network, you may need to configure the Default Gateway within NAS4Free. You may also need to configure the Default Gateway to permit NAS4Free to connect to NTP time servers.

Using the Navigation Tree on the Left Hand side of the screen, select Interfaces/LAN

Configure the address your Default Gateway. (, in this example) If you change your Default Gateway, or select Save at this point, you will be prompted to reboot the NAS4Free server with the following message:

“The changes have been saved. You must reboot your NAS for changes to take effect.”

To Reboot the NAS4Free server, Expand the Diagnostics item in the Navigation Tree, select Reboot System and select Yes. The NAS4Free PC will reboot.

Once the NAS4Free server is rebooted, again point your web browser at the FreeNAS PC. You should be presented with the System Status page again. Login if prompted.

Static Routes

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 NAS4Free, then additional static routes may be needed in FreeNAS 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 and its default gateway is, my Internet router. I have another router with a local address of that is connect to another network ( In order for FreeNAS to direct traffic to the network, a static route is configured directing any traffic to the (local router to its remote network) via the LAN NIC.

documentation/setup_and_user_guide/network_interface_lan.1335281080.txt.gz · Last modified: 2018/07/08 17:48 (external edit)