In this section you can set several system network related settings.
General
Hostname and domain settings.
Interfaces
Only network interfaces that have been configured via the web interface aredisplayed in the data table. If this panel is empty right after theinstallation the automatic synchronisation of the interface configurationthat was done by the installer. In this case simply start to configurethe interfaces via the web interface.
The dashboard contains a network widget that displays the current statusof the interfaces.
Ethernet
Just select DHCP or static. openmediavault is a server so the recommended settingis to have static IP address, if you have a proper network infrastructure(separate router and switch). In a reboot, if the router fails to bootyou can still access the web interface through the switch bridge. If the switchalso fails you can use a direct Ethernet connection with the static IPaddress assigned to the server NIC.
Do not leave DNS setting empty; it is essential for fetching updates.A common value is to use the same IP address as the gateway. If unsure,just use google DNS 8.8.8.8.
- Wake on LAN (WOL)
This enables WOL in the kernel driver, make sure the NICs supportsthis and the feature is enabled in BIOS.
Wireless
The configuration window displays the same IP configuration fields asEthernet, plus the relevant wireless values: SSID (the wireless networkname) and the password.
Whenever possible, use Ethernet for a NAS server. Wireless should not beused in a production server; this feature is intended for extreme casesonly.
VLAN
If your network supports VLAN, just add the parent interface and the VLANid.
Bond
The configuration window provides all available modesfor the bond driver. To configure bonding, is necessary at least twophysical network interfaces. The web interface allows the selection of lessthan two. This is by design for configuration purposes. The workflowis as follow for dual NICs:
If the primary NIC is already working either by the installer, configure it through the web interface as static. If set as static using the same IP address given by DHCP, it should not be necessary to re-login to the web interface.
Click
Network | Interfaces | Add | Bond, select the second available NIC, select the bond mode, fill the IP field and subnet mask values, leave gateway and DNS empty. Save and hit apply.Log out and access the web interface using the new IP address assigned to the bond interface created.
Now select the primary interface configured through web interface in the first step, and delete it. Save and hit apply.
Select the newly created bond interface, click edit add now the physical nic that was deleted from the step before should be available to select. Save and hit apply.
The dashboard should now report the bond interface information (including speed).
Note
802.3ad LACP (Link Aggregation) mode only works if physical interfaces are connected to a managed switch that supports aggregation.
Is not possible to achieve 2GBit bandwidth (or more depending on the number of NICs) in a single client using LACP, even if the client also has a LACP-bonded NIC or 10Gbit card; there is no multipath support in Samba or other openmediavault services in the way Windows Server has for file sharing using SMB.
Higher speeds using link aggregation are limited by disk speed. When serving simultaneous clients make sure the physical media is capable of reaching the speed of the bonded NIC (e.g. SSD or RAID array).
Advanced Interface Configuration
Proxy
This panel configures the server proxies using system wide environmentalvariables. All software that obeys Linux proxy environmental variablesshould be able to use the proxy. This is useful for example if there aremany Debian servers in the network, when performing aptoperations, packages can be cached in the proxy if this configuredappropriately to reduce download bandwidth.
The variables name are:
http_proxyhttps_proxyftp_proxy
This settings do not configure openmediavault to act as a proxy server.
Service Discovery
Announcing services via Zeroconf/mDNS is an essential feature of openmediavault.A service will be automatically announced if it is enabled. This appliesto NFS, FTP, Rsync, SMB/CIFS, SSH or the Workbench UI for example.Plugins may also announce their service via Zeroconf/mDNS.
As this is an essential feature, this cannot be switched off in general.However, it is possible to deactivate the advertising of individualservices using environment variables.
To get a list of supported environment variables, run the followingcommand:
# omv-env list | grep ZEROCONF_ENABLEDTo enable or disable a service use this command:
# omv-env set -- OMV_XXX_ZEROCONF_ENABLED [yes|true|1|no]Finally the modified environment variable(s) must be applied by running:
# omv-salt stage run prepare# omv-salt deploy run avahi
Example:
# omv-env set -- OMV_PROFTPD_ZEROCONF_ENABLED no# omv-salt stage run prepare# omv-salt deploy run avahi
Firewall
This data table is for adding iptables rules. This can be useful if youneed to secure access in your local network. Currently it is only possibleto add rules to the OUTPUT and INPUT chains in the filter table. Theconfiguration to load the rules at boot or network restart is done by thesystemd unit called openmediavault-firewall.
To avoid locking yourself out while testing, create a cron command to run every five minutes that flushes the OUTPUT/INPUT chain. Don’t forget to delete the cron job after testing.:
*/5 * * * * root /sbin/iptables -F INPUT && /sbin/iptables -F OUTPUT
Before adding the last rule to reject all, add a rule before the reject all, to LOG everything. This will help understand why some rules do not work. The log is saved in dmesg or syslog.
Tip
When seeking support please avoid posting screenshots of the data table, this is useless because it does not give the full overview of your firewall ruleset. Instead use:
$ iptables-save > /tmp/file.txt
