Network

The network connections should be configured as early as possible. You can find the settings for the network adapters in the context menu under Antcas Control ▸ Infrastructure ▸ Server ▸ Network.

Note: The settings are applied immediately after saving, but not permanently stored. If an incorrect configuration was made, it can be reset by restarting the server.

Please note that each interface requires its own subnet. The following settings are invalid:

eth0: 192.168.1.100/24
eth1: 192.168.1.101/24

The server cannot assign packets to a unique routing in this way. In addition, only one standard gateway can be defined.

In the Setup, you can check the IP settings.

Important: If a DHCP client is used and the IP address changes, it cannot be guaranteed that all services will adopt it. A restart of the services may be necessary. Therefore, it is not recommended to use the server as a DHCP client.

Adapter Names

There are different adapter names, which in classic mode are always eth0, eth1, wlan0, usb0, etc. In modern mode, these are named after PCI address and slot, e.g., enp4s3 (ethernet port 4 slot 3). Local network adapters start with eno# (ethernet onboard). USB devices are addressed with the complete MAC, e.g., wlx8416f9150734 (wireless mac 84:16:f9:15:07:34). Various servers have their own profiles that specifically address all network ports. This ensures consistency with the server's labeling. The method of addressing cannot be set manually.

Note: In this documentation, the network names are mostly described in classic mode.

Wireless Networks

Antcas Control also supports the use of wireless networks. However, we recommend using them only from Core 2 onwards. Antcas Control can list the SSIDs of all networks if the adapter has been activated. To do this, after saving, you need to focus on the SSID field. The search may take a short moment.

Hostname and Alias

The hostname defines the server name of an individual network interface. An alias allows the same interface to be additionally accessible via a public DNS server under an alternative name. Aliases are enabled by default and can be disabled per interface via a checkbox.

The hostname is used for the mDNS service so that the device can be automatically detected in the local network. Both the hostname and the alias are considered when creating and assigning the certificate, allowing secure connections via both names.

An alias can be used multiple times. In this case, all associated IP addresses are combined. This allows the same connection to be used via multiple network interfaces under the same name. Note that establishing the connection may take more time depending on the number of addresses used.

Note: Enabling or disabling an alias can take some time until the DNS entries are available and the certificate has been downloaded and assigned. Also note that the certificate cannot be created or renewed without an internet connection.

The URL of the alias consists of the subdomain eth0-randomid and the domain .local.antcas.com. This way, Antcas Control can be accessed as shown below. The random ID corresponds to the same ID used by the DynDNS service. Additionally, a prefix is used that can be manually configured. Characters such as _ (underscore) or . (dot) are not allowed. Instead, a - (hyphen) should be used.

https://eth0-randomid.local.antcas.com:10000/

MTU

The MTU (Maximum Transmission Unit) defines the packet size of the interface. These should ideally be smaller than the nested values. If a VLAN is used, the MTU of the VLAN can be at most the size of the physical interface. The default value is 1'500.

The MTU should definitely be chosen smaller for VPN connections than the value of the interface used. For most VPN connections, a value of 1'400 is recommended.

Gateway and Route Metric

Each interface can have one gateway set. This gateway is used to reach all networks that are not directly accessible (default route).

Additionally, a route metric can be specified per interface under the Advanced tab. This determines the priority of the interface when multiple routes are possible. The rule is: the lower the metric, the higher the priority.

If multiple gateways with identical metrics are configured, they can be used in parallel by the system. However, this does not correspond to an explicit load distribution and depends on the internal routing logic of the Linux kernel.

If the metric is set to Automatic (no value), it is assigned by the system. The metric for each active network interface is increased step-by-step by 100. The order follows the interface sequence of the infrastructure: the topmost interface receives the smallest metric and thus has the highest priority.

Telephony

Under the Network settings, there is a tab for Telephony. The properties are necessary for visualization and are further explained in the chapter Telephony under WebRTC.

Tagged VLAN According to IEEE 802.1Q

VLANs are directly supported. Note that network settings can become invalid with incorrect configuration and the server may no longer be reachable.

Note: Not all LAN interfaces support VLAN. Test the VLAN configuration on the server before deploying it.

The VLAN ID is written after the adapter address. For example, eth0.10 corresponds to the ID 10 (tagged) of the adapter eth0. The valid range for IDs is from 1 to 4'094. The ID 0 corresponds to untagged and is the network interface itself. It is recommended not to disable this.

Recovery

Recovery can be done using a USB stick. For this, the label must be ETH_RESET, and then the server must be restarted. All IP configurations are reset to factory settings.