What’s new in GNS3 version 2.1
Version 2.1 is a new feature release of GNS3. This version continues the work of 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.
If you still have projects created with 0.8.x open them with a 1.X version of GNS3 before switching to 2.1. No direct conversion from 0.8 to 2.1 will be supported.
No date for the moment
Current 1.5 is stable and have no blocking bug, we will not release a new version to avoid breaking something.
During the 2.1 alpha/beta cycle, we will eventually release a new 2.0 to fix bug.
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 app is provided with version 2.1. We have experimental application on Github but it is only to validate our architecture.
You can search appliance template from the application. The first time you will need it, the wizard will ask you for the required images.
When you zoom you now see the zoom level in the status bar
Until now you were limited to 32 adapters for qemu (or less depending of the PCI devices connected). The limit is now 275 the maximum that Qemu could support. This require Qemu 2.4 or later.
A drawing line tool is now available. You can style them like rectangle and circles.
Error will be displayed in a floating popup. This allows you to close the console without losing errors.
At the bottom of the screen you can see the number of errors reported by GNS3 and if you click on it the GNS3 console will open.
This change impact user with a central GNS3 server. In version prior to 2.1 the base configuration for VPCS, IOU and Dynamips was sent by the GNS3 client. This mean a node created by two different client could have a different base configuration. Now the configuration on the central server is use for all nodes.
If you pass %n as a parameter of the telnet console it will replaced by the node UUID. This allow you to use it for scripting.
If you have VMware installed on Windows and Mac the NAT can use the VMware vmnet adapter instead of the libvirt nat of the GNS3 VM. This allow you to connect a Dynamips topology to the internet without the need of booting the GNS3 VM.
aiohttp is the library use for running the HTTP API of GNS3. This upgrade was required in order to support bleeding edge distribution like Alpine or Arch.
Spice provides an access to displays and devices. In combination with QXL (paravirtualized framebuffer) can improve graphics experience in the guest.
Now VPCS is a part of the GNS3 server, rewrote in pure python it’s lighter (no more external process) and easier to extend. This solve old issues like invalid checksum in TCP frames.
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 he will protect the connection to the GNS3 server and to the server consoles.
We no longer provide package for Ubuntu trusty. The last supported release is the current ubuntu LTS: Xenial. The main reason is the Qt version provided by Trusty is old and contain bug especially for HDPI screens.
With the drop of Ubuntu Trusty support we ask now for Qt 5.5 and later for Linux. This allow the GNS3 team to use new Qt module like websockets which mean benefits for all users.