The CORE Network Emulator development team released CORE version 4.7 in August 2014. I installed this new version of CORE on a newly-installed Linux 14.04 system and tested some of the new features. In this post, I list the new features that are most relevant to researchers who use the CORE GUI to set up […]
The occasion of my fiftieth post is a good milestone to pause and look back on the two years since I started blogging about open-source routing and network simulation. I will review the blog’s performance statistics and reflect on why I started this blog and what I want to do next. The chart above shows
The Cloonix open-source network simulator uses the Spice remote desktop system to provide a virtual desktop connection to quest virtual machines that run a graphical user interface, such as Microsoft Windows or a Linux desktop environment. To use a graphical desktop user interface on a guest VM, we access the VM using the Spice desktop
To run a program that uses a graphical user interface on a guest virtual machine running in the cloonix open-source network simulator, log into the guest VM from the host computer using SSH and forward the X11 display. Then, any X11 program you run on the guest VM using that SSH session, such as Wireshark,
As we work through this tutorial, we will learn how to use the cloonix graph interface to build a simulation scenario that includes two small IPv6 networks connected to each other by two routers via static routes. We will also learn how cloonix saves network topologies and guest virtual machine root filesystems. The cloonix open-source
The cloonix project provides a variety of root filesystems for use in the cloonix network simulator. These root filesystem only have the most basic software packages installed and will not support advanced network configuration (with the exception of router filesystems such as openwrt). To create a network simulation that runs real-world networking software, we need
The cloonix development team recently updated the cloonix network simulator to version 24. This post describes the changes in cloonix v24 compared to cloonix v19, which we reviewed in a previous post. Version 24 simplifies the setup of guest virtual machines, improves the link performance emulation tool, and adds new interface types designed to improve
The Cloonix open-source network simulator was recently updated to version 24. The last time I used Cloonix, it was at version 19 (see my review of Cloonix and my using the Cloonix graph interface posts). Compared to version 19, only a few details of the installation procedure have changed — the list of package dependencies
While working through some of the previous tutorials about the CORE Network Emulator or IPv6, we noticed some strange broadcast packets in the Wireshark packet analyzer that appeared to have nothing to do with the processes running on the simulated network. For example, we started a simulation consisting of two nodes connected to the same
In Part 1 of this series, we performed some practical experiments to show how interfaces in an IPv6 network configure themselves with link-local IPv6 addresses when they start up. We also showed how to manually configure IPv6 addresses on a Linux system. In this post, we will use an open-source network simulator to demonstrate another
IPv6 addressing is about more than just a longer 128-bit address length. The working groups that defined IPv6 were trying to solve some of the problems that programmers, network administrators, and network engineers were encountering with IPv4. The way that IPv6 prefixes and addresses are assigned and configured differs significantly from IPv4. IPv6 offers some
Previously, we installed the CORE Network Emulator from source code and installed the network services used by CORE. Now, we want to run a simulated networking scenario and modify the configuration of the quagga routing daemon on one or more virtual routers. To do this, we open a shell to the node and start the