What’s new in GNS3 version 2.1
Version 2.1 is a new feature release of GNS3. This version continues the work started in version 2.0 to improve the experience when using a central GNS3 server and for controlling GNS3 via the API.
No rollback is possible. Backup all your projects, settings and you need to snapshot the GNS3 VM. Version 2.1 is in alpha stage which means many things could be broken or not work as expected.
Regarding projects created with version 0.8.x, open them with version 1.x of GNS3 before switching to version 2.1. No direct conversion from 0.8 to 2.1 is supported.
In August 2017.
Current 1.5 is stable and have no blocking bug, we will not release a new version to avoid breaking something.
We will eventually release a new minor 2.0.x version to fix bugs during the 2.1 version alpha/beta cycle.
Yes, excepting unexpected bugs.
NO! Upgrade only if you are not in the middle of something important. We put a huge effort to make sure to test each release but due to the nature of GNS3 we cannot possibly test all the scenarios, environments, images, etc.
No web GUI is provided with version 2.1. We have a new team member who will work full time on it after version 2.1 is released.
Originally we planned to include an host only node in this release however the task was more complex than expected and we still don’t have a good and portable solution.
You can apply packet filters on links without stopping any node. Supported filters are:
All packet filters can be combined, meaning you can apply both a packet loss filter and a delay filter on the same link.
Links can be suspended resulting in no packets going through. This is currently implemented using a frequency drop packet filter with a value of -1 (drop all packets).
You can search appliance templates from within the application. A dialog wizard will ask you for required images the first time you install an appliance.
A zoom percentage will be displayed in the status bar when zooming in and out.
Until now you were limited to a maximum of 32 network adapters for Qemu VMs (or less depending if other PCI devices were connected). The limit is now 275, the maximum support by Qemu. Qemu version 2.4 or later is required.
A drawing line tool is now available. The style can be changed just like rectangles and ellipses.
Errors will be displayed in a floating popup. This allows you to close the GNS3 console without missing errors and notifications.
The number of errors or warnings will be displayed at the bottom right of the GNS3 application. Clicking on it will show the GNS3 console.
This change impacts users with a central GNS3 server. Prior to version 2.1, base configurations for VPCS, IOU and Dynamips were sent by the GNS3 client. This meant that a node created by two different clients could have a different base configurations. Now the based configurations stored on a central server ared used for all nodes.
%n will be replaced by the node UUID when passed as a parameter of the Telnet console command line. This is useful for scripting.
The NAT node will use the VMware vmnet adapter instead of the libvirt NAT feature of the GNS3 VM provided VMware is installed on Windows or MAC. This allows to connect a Dynamips topology to the Internet without having to boot a GNS3 VM.
VPCS, Dynamips routers and Ethernet switches can be duplicated using the right click. This includes their configuration. More node types will be supported in the final 2.1 version.
aiohttp is the library used to run the HTTP API of GNS3. This upgrade was required in order to support Linux distributions like Alpine and Arch.
Spice provides an access to displays and devices. In combination with QXL (paravirtualized framebuffer), it can improve graphics experience in the guest.
GNS3 now saves UI state of show layers, snap to grid, show the grid and show/hide interface labels per project.
A security prevents you to start GNS3 as a normal user if you started it as root before (this doesn’t apply on Windows). This is to avoid permissions issues. We strongly recommend to avoid running GNS3 as root since there is no good reason to do that.
We have release a new maintenance version of Dynamips which is included in GNS3 2.1. This version of Dynamips has the following changes:
Deprecated features should not impact you, these are rarely used features which are usually not documented.
You can no longer connect to a GNS3 server using HTTPS. Support in version 2.1 was buggy.
We recommend to setup a VPN instead because it will protect connections to the GNS3 server and to server consoles.
We no longer provide packages for Ubuntu trusty. The last supported release is the current LTS version of Ubuntu: Xenial. The main reason is the Qt version provided by Trusty is old and contain bugs especially with HDPI support.
Launchpad allow us now to build only for the last LTS and next releases. That’s why we ship only packages for this releases.
Qt 5.5 and later is required on Linux. This allows the GNS3 team to use new Qt module like websockets which benefits all users.
uBridge, our tool allowing enhanced link support, is mandatory to run GNS3. uBridge is stable and support advanced features like packet filters.