It is currently Thu May 17, 2012 4:18 pm


All times are UTC




Post new topic Reply to topic  [ 110 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6 ... 11  Next
Author Message
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Wed Nov 10, 2010 12:05 am 
Offline

Joined: Fri Oct 29, 2010 12:27 am
Posts: 23
These are not bugs preventing the use of GNS3 but small improvement (in my opinion) :)

When you use load-balanced on external hypervisors, if the hypervisor is down it will raise an error, not add the router but then it will go on with the numbering.

Example to make it more clear:
I have two hypervisors. One is up and the other one is down.
I add a router and GNS3 decides to use the hypervisor that it is up and gives it the hostname R1.
Everything is fine so far.
I add router and GNS3 decides to use the hypervisor that it is down.
I get the warning but the router is not added.
I try to add one more and it uses again the hypervisor that it is up but but now the hostname of the router is R3 instead of R2 that it should have been.

----

When you add an Ethernet switch it has 8 ports by default.
If you use 1 or 2 of them, save your project and reload it again the switch will have only the number of connected ports (in that case an one or two ports switch).
The number of added ports should be saved even if they are not connected.

Regards,
Vangelis






Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Wed Nov 10, 2010 8:02 pm 
Offline

Joined: Fri Oct 29, 2010 12:27 am
Posts: 23
Bug with Qemu hosts while testing 0.7.3..

I have 3 qemu images. Tinycore 2.11.5, Microcore 2.11.5 and a debian one that I created myself.
I start GNS3 and add QEMU1 as Microcore and QEMU2 as the Debian one.
I close GNS3.
I Reopen it and this time I add Tinycore as QEMU1 and Microcore as QEMU2 but instead of the tinycore the microcore (that I added before closing GNS3 as QEMU1) comes up and instead of microce the debian comes up!
Sometime after the re-opening of GNS3 I can't load any qemu host at all and qemuwrapper gives me this error:

Code:
Qemu path is now /home/cyber/Desktop/GNS3/qemu-0.12.5/i386-softmmu/qemu
Qemu-img path is now /home/cyber/Desktop/GNS3/qemu-0.12.5/qemu-img
!! QEMU1.console = 3000
!! QEMU1.kvm = True
!! QEMU1.netcard = e1000
!! QEMU1.nics = 4
!! QEMU1.image = /qemu-images/debian-506-i386-qemu-gns3.img
!! QEMU1.ram = 64
!! QEMU1.options = -no-acpi




    command: ['/home/cyber/Desktop/GNS3/qemu-0.12.5/i386-softmmu/qemu', '-m', '64', '/tmp/QEMU1/FLASH', '-hdb', '/tmp/QEMU1/SWAP', '-enable-kvm', '-net', 'nic,vlan=0,macaddr=00:00:ab:22:e0:00,model=e1000', '-net', 'nic,vlan=1,macaddr=00:00:ab:4a:b6:01,model=e1000', '-net', 'nic,vlan=2,macaddr=00:00:ab:1a:da:02,model=e1000', '-net', 'nic,vlan=3,macaddr=00:00:ab:fa:e1:03,model=e1000', '-serial', 'telnet::3000,server,nowait', '-no-acpi']
qemu: could not open disk image /tmp/QEMU1/FLASH: No such file or directory
    pid: 20404


The "/tmp/QEMU1/FLASH" already exists though!

If I clear the /tmp/QEMU* manually, everything looks like working fine...


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Sat Nov 13, 2010 4:01 pm 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 313
Location: [email protected]
Thanks again for your great work :)

[Bugs in last all-in-one v0.7.3]
1)
While trying to copy the output from Dynagen Console with Ctrl+C/V/X/Y, etc it replaces the selected text with a ASCII chart and the clipboard remain unchanged.
With right click content menu works.
2)
The new option on routers "change aux port" shows the errors in the attached file.
3)
GNS3 get stuck and hangs on dynamips when you start/stop a full topology. (from time to time, more often than in older versions)

[Small improvements]
1)
Please add "Reload" option in content menu for PIX, ASA, Qemu Host, IDS and also a Reload/Restart topology in control menu.
2)
Add a option so, when you power up a device the telnet to the console starts automatically.
3)
Ask you for a custom Hostname when you drag a new device in the topology. Global option or when you add it with right click mouse button.
4)
Please add a Apply button for idlepc after calculating all values. Sometimes you can find more possible best choices values, "*" marked.
This option allow you to test all of them before you choice one.
5)
Lets create a best "IDLEPC" db for specific IOS.
7200 - 0x60758690 - c7200-p-mz.124-16-extracted.bin
7200 - 0x610eaedc - c7200-advipservicesk9-mz.124-2.T-extracted.bin
3725 - 0x61200084 - c3725-adventerprisek9-mz.124-16-extracted.bin
3640 - 0x60503ba4 - c3640-jk9o3s-mz.124-16a-extracted.bin
2621 - 0x80c0e29c - c2600-ipvoice-mz.123-1-extracted.bin
1710 - 0x805fa2c0 - c1700-ipvoicek9-mz.124-3b-extracted.bin

