User GuidesAPIs, SDKs & ToolsSupport FAQ
Search…
IONOS Cloud Documentation
Getting Started
Data Center Designer
Basic Tutorials
Developer Tools
Compute Engine
Virtual Machines
Block Storage
Networks
Overview
DCD How-Tos
API Reference
Networks FAQ
Managed Services
Managed Kubernetes
Database as a Service
Monitoring as a Service
S3 Object Storage
Managed Backup
Early Access
Network Load Balancer
Application Load Balancer
NAT Gateway
DBaaS - MongoDB
Legal
Privacy Policy
Imprint
Powered By GitBook
Networks FAQ

For every network interface, you can activate a firewall, which will block all incoming traffic by default. You must specify the rules that define which protocols will pass through the firewall, and which ports are enabled. For instructions on how to set up a firewall click here​

The IONOS firewall offered in the DCD can be used for simple protection for THE hosts behind it. Once activated, all incoming traffic is blocked. The traffic can only pass through the ports that are explicitly enabled. Outgoing traffic is generally permitted. We recommend that you set up your own firewall VM, even for small networks. There are many cost-free options, including IP tables for Linux, pfSense FreeBSD, and various solutions for Windows.

Yes, there are DNS resolvers. Valid everywhere IP addresses for 1&1 resolvers are:
212.227.123.16
212.227.123.17
2001: 8d8: fe: 53: 72ec :: 1
2001: 8d8: fe: 53: 72ec :: 2
​
By adding a public DNS resolver you will provide a certain level of redundancy for your systems.

Please contact IONOS enterprise support team for personal assistance and more information on how to enable reverse DNS entries.

Once a server has been provisioned, you can find its IP address by following the procedure below:
  • Open VDC
  • Select the server, for which you wish to know the IP
  • Select the Network tab in the Inspector
  • Open the properties of the NIC
    The IP address is listed in the Primary IP field.

The internet access element can connect to more than one server. Simply add multiple virtual machines to provide them all with internet access.

Users with the appropriate privileges can reserve and release additional IP addresses. Additional addresses are made available as part of a reserved consecutive IP block.

The public IP address assigned by DHCP will remain with your server. The IP address, however, may change when you deallocate your VM (power stop) or remove the network interface. We, therefore, recommend assigning reserved IPs when static IPs are required, such as for web servers.

Yes, you can. To make sure that a network interface will be addressed from your own DHCP server, perform the following steps:
  • Open your data center
  • Select the NIC
  • Open the properties of the NIC in the Inspector
  • Clear the DHCP check box
    This will disable the allocation of IPs to this NIC by IONOS DHCP, and then you can use your own DHCP server to allocate information for this interface.

We preset the subnet mask 255.255.255.255 for the DHCP allocation of public IPs. Unfortunately, this is not supported by all DHCP clients. You can perform network configuration at the operating system level or specify the netmask 255.255.255.0 using a configuration file.

DHCP configurations may fail during the installation of Linux distributions that do not support /32 subnet mask configurations. If this happens, the IP address can be assigned manually using the Remote Console.
Example
Network interface "eth0" is being assigned P address "46.16.73.50" and subnet mask "/24" ("255.255.255.0"). For the internet access to work, the IP address of the gateway (which is "46.16.73.1" in this example) must also be specified.
  • Command-line:
    ifconfig eth0 46.16.73.50 netmask 255.255.255.0
    route add default gw 46.16.73.1
  • Config file:
    Modify the "interface" file in the "/etc/networking/" folder as follows:
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).
    # The loopback network interface
    auto lo
    iface lo inet loopback
    # The primary network interface
    allow-hotplug eth0
    iface eth0 inet static
    address 46.16.73.50
    netmask 255.255.255.0
    gateway 46.16.73.1
  • Restart the interfaces:
    ifdown eth0
    ifup eth0

We presently support IPv4, and are working on implementing IPv6 in the future.

Our data centers are connected as follows:
Data center Bandwidth
Location
Bandwidth in Gbit/s
Karlsruhe (DE)
4 x 10
Frankfurt (DE)
2 x 40 & 3 x 10
Berlin (DE)
2 x 10
London (UK)
2 x 10
Las Vegas (US)
3 x 10
Newark (US)
2 x 10
Logroño (ES)
2 x 10

First, attempt to log on to the VM with the Remote Console. If this is successful, please collect the information we will need to help you resolve the issue as described below.
We will need to know the following:
  • VM name
  • IP address
  • URLs of web applications running on your VM
We will need the output of the following commands:

  • ping Hostname
  • date /t
  • time /t
  • route print
  • ipconfig /all
  • netstat
  • netstat -e
  • route print or netstat -r
  • tracert and ping in/out
  • nslookup hostname DNS-Server
  • nslookup hostname DNS-Server

  • date
  • traceroute
  • ping Hostname
