Zabbix Appliance network interface not working under VirtualBox

[bmercer]

I'm not able to get a working network interface on a Zabbix VMDK appliance under VirtualBox.
I had this problem first with the previous version, and now that 4 is released I tried it again with the same result.
I'm trying to use a bridged adapter, but have had the same problem with other adapters.
Here's a screenshot showing ifconfig -a and lscpi output.
I didn't see any errors in dmesg.


Is the appliance not supposed to be a turnkey option for testing?

[bmercer]

I've tried a few different approaches to launching a Zabbix appliance on VirtualBox with no success. Is VirtualBox not a supported platform?

[Atsushi]

Since the network interface name may be different depending on the environment, it is necessary to set the network interface to be used according to the environment.

When I started the Zabbix 4.0 appliance on VirtualBox, in my environment enp0s3 was the interface name for external network access.
By default, since it is ens33, the network device will not be valid as it is.

Please change the setting file and restart the network service.

$ sudo su -
# vi /etc/network/interfaces

default:

auto ens33
iface ens33 inet dhcp

change to:

auto enp0s3
iface enp0s3 inet dhcp

and restart networing.

# systemctl restart networking

[bmercer]

I tried editing the network interface, but had no luck, and gave up for a while.
I revisited the project last week, and after trying to get an appliance running using various download types, (the ISO version, the RAW version, the LiveCD ISO, and the .vmdk version all failed) I finally got it to work by using the OVF version of the download.

Downloaded and imported the OVF, and all networking issues were resolved without any configuration changes.
No other options worked.

If anyone else is having similar problems, start with the OVF edition

[DeltaCentral]

On Virtual Box I managed to get both Server/Proxy working by using the ISO installer and also ensuring that the following settings were setup in Virtual Box before installing.

VirutalBOX (Settings)

Type: Linux
Version: Ubuntu (64bit)

Network Settings
Attached To: Bridged Adapter

Advanced (Under Network Settings)
Promiscuous Mode: Allow All

:::::::::::::::::::::::::::::::::::::::::::::::::: :::::::::::

Then mount the ISO installer, install the server you require, once installed, login at the prompt, use the ifconfig command and see if you get an automatic IP address first. If you do then edit the interface settings and set to static, see below in bold what changes you need to. Once done, use the command sudo reboot for the changes to take affect. Then use the ping command from another terminal on the network to see if you can see the machine.

# The Primary Network Interface
auto ens192
iface ens192 inet static
address 192.168.253.50
netmask 255.255.255.0
network 192.168.253.1
broadcast 192.168.253.255
gateway 192.168.253.1
dns-nameservers 8.8.8.8 8.8.4.4

Also not that for (DNS-NAMESERVERS) do not use the primary gateway address as I found on my setup that Zabbix was not resolving hostname or was not able to do hostname lookups.