Note: This is a temporary workaround whilst we work on a more permanent solution for this.This FAQ applies for the following OSs only:
| Operating system | Version |
|---|---|
| Ubtuntu | Ubuntu 20.04.6 LTS |
| Ubtuntu | Ubuntu 22.04 LTS |
| Ubtuntu | Ubuntu 24.04 LTS |
| Debian | Debian 11 |
| Debian | Debian 12 |
You might notice that the second network interface (NIC) may not activate automatically once you've enabled the `Split-NIC` feature.
To activate the second NIC, you'll need to manually configure it. SSH into your server and execute the following command:
printf "[Match]\nName=ens4\n\n[Network]\nDHCP=yes\n" >/etc/systemd/network/ens4.network
Once you've made that change, restart your networking service with:
systemctl restart systemd-networkd
You can use `ip addr` to check the LAN interface (`ens4`) is configured correctly.
If you experience issues with DNS or the routing table (e.g., private NIC traffic interfering with public NIC traffic), or you would like to customise DNS behaviour for the private NIC, you can use the following alternate configuration:
(Note: If you have a custom DNS server within your VPC, you would need to change the below to `UseDNS=yes` in addition to manually defining the DNS server's IP in the appropriate configuration file, such as `/etc/resolv.conf`)
printf "[Match]\nName=ens4\n\n[Network]\nDHCP=yes\n\n[DHCP]\nUseDNS=no\n" > /etc/systemd/network/ens4.network
Restart the networking service as before:
systemctl restart systemd-networkd
After applying, verify that the LAN interface (`ens4`) is configured correctly using `ip addr` or `ip route`. Check that the private NIC traffic and DNS settings are behaving as expected.
If you require assistance, feel free to submit a support ticket at our helpdesk here: Submit a ticket | BinaryLane