All of them consume up to 1%CPU, except 1710 with 2%CPU
I use Vista x64, 6Gb RAM, Intel Q6600 CPU

Attachment:
Change_AUX_0.7.3.zip [397 Bytes]
Downloaded 207 times


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Sat Nov 13, 2010 8:33 pm 
Offline

Joined: Tue Jul 20, 2010 5:50 pm
Posts: 93
This might be connected to bug report above -> when using external hypervisor the console and AUX port clash into one. In the example below they clash into 2001:
Code:
=>   DEBUG: sending to dynamips at 127.0.0.1:7201 -> hypervisor version
  DEBUG: returned -> ['100-0.2.8-RC2-x86']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> hypervisor reset
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> hypervisor working_dir "C:\GNS3Project"
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm create R2 1 c7200
  DEBUG: returned -> ["100-VM 'R2' created"]
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm set_con_tcp_port R2 2001
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm set_aux_tcp_port R2 2001
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> c7200 set_npe R2 npe-400
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm set_ios R2 "C:\GNS3Project\c7200-p-mz.122-25.S15.BIN"
  DEBUG: returned -> ["100-IOS image set for 'R2'"]
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm set_ram R2 256
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm push_config R2
  DEBUG: returned -> ["100-IOS config file pushed tm VM 'R2'"]
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm set_aux_tcp_port R2 3001
  DEBUG: returned -> ['100-OK']
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm start R2
  DEBUG: returned -> ["100-VM 'R2' started"]
  DEBUG: sending to dynamips at 127.0.0.1:7201 -> vm stop R2
  DEBUG: returned -> ["100-VM 'R2' stopped"]


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Tue Nov 16, 2010 7:32 am 
to expect 0.7.3 release

grossmj wrote:
Hi guys,

We are currently debugging the next version of GNS3 and we would like that more people who are already experienced with GNS3 participate.

It's easy, first download the debug version for Windows or if you have another OS, download the last dev version on code.gns3.net

Then you can test whatever you want, create labs etc. and if you find a bug, post here with as many details as you can in order to reproduce the bug (i.e. *.log files in GNS3 exec directory, .net files, error messages in GNS3 etc.)

Please also check for consistency issues, spelling mistake or whatever you feel should change. This is really helping us to improve GNS3.

Here is the current changelog for this version:

* Easily change the symbol of one or several nodes (Select a node, then right click -> Change symbol).
* A docked window to see on what device and interface captures are running (View -> Docks -> Captures). You can stop capturing or start Wireshark using this view.
* Only the necessary files (nvram/flash/disks) are copied or kept when creating projects and snapshots.
* Preventing unsaved interface labels to show up after loading a topology. This can be reset using the "show interface labels" button.
* Improvements for ATM and Frame Relay switches: proper naming, dynamic mapping support and it is not needed to remove a link to change its DLCI/VC mapping.
* PCAP capture support for Qemu based devices (Qemu host, JunOS ASA, PIX, IDS). This option cannot be used after the selected device is started.
* Fixed many issues with the snapshot feature. Now it should work as expected.
* New node type: EtherSwitch router. This is a c3700 router with a Etherswitch NM-16ESW loaded.
* Better consistency between buttons and menus. Many items have been renamed, toolbar buttons accessible from the menu etc.
* Possibility to configure the AUX port. Only works for c7200 routers (Preferences -> Dynamips -> Base AUX port).
* Changed standard naming convention for project and snapshots. Topology file is named topology.net, working directory: working and configurations directory: configs.
* Duplicate option for annotations, ellipses and rectangles (Select an item, right click -> Duplicate).
* Horizontal + vertical alignment options (Select nodes, right click -> Align horizontally/vertically).
* Possibility to have multiple images for Qemu hosts, JunOS, PIX, ASA and IDS and to configure the number of interfaces on each devices.
* Autosave feature to save your topology every x secondes (Preferences -> General).
* A default base config (with hostname, exec-timeout commands etc.) is automatically loaded when creating a new IOS based router. The path to this default config can be changed in "IOS images and hypervisors" dialog.
* A more understandable MAC address table for Ethernet switches (right click on a switch -> Show MAC address table).

The final version is expected to be released early November.

Many Thanks.


Top
  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Tue Nov 16, 2010 9:10 am 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 964
Location: Canada
I'm still waiting a bit before releasing as I want this version to be very consistent and with a maximum of bugs fixed.

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Tue Nov 16, 2010 9:40 pm 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 313
Location: [email protected]
I found why my ASA console is not working with Qemuwrapper (version 0.7.3), but is with (version 0.3)
I've bothered you few times about this stuff :))

I've manually started Qemuwrapper with command "qemuwrapper.exe" --listen localhost --port 10525"
for both versions and the only difference was this:

[Qemuwrapper v0.7.3]
Starts qemu with " ... '-serial', 'telnet:localhost:3000,server,nowait' "
[Qemuwrapper v0.3]
Starts qemu with " ... '-serial', 'telnet:127.0.0.1:3000,server,nowait' "

