GNS3 error while loading topology that worked before - 206-unable to create UDP NIO

When loading a topology file into GNS3 which worked perfectly before I experienced the following error from time to time:

1_gns3_2012-11-13_12-54-12

Last time I faced this error the topology.net file was mixed up due to unknown reason. Let’s see if it’s the same issue again…

When looking on the topology.net file in a text editor the main sections are mixed up in term of numbering regarding the UDP Port numbers (see the red marks):

2_cusersstephandocumentsgns3projectsprovider-network-customer-mpls-vpnto_2012-11-13_13-34-20

They should start at port “7200” and increment by 1 for each section.

Order all main sections so that they start again with port 7200 and that the file looks something like this:

3_cusersstephandocumentsgns3projectsprovider-network-customer-mpls-vpnto_2012-11-13_13-40-00

After that GNS3 should start up correctly again.

gns3 

See also