The output of the following commands can also give important clues:
  • arp -n
  • ip address list
  • ip route show
  • ip neighbour show
  • iptables --list --numeric --verbose
  • cat /etc/sysconfig/network-scrips/ifcfg-eth*
  • cat /etc/network/interfaces
  • cat /etc/resolv.conf
  • netstat tcp --udp --numeric -a

We have prepared a ready-made script that helps gather the relevant information. The script provides both screen output and a log file which you can forward to us.
Use the script with the additional parameter -p
You will be able to observe the commands as they are being executed, and take screenshots as needed.

If you are using the Java-based edition of the Remote Console, please ensure that you have the latest Java version installed and the following ports released:
  • 80 (HTTP),
  • 443 (HTTPS),
  • 5900 (VNC).
The Remote Console becomes available immediately once the server is provisioned.

There is no traffic overview screen in the user interface currently.
Customers can use either Traffic or Utilization endpoints of the Billing API to get details about their traffic usage.
Traffic
curl -X GET "https://api.ionos.com/billing/:contract/traffic/?output=all" -H "accept: application/json" -H "Authorization: Basic ******"
Utilization
curl -X GET "https://api.ionos.com/billing/:contract/utilization/?type=TRAFFIC" -H "accept: application/json" -H "Authorization: Basic ******"
More information in Swagger: https://api.ionos.com/billing/doc/​

Please use the configuration below to ensure the stability and performance of the network connections on the operating system side. We suggest that you first check the current settings to see if any adjustments are necessary.

  1. 1.
    Open Device Manager
  2. 2.
    Open the network adapter section where you can see all your connected virtual network cards named “Red Hat VirtIO Ethernet Adapter”. Now open the Properties dialog and go to the “Advanced” tab.
  3. 3.
    Verify that your settings match those listed below; if not, follow the guidelines later in this guide to update them accordingly.
    • "Init.MTUSize"="1500"
    • "IPv4 Checksum Offload"="Rx & Tx Enabled"
    • "Large Send Offload V2 (IPv4)"="Enabled"
    • "Large Send Offload V2 (IPv6)"="Enabled"
    • "Offload.Rx.Checksum"="All"
    • "Offload.Tx.Checksum"="All"
    • "Offload.Tx.LSO"="Maximal"
    • "TCP Checksum Offload (IPv4)"="Rx & Tx Enabled"
    • "TCP Checksum Offload (IPv6)"="Rx & Tx Enabled"
    • "UDP Checksum Offload (IPv4)"="Rx & Tx Enabled"
    • "UDP Checksum Offload (IPv6)"="Rx & Tx Enabled"
Manual adjustments in the Properties dialog are not saved to the registry. To make any persistent changes, follow the guidelines in the following section.

Once you determine that your system needs an update (see the “Verifying current network configuration” above), one of the following actions must be taken to adjust the settings:
Online update using IONOS VirtIO Network Driver Settings Update Scripts (recommended)
The best way to update network configuration is by using IONOS VirtIO Network Driver Settings Update Scripts.
The scripts are distributed in the following versions:
  • Installer, available for download here: https://github.com/ionos-enterprise/ionos-network-helper/blob/master/WinNet-v0.1.171.0001.exe
    Installer will extract the scripts to the user-specified folder and optionally run the scripts.
  • ZIP archive, available for download here: https://github.com/ionos-enterprise/ionos-network-helper/blob/master/WinNet-v0.1.171.0001.zip
When using the ZIP archive, or not selecting script execution in the installer, scripts can be started manually by launching the update.cmd file in the root folder of the extracted scripts.
If Windows does not allow you to start the installer or update.cmd from the File Explorer window, please launch it directly from the command line.
Offline update using IONOS Windows VirtIO Drivers ISO Image (alternative)
Alternatively, use the VirtIO drivers ISO for Microsoft operating systems provided by IONOS.
  1. 1.
    Use DCD or API to add an ISO image to the virtual server you’d like to update (In DCD select the VM -> Inspector -> Storage -> CD-ROM -> IONOS-Images -> Windows-VirtIO-Drivers).
  2. 2.
    Set the boot flag to the virtual CD/DVD drive with the ISO image.
  3. 3.
    Boot your virtual server from the Windows VirtIO drivers ISO.
  4. 4.
    Open the remote console of the virtual machine.
  5. 5.
    Select an operating system from the list of supported versions. Driver installation or update will be performed automatically.
  6. 6.
    Remove the ISO and restart the VM through the DCD. Make sure that the boot flag is set correctly again.