A ping to localhost says "Reply from ::1: time<1ms", so IPv6, not 127.0.0.1

Qemu sockets are IPv6 when started on localhost:3000, Qemuwrapper remain IPv4 in all versions
[Qemuwrapper v0.7.3]
>netstat2 | grep qemu
Nr Proto Local Address Foreign Address State Deamon
8 TCP [::1]:3000 [::]:0 LISTENING [qemu.exe]
9 TCP [::1]:3000 [::1]:28847 ESTABLISHED [qemu.exe]
19 TCP 127.0.0.1:10525 0.0.0.0:0 LISTENING [qemuwrapper.exe]
20 TCP 127.0.0.1:10525 127.0.0.1:28837 ESTABLISHED [qemuwrapper.exe]

[Qemuwrapper v0.3]
>netstat2 | grep qemu
Nr Proto Local Address Foreign Address State Deamon
16 TCP 127.0.0.1:10525 0.0.0.0:0 LISTENING [qemuwrapper.exe]
17 TCP 127.0.0.1:10525 127.0.0.1:28837 ESTABLISHED [qemuwrapper.exe]
25 TCP 127.0.0.1:3000 0.0.0.0:0 LISTENING [qemu.exe]
26 TCP 127.0.0.1:3000 127.0.0.1:28848 ESTABLISHED [qemu.exe]

[Solution/Workaround]
1)
After commenting this line in hosts everything works just fine...
C:\Windows\System32\drivers\etc\hosts
#::1 localhost
2)
Or change IP/host binding on Preferences->Qemu->General Settings
from "localhost" to "127.0.0.1".
Seems that Qemuwrapper v0.7.3 when starts new qemu child is using the same binding.

So, the conclusion is that this version of Qemu does not work very well in IPv6
On their website is announced a new version QEMU v0.13.0 from Oct 15 2010, but no info about IPv6 (ChangeLog is coming soon).


Last edited by tranzitwww on Mon Dec 06, 2010 11:26 am, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Tue Nov 16, 2010 10:32 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 964
Location: Canada
I was suspecting this problem ;) thanks for confirming. I think I'll change the default value in the next release.

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Thu Nov 18, 2010 2:14 pm 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 313
Location: [email protected]
Hi again, I have some good news and I hope that will be confirmed!
I did a little digging in Qemu and this is what I found:

1)
A good option for users which accidentally close a working qemu :))
This can be a default for any qemu supported device Host/ASA/IDS/Juniper
Code:
-no-quit

Optional will be great to have VNC with a incremental port like the serial
and a option to start that VNC from content menu
but this will replace the main VGA window
Code:
-vnc 127.0.0.1:i++
VNC Listening socket 127.0.0.1:5900+i


2)
How do you know which Host is Qemu3, when all of them are named QEMU?
This also can be a default for any qemu supported device Host/ASA/IDS/Juniper
Code:
-name Qemu3


3)
Can you please change the GNS3 behavior when it receive the bellow message from Qemuwarper, so it will treat the Qemu host as stopped/death?
Or ask the user about, because that Qemu remain stuck and I have to restart GNS3.
Code:
Unable to stop Qemu instance QEMU12
Access is denied.


4)
Let's brings the cake.... ;)
How do you run multiple Qemu hosts? Well this post was a answer, but lets find out why it works like that?

I've use Process Monitor with GNS3 starting a bunch of Qemu hosts...
And the result was that Qemu.exe (Win32) makes a ERROR_SHARING_VIOLATION with other Qemu hosts because all of them keeps qemu_image.img open for some reasons and the sharing is not well configured.

Debug image detail
Image

This bug is also present in qemu-img as well, that's when you find the message "qemu: could not open disk image" in "stderr.txt"
And a smart guy finds a solution for a similar problem. I just hope it will work for this one. ->See this post!!!
PS: I didn't compiled it... :D

Code:
--- qemu-0.9.0/block-raw.c.orig Mon Feb 5 18:01:54 2007
+++ qemu-0.9.0/block-raw.c Tue Mar 20 15:27:39 2007
@@ -1281,10 +1281,11 @@
overlapped = FILE_FLAG_OVERLAPPED;
#endif
s->hfile = CreateFile(filename, access_flags,
- FILE_SHARE_READ, NULL,
+ FILE_SHARE_READ | FILE_SHARE_WRITE, NULL,
create_flags, overlapped, NULL);
if (s->hfile == INVALID_HANDLE_VALUE) {
int err = GetLastError();
+ fprintf(stderr,"Error on %s:%d\n", filename, err);

if (err == ERROR_ACCESS_DENIED)
return -EACCES;

credit blue_toleco


Top
 Profile  
 
 Post subject: Re: GNS3 0.7.3 debugging version
PostPosted: Thu Nov 18, 2010 11:18 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 964
Location: Canada
Great job!! I'll try to do tests next week-end and think about implementing your ideas as well.

Many thanks, it's really helpful :)





_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 110 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6 ... 11  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO