Hi,
Quote:
it's not perfect yet ;-) : the name of this interface on GNS3 is e1, while this name on Linux is e0 (eth0)
The interface name match VBox numbering.
Quote:
As for GNS3 0.8.2 BETA2 : When i create my own symbol : Name "Guest VPCS", Type "Cloud" and picture "computer", it has also the proprieties of the symbol "Host" (nio_gen_eth:). Or I used the wrong method.
Not really a bug but yes this one has not been fixed.
Quote:
On linux, a lab with 1 Router and 1 VMBox (Linux), and the option "Bring console window to front" enabled. The window of the Router doesn't appear when I double-click on it. I have the same with gns3-vbe 0.8.1. Known bug because of "experimental feature" ?
Well, yes this is experimental and I didn't implement this feature, so I don't really know what's wrong.
Quote:
Features Requests (if it isn't too late)
Can you add an option to turn on from the start "show interface label" ?
The menu to select the virtual machine to a "VBOX-Host" only shows the virtual machines that are not already in the laboratory.
Can we have an option for each VM-Box that indicates of to launch it in the background (VBoxManage startvm "VM name" --type headless or VBoxHeadless --startvm <uuid|name> ) ? Only if it is enabled, the gns3's menu has an option "console" (as for Router) who launches an command given in the interface of configuration. We should have access to a few parameters for configure this command (port or name of the VM).
I implemented "The menu to select the virtual machine to a "VBOX-Host" only shows the virtual machines that are not already in the laboratory." but for the rest this is gonna wait a future version.
Quote:
*Confirmed. You can't rename PIX/ASA/JunOS/ETC (Pemu/Qemu nodes) Errors exactly as "SARS" reported.
This is fixed now.
Quote:
*Confirmed. Having space characters in Project/Working/Image directorys will crash Qemu process. As "rochey" reported (and possible match "UldisD" problem).
Pemu is Ok, because you first change the working directory to Project/Working and then start pemu from there just with [... -m 128 FLASH ...] without the full FLASH path ;)
On Windows you have to be always prepared and use double quotes to solve this problem
You already do that for qemu-img.exe
Fixed as well. Needs careful testing.
Quote:
* The backup nvram export (post-mortem) is kind of broken :)
When Dynamips is down + Save button = It does the export (Rx.recovered.cfg), but after that comes this error
This is when is trying to stop again (make it red from green), but was already red (stopped)
Fixed as well. Please also test the "Export all configs to directory" feature as it calls the same function to export them.
Quote:
If you add a Router/VBOX/Qemu/Pemu inside the topology, save the topology, then delete all the nodes from the topology
and save it again, there are some trace of Qemu/Vbox, but that is not the problem.
The problem is that if you close/reopen that topology, GNS3 will have to start one Qemuwrapper and one Vboxwrapper without a good reason :)
For Dynamips all are good :D
Fixed!
Quote:
* Dynamips IDLE-PC problem and solution "On Windows" :) - Jeremy please add a "hint" for this :)
Probably most of the users(including me!) are creating a IDLE-PC value while the router is showing the prompt in console "R1>, R1#, R1(config)#"
Well, you should never do that again! :)
Create a new IDLE-PC value only when the console is in idle state, with this message on the screen "R1 con0 is now available [...] (Press RETURN to get started.)" and without any router prompt (password/R1#/etc)
In this way your IDLE-PC value will be applied by dynamips from the moment the router is started, otherwise it will have effect from the moment you open a console and press some enter keys to bring the prompt :D
I hope this is working for you as is for me ;)
PS: This will only cover now topologies files (.net), For old files, please edit the file and manually change the "idle-pc" with the new value
I added a help button to the IDLE PC dialog box. This gives some hints to get good idlepc values.
Quote:
1. Double clicking on the .net file launches GNS3 if it was closed but it doesn't do anything.
Well this is not supported on OSX. Something they (Apple) don't do like everyone else.
Quote:
2. Arabic language needs some serious work as a lot of the panels are still in English.
Someone has to update it ... unfortunately I don't speak Arabic ;)
Quote:
A lot of people download topologies from a lot of learning website. If I download a topology that has 3640 router, can I have the option to choose my own IOS instead of throwing the error that the IOS isn't found?
GNS3 will try to automatically find an alternative IOS image. I reckon this is a something to improve.
Quote:
This package crashes on my MacBook Pro with 10.7.3
This is fixed now. Please test again when I update the package soon.
Thanks for your help!