It is currently Sat May 25, 2019 5:58 pm


All times are UTC




Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2, 3  Next
Author Message
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Sun Jan 09, 2011 9:28 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Quote:
Any ETA for a fix to that "Ethernet Switch" <-> "Cloud Real_NIC" bug?
It is difficult to create a lab with "NIO eth" without...


I plan to work on GNS3 in 1 or 2 weeks. I'm quite busy these days ;)

Thanks for the posts.

Cheers,



_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Thu Jan 13, 2011 8:25 pm 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 411
Location: [email protected]
Ok, Thanks, but I got something for you ;))

*)
As announced, that the new version of dynamips looks promising some GNS3 improvements may be required ;)
The point is to have both 'console' and 'aux' in all places
1) 'Open AUX' on IOS nodes that support that option or all of them;
2) Update Dynagen 'list' command to display aux port as well;
4) Dynagen 'aux' command to open telnet to AUX port;
5) In "IOS images and hypervisors"->"External hypervisors", add base AUX on settings and both console and aux in the saved hypervisors panel

*)
A most wanted one, for Dynamips nodes :))
Please add the option (optional to the user) to start the console right in the moment that node has started, no matter if you start one node or all of them at once.
It is critical because in large topologies after starting 4-8 routers the CPU gets to 100% even with best IDLEPC, until you start the console and press enter a few times to get to the 'save' zone.
In a "start all devices" scenario you have to permit users to open consoles to the started nodes, even if the starting process is not fully completed, now it is annoying to wait (or use some GNS3 external scripts to open the consoles and save the day) and see that CPU is very high, GNS3 get stuck waiting for dynamips to respond, some dynamips processes may crash and you have to kill all GNS3/dynamips precesses and start your topology one by one...

I have this script, currently for Linux, but without a full dynamic automation it doesn't help to much...
I say that, because 'Dynamips'/'Entire PC' get stuck when CPU is very high.
So, a new approach is needed. The best will be to fix Dynamips code to automatically "press some enters" inside every new started router console.
Another thing will be that GNS3 to open a telnet to the Dynamips host exact in the moment it is started and send "\n\r" every 200ms for example, until the prompt, to get ride of that high CPU usage. (This works either with console or AUX port.)

*)
Automatically extract startup-config from nvrams to files.cfg if dynamips process crashes (and it does) if user is pressing save button;

*)
Dynagen "conf localhost" freeze GNS3;

*)
Using a text note inside a topology which contains '#' result as a comment line, and all the rest text is ignored on reopen topology
ex: "text foo# bar" -> "text foo";


Top
 Profile  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Mon Jan 17, 2011 9:05 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Concerning the "Ethernet Switch" <-> "Cloud Real_NIC" bug, did you have the same issue in previous releases?

Has someone else the same bug?

I'm trying to find out what could be wrong ... ;)

Cheers,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Wed Jan 19, 2011 12:12 am 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 411
Location: [email protected]
Sorry for delay, I had to put back all old versions back to 0.7.1 ...

0.7.3 - the issue as reported
0.7.2 - same story
0.7.1 - the emulated switch doesn't duplicate the interfaces name on mouseover anymore, but it keeps a cloud connected even when the link is removed. The connectivity is quite the same: from router to cloud thru the switch no ping reply comes back and from the other side only ~1/4 requests comes to the router and all of them are answered and the message gets back. In this version is not available the possibility to read the switch mac table, so no check for mac flapping

We really need someone else to test this out, to exclude the possibility to a local issue in my PC, because I'm using a Win x64 system...
And it can come from 64bit network drivers, winpcap also 64bit version, installed software, etc...
As a workaround can be used a MSLoopback

I have a strange filling about this one ;))

PS: By the way, if your NIC supports TCP, UDP, and IP Checksum Offloading and is activated then game over... :))


Attachments:
File comment: Details from GNS3 0.7.1
GNS3-0.7.1.jpg
GNS3-0.7.1.jpg [ 23 KiB | Viewed 5631 times ]
Top
 Profile  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Sat Jan 22, 2011 6:53 pm 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 411
