Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
doc.zentyal.org
Let’s see how to deploy network scenarios somewhat more complex than just a virtual machine with
Internet access.
This first scenario consists of a virtualized Zentyal server with three network interfaces. The first
interface (typically eth0) will link the server to the Internet, using a Bridged Adaptor connection with
DHCP resolution. The second one (eth1) is a Host-Only interface type connecting with the host (real)
machine. This network will work on the vboxnet0 interface (Default). The third interface (eth2) will
connect the server with a virtual client, using an Internal network type connection.
The first network will connect the server to the Internet and the address will be assigned by DHCP. The
second network will use the vboxnet0 interface, using the 192.168.56.0/24 range. This network is
considered internal and Zentyal will use it to connect with the Host. The third network will use the
intnet internal interface in VirtualBox and it will be also considered internal for Zentyal, using the
192.168.200.0/24 range.
Scenario 1 diagram
In this scenario and the next ones, the part tagged as VM is the configuration for your virtual machine
manager, VirtualBox in this case, and the part tagged as Zentyal is the configuration of the interface
From Settings –> Network on the virtual machine on which you intend to install Zentyal, connect the
interfaces to a Bridged Adapter. You need to choose also the (real) physical interface that will provide
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 1/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Set the third interface as Internal Network, named intnet. Name is important in VirtualBox, if two hosts
have different names for their internal networks, they will not be connected internally by VirtualBox.
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 2/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Now you can reboot your Zentyal server and configure its interfaces. You can use any operating system
for the client machine, although we recommend Ubuntu Linux (try the lighter versions like Xubuntu or
Lubuntu) for its ease of use and because it is free to download and install.
This scenario is identical to the last one but you add an extra virtual network using the range
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 3/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Scenario 2 diagram
This interface is internal and will be created in a similar way to that of the previous scenario, but
The next scenario is targeted at deployments or exercises where you have more than one gateway,
which allows you to take advantage of Zentyal traffic balancing, multigateway rules and wan-failover
capabilities.
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 4/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Scenario 3 diagram
To do this, you modify the first network interface, changing it to NAT. You enable the last network
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 5/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Then you will configure eth0 and eth3 as external, DHCP. This way, from the point of view of your
Zentyal server there are two different gateways that can be used to reach Internet.
This scenario is similar to scenario 1, but you will have an extra client that does not access Internet
through Zentyal, like the client located under eth2, but can contact Zentyal by using an external network.
This scenario can be useful to check VPN connectivity, or just to check the access from Internet to any
of the services offered by Zentyal and allowed in the section ‘Filtering rules from External networks to
Zentyal’.
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 6/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Scenario 4 diagram
The recommend configuration is to set up the network interface of the client as ‘Network Bridge’, so
Zentyal can reach it through the external network. You have to take into account that Zentyal does not
In this scenario you will duplicate scenario 1 to deploy an environment with multiple locations, each one
managed by its own Zentyal server, suitable for scenarios with VPN tunnels, several Active Directory
DCs or both.
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 7/8
28/11/2018 Advanced network scenarios — Zentyal 5.1 Documentation :: Reader View
Scenario 5 diagram
It’s important to make sure that both the additional client, and the eth1 interface of the additional Zentyal
chrome-extension://ecabifbgmdmgdllomnfinbmaellmclnh/data/reader/index.html?id=738059671 8/8