Updating drivers
  1. 1.
    Make sure you have the latest “VirtIO Ethernet Adapter” driver package. The driver package is available in the “Drivers” folder of IONOS VirtIO Network Driver Settings Update Scripts as described above.
  2. 2.
    Open Device Manager.
    in the “File Explorer“ window right-click “My PC”, select “Properties” and then “Device Manager”.
  3. 3.
    Under Network Adapters, for each "Red Hat VirtIO Ethernet Adapter":
    1. 1.
      Right-click the adapter and select “Update driver”
    2. 2.
      Select “Browse my computer for driver software”
    3. 3.
      Click “Browse” and select the folder with the driver package suitable for your OS version
    4. 4.
      Click OK and follow the instructions to install the driver.
Updating existing VirtIO network devices
  1. 1.
    Open Device Manager
    In the File Explorer window, right-click My PC, select Properties, and then Device Manager
  2. 2.
    Under Network adapters, for each "Red Hat VirtIO Ethernet Adapter":
    1. 1.
      Open Properties (double-click usually works)
    2. 2.
      Go to Advanced tab
    3. 3.
      Navigate and set the following settings there:
      • "Init.MTUSize"="1500"
      • "IPv4 Checksum Offload"="Rx & Tx Enabled"
      • "Large Send Offload V2 (IPv4)"="Enabled"
      • "Large Send Offload V2 (IPv6)"="Enabled"
      • "Offload.Rx.Checksum"="All"
      • "Offload.Tx.Checksum"="All"
      • "Offload.Tx.LSO"="Maximal"
      • "TCP Checksum Offload (IPv4)"="Rx & Tx Enabled"
      • "TCP Checksum Offload (IPv6)"="Rx & Tx Enabled"
      • "UDP Checksum Offload (IPv4)"="Rx & Tx Enabled"
      • "UDP Checksum Offload (IPv6)"="Rx & Tx Enabled"
Please be aware that these settings will revert to old Registry values unless the full update procedure is executed as described above.

Please use the configuration below to ensure the stability and performance of the network connections on the operating system side.

Please make sure to use the MTU setting of 1500 for all network interfaces.
[email protected]:~# ip link
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 02:01:26:cb:fc:d5 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 02:01:fb:20:f1:65 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 02:01:2a:a0:e1:53 brd ff:ff:ff:ff:ff:ff
Make sure that all of your network interfaces have hardware offloads enabled. This can be done with the ethtool utility; to install ethtool:
  • For .deb-based distributions: apt-get install ethtool -y
  • For .rpm-based distributions: yum install ethtool.x86_64 -y
Once installed, please do the following for each of your VirtIO-net devices:
Replace the [device_name] with the name of your device, e.g. eth0 or ens0, and check that the highlighted offloads are in the On state:
[email protected]:~# ethtool -k [device_name]
...
tx-checksumming: on
...
tx-checksum-ip-generic: on
...
...
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: on
...
tx-tcp6-segmentation: on
If you changed any configuration parameters, such as increase MTU or disable offloads for network adapters, please make sure to roll back these changes.

Fixing persistent network interface configuration may include removing such configuration in the below files:
/etc/network/interfaces
iface eth0 inet static
...
pre-up /sbin/ifconfig $IFACE mtu 64000 <-- WRONG
/etc/dhcp/dhclient.conf (for .deb-based distributions)
interface "eth0" {
supersede interface-mtu 64000; <-- WRONG
}
/etc/dhcp/dhclient-*.conf (for .rpm based distributions)
supersede interface-mtu 1500; <-- Correct
and then restarting the affected network interfaces with ifdown eth0; ifup eth0

In all examples below, please replace the [device_name] with the name of the network device being adjusted, e.g. “eth0” or “ens6”.
Dynamically adjust network device MTU configuration:
ip link set mtu 1500 dev [device_name]
Dynamically enable hardware offloads for VirtIO-net devices. This can be done with the ethtool utility; to install ethtool:
  • For .deb-based distributions: apt-get install ethtool -y
  • For .rpm-based distributions: yum install ethtool.x86_64 -y
Once installed, please do the following for each of your VirtIO-net devices: ethtool -K [device_name] tx on tso on
Previous
Cross Connect VDCs
Next - Managed Services
Managed Kubernetes
Last modified 8mo ago
Export as PDF
Copy link
On this page
How do I set up a firewall?
How does the IONOS firewall work?
Do you have a DNS resolver?
How do I create reverse DNS entries?
What is the IP address of my new server?
How can I connect multiple servers to the Internet?
How can I get additional IPs for my server?
How are IPs assigned by DHCP?
Can I use my own DHCP server?
How do I set up DHCP during a Linux installation?
How do I assign an IP address to a Linux server manually if DHCP fails?
Which IP versions are supported?
What is the maximum bandwidth of your data centers?
What should I do if the network does not work?
What should I do if the Remote Console does not work?
Is there a detailed traffic overview available?
How can I configure VirtIO settings in Windows?
How can I configure VirtIO settings in Linux?