Location: [email protected]
*)
Because Dynamips has 2 console ports, CON0 and AUX per device and Qemu only has ttyS0, plus the 'SDL VGA' that is not so easy to work with it, let's make a balance ;)
That was the good news, but because Qemu always has issues between versions, only v0.11.0 allows to use 4 serial ports, v0.13.0 (I've tested only those two versions) works only with 2 of them, and if the number is increased it crashes "ERROR: isa irq 4 already assigned"

Qemu allows you to use up to 4 serial ports per host...
-serial telnet:127.0.0.1:3000,server,nowait
-serial telnet:127.0.0.1:3001,server,nowait
-serial telnet:127.0.0.1:3002,server,nowait
-serial telnet:127.0.0.1:3003,server,nowait

In order to work we have to activate the remaining serial ports...

In "/etc/inittab" add...
ttyS0::respawn:/sbin/rungetty ttyS0 --autologin tc #this one already exists
ttyS1::respawn:/sbin/rungetty ttyS1 --autologin tc
ttyS2::respawn:/sbin/rungetty ttyS2 --autologin tc
ttyS3::respawn:/sbin/rungetty ttyS3 --autologin tc

In "/etc/securetty" add...
ttyS0 #this one already exists
ttyS1
ttyS2
ttyS3


Top
 Profile  
 
 Post subject: Re: Bugs/new features in GNS3 0.7.3
PostPosted: Mon Jan 24, 2011 11:02 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Hi,

I didn't forget you ;) I'm working on the new Dynamips release and once we have something stable I work on the next release of GNS3 which should fix many of the things you reported as well as supporting the new features of Dynamips RC3.

Cheers,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: Bugs/new features in GNS3 0.7.3
PostPosted: Tue Jan 25, 2011 9:20 am 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 411
Location: [email protected]
Quote:
I didn't forget you ;)


I sow that you guys are very busy with the new Dynamips version and that is a good thing ;))
I'm too lazy/busy to install Cygwin, but probably I'll put it on VMWare in few days to check how the new version works :)

Thanks for keeping it alive!


Top
 Profile  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Fri Feb 11, 2011 11:38 pm 
grossmj wrote:
Concerning the "Ethernet Switch" <-> "Cloud Real_NIC" bug, did you have the same issue in previous releases?

Has someone else the same bug?

I'm trying to find out what could be wrong ... ;)

Cheers,


I have exactly the same problem...if I put an "Ethernet Switch" between the Cloud NIC and the router I can't do the ping anymore but if I do a direct link between clound and the router everything is fine, I'm able to ping the router and the loopback. I even tried using a router (3660 with NM-16ESW) and still didn't work.

Win 7 x64 GNS3 0.7.3
Vince


Top
  
 
 Post subject: Re: Bugs in GNS3 0.7.3
PostPosted: Sat Feb 12, 2011 8:01 am 
Offline

Joined: Thu Jun 24, 2010 3:58 pm
Posts: 411
Location: [email protected]
vicmaxabc wrote:
I have exactly the same problem...if I put an "Ethernet Switch" between the Cloud NIC and the router I can't do the ping anymore but if I do a direct link between clound and the router everything is fine, I'm able to ping the router and the loopback. I even tried using a router (3660 with NM-16ESW) and still didn't work.

Win 7 x64 GNS3 0.7.3
Vince

Thanks vicmaxabc ;)
What Winpcap version do you have?
Also what's the current status for TCP, UDP, and IP Checksum Offloading

Anybody else having this bug!! (Promotional 100% Free ;)
We need users with windows XP 32bit (x86) first, but is room for all


Top
 Profile  
 
 Post subject: Re: Bugs/new features in GNS3 0.7.3
PostPosted: Tue Feb 15, 2011 9:25 am 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Do you have the same kind of issue using Windows Loopbacks?



_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


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