Skip to content


Switch branches/tags


Failed to load latest commit information.
Latest commit message
Commit time


VySOlator provides isolation of (virtual) networks based on VyOS. The goal of this project is to provide an initial setup for anyone who is looking to properly isolate (virtual) networks and protect their host machine. Use cases for this project:

  • Pentesting
  • Malware research

Currently only one network (internet only) is provided but more will be added as the project progresses.

Process (steps)

  • Building the VyOS iso
  • Configure additional VMware networks
  • Create and configure the VyOS virtual machine
  • Troubleshooting
  • Optional: test your setup
    1. Use your favourite network attacks and ensure it works as intended
    2. Create a pull request or issue if you found a way to access something else than the internet

Building the VyOS iso

A pre-build iso is available through VyOS ( However, building it from scratch allows for more granular control. Here are the steps for building the iso using docker:

  1. Install docker, you can use the script in this repository
    • sudo ./
  2. Clone the VyOS repo and change the branch to crux
  3. From within the vyos-build folder
    • sudo docker build -t vyos-builder docker
    • sudo docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos-builder bash
      • ./configure --custom-package vim --build-by DiabloHorn
      • sudo make iso

The result of the above commands will be the iso created in the build directory within the vyos-build directory. This is the iso we can use to install VyOS.

Configure additional VMware networks

We will add to new networks two VMWare (vmnet2,vmnet3) that have zero interaction with the host. Below are the configration steps per VMWare version:

Create and configure the VyOS virtual machine

Creating the virtual machine

Add a new virual machine and select install from disc or image as the installation method. In the next screen select the vyos image we build in the previous step. As the operating system we choose Linux/Debian 7.x 64-bit (newer Debian version might also work). Recommended disk space is 5 GB and memory 512 mb. Give it two network adapters, one connected to vmnet2 and the other to vmnet3. After the vm has booted login with:

Username: vyos
Password: vyos

On the commandline interface just run install image and make some common sense choices. After you are one, reboot the system. You will be able to login into your virtual gateway using your chosen password. The username will remain vyos. You can now shutdown (poweroff) your virtual machine to be able to configure some additional network interfaces.

Configure the virtual machine

Enable ssh for remote management

The following commands will enable SSH and DHCP on the 'mgmt' interface:

set interfaces ethernet eth1 description 'mgmt interface'
set interfaces ethernet eth1 address ''
set service dhcp-server shared-network-name mgmt subnet set service dhcp-server shared-network-name mgmt subnet range 0 start ''
set service dhcp-server shared-network-name mgmt subnet range 0 stop ''
set service ssh listen-address ''
set service ssh port '22'

To be able to connect to VyOS via SSH another VM has to be placed in the same network/segment.

Running setup script

We perform the following from our mgmt VM:

scp vyos@

ssh vyos@ "chmod +x ; sg vyattacfg -c ./"

That's it. If we now place a VM in the same segment / interfaces as vmnet3/eth2 it will only be able to connect to the internet.


  • Running "sudo docker build -t vyos-builder docker" does not work (container is unable to install packages) When running docker on Ubuntu 16 you might have no internet inside your containers, comment out dnsmasq in /etc/NetworkManager/NetworkManager.conf and restart the Network Manager service.
  • I messed up the configuration

    load /opt/vyatta/etc/config.boot.default
    # If you are doing this remote, connection will drop after this

  • Can I use different IP ranges than your example?
    Yes, of course. Be mindful of typo's



vyos based isolation of networks







No releases published


No packages published

Contributors 4