It is currently Tue Apr 23, 2019 10:09 am


All times are UTC




Post new topic Reply to topic  [ 40 posts ]  Go to page Previous  1, 2, 3, 4
Author Message
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Fri Jun 28, 2013 8:35 pm 
Offline
Site Admin

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

Quote:
Re Nickbee's mention of "default of 127.0.0.1" - he was referring to the fact that in gns3.ini, there is still a binding to "localhost" rather than "127.0.0.1"


Got it, I had overlooked the external_hosts=localhost:11525. There was the same issue for Qemu.

Quote:
With Qemu/ASA/Junos - GNS3 does not necessarily create a working directory for a project - the FLASH files get put in the qemu working directory if you Don't check [ ] Save nvrams and start building a newtork with ASAs (I think it did in RC2 or RC3 - and I now believe that was a GOOD idea) so it IS possible to overwrite files.


I agree now, I was still thinking about RC2/RC3.

Quote:
a) Remove the [x] Save IOS configs option. Just do it


Done.

Quote:
b) Play it like it was for ASA/Qemu back in RC2/RC3 when there was ALWAYS a working directory created when you created a project


Yes I could do it but this was more a bug than something intended. If I do this, IOS nvrams + other PCMCIA disks are automatically saved. I'll temporally do it so you can test but I don't think this is a good idea, at least until a do a good clean up.

Here is a dev snapshot to test on Linux: http://code.gns3.net/gns3-devel/archive ... 1d.tar.bz2

And a quick change log for it:

  • Always create a working directory (for testing purposes)
  • instructions file must be inside instructions folder in the project directory.
  • E1000 is the default NIC for Qemu guest, PIX, ASA, JunOS
  • Fixed issues with IDLE PC when Dynamips binding is 0.0.0.0
  • 512 MB is the default RAM for JunOS
  • Removed the "Save IOS configs option". Always save IOS configs.
  • Added default VPCS NIO UDPs for "Host" device.
  • Fixed major bug with UDP port allocations.
  • External hosts for Qemu/VirtualBox changed from localhost to 127.0.0.1

I'm gonna be away this weekend.

Cheers,



_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Sat Jun 29, 2013 12:11 am 
Offline
Site Admin

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

Here is another dev snapshot with the following changes => http://code.gns3.net/gns3-devel/archive ... a3.tar.bz2

  • Removed: "Always create a working directory (for testing purposes)"
  • Fixed issue with 0.0.0.0 binding for Qemu/VirtualBox
  • Default file type is *.net;*.png when opening a file.
  • Added some debugs message when moving or cleaning up files
  • Fixed crash on FreeBSD/Solaris

@Jason

Can you check if this is correct on FreeBSD or Solaris?

Thanks!

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Sat Jun 29, 2013 12:11 pm 
Offline

Joined: Fri Mar 05, 2010 11:33 am
Posts: 1494
Location: Australia
@Jeremy

gns3-devel-54625b3ff71d (first one)

************************** TEST 1 ************************************
Set default bindings to 0.0.0.0 for dynamips
Test idle-pc as I add Cisco images WORKS


************************** TEST 2 ************************************
Set default bindings to 0.0.0.0 for dynamips/qemuwrapper and vboxwrapper

Start new blank project
[ ] Save nvrams *NOT* checked
configs and working directories created immediately, along with the project directory

Add Cisco router
Temporary files added immediately to ~/GNS3/<projectname>/working directory EVEN THOUGH [ ] Save nvrams *NOT* checked
[Would have thought that these would go in the dynamips working directory]

Add Junos router (Qemu)
Directory JUNOS1 created in /tmp directory
[Would have though this would go in the ~/GNS3/<projectname>/working directory OR /home/user/GNS3/Projects/Check2/configs (see actionmystique's comment topic6511-27.html)]

Add ASA
Directory ASA2 created in /tmp directory
[Would have though this would go in the ~/GNS3/<projectname>/working directory OR ../configs]

Joined all routers together
Save topology
=> show run [selected snippets]
[127.0.0.1:7200]
workingdir = /home/user/GNS3/Projects/Check2/working <**** WHY? I didn't check the option
[[3725]]
[[ROUTER R1]]
cnfg = /home/user/GNS3/Projects/Check2/configs/R1.cfg
[vbox 0.0.0.0:11525]
workingdir = None <**** I don't understand vbox working directory - but it didn't seem to matter
[qemu 0.0.0.0:10525]
workingdir = None <****** expected /home/user/GNS3/Projects/Check2/working OR /home/user/GNS3/Projects/Check2/configs (see actionmystique's comment topic6511-27.html)



COMMENT

As you said,
Quote:
Always create a working directory (for testing purposes)
, but the USE of the working directory is the wrong way around.

I was suggesting that the working directory (under the <projectname> directory) would ALWAYS be used for Qemu Working - not for dynamips working - in other words, just use the [ ] Save nvrams...... option to indicate where dynamips working files should be kept.

I think the problem stems from the fact that we have had ONE option ([ ] Save nvrams......) to indicte TWO things. (A) whether dynamips working files are kept with your project and (B) whether Qemu working files are kept with your project.

I'm suggesting that Qemu working files should ALWAYS be kept with your project (just like Cisco configs - that seems to work well)

Leave the [ ] Save nvrams...... option simply to indicate if you want dynamips nvrams and disks kept.

[Note: would have thought that maybe if the dyanamips setting still shows 127.0.0.1, why not the qemu and vbox areas too???]

************************** TEST 3 ************************************
Delete ASA2 and JUNOS1 form /tmp
New Blank Project
[x] Save nvrams CHECKED
configs and working directories created immediately, along with the project directory

Add Cisco router
Temporary files added immediately to ~/GNS3/<projectname>/working directory [as expected]

Add Junos router (Qemu)
Directory JUNOS1 created in /tmp directory
[Would have though this would go in the ~/GNS3/<projectname>/working directory - ESPECIALLY since [x] Save nvrams.. was checked]
Add ASA
Directory ASA2 created in /tmp directory
[Would have though this would go in the ~/GNS3/<projectname>/working directory]

Add Two Vyatta routers (VirtualBox)

CONCLUSION:
CHECKING THE [X] Save nvrams MAKES NO DIFFERENCE
************************** TEST 4 ************************************
Repeat last two tests with Qemu bound to 127.0.0.1
Binding to 127.0.0.1 MAKES NO DIFFERENCE - which is a good thing

************************** TEST 5 ************************************
gns3-devel-c565d128c4a3
************************** ****** ************************************
Behaved more consistently, (ALL dyanamips AND Qemu files were kept in the <projectname>/working directory if [x] Save nvrams was checked OR in /tmp if NOT checked)
************************** TEST 6 ************************************
File | Open Project

Result: NO files showing :-(

Looks like the *.net;*.png doesn't work for Linux. It was worth a try!

************************** TEST 7 ************************************
Haven't had time to do testing on NIO UDP bug yet.

************************** ONE MORE THING ************************************
pedantic change
In GNS3 Preferences | VirtualBox settings [General Settings] tab

Please change the
[ ] Show VirtualBox Advanced Options
to
[ ] Show Advanced Options in VirtualBox Guest tab

It took me 10 mins to work out WTF this checkbox did!

[But I have to ask - why isn't this option actually found inside the [VirtualBox Guest] tab rather than here in [General Settings]?]

_________________
RedNectar
http://rednectar.net
@rednectarchris
GNS3 WorkBench-a VMware image of Ubuntu with GNS3 and VPCS installed and a collection of exercises/labs


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Sat Jun 29, 2013 2:00 pm 
Offline

Joined: Fri Dec 02, 2011 2:12 pm
Posts: 120
Location: Paris
rednectar wrote:
COMMENT
I was suggesting that the working directory (under the <projectname> directory) would ALWAYS be used for Qemu Working - not for dynamips working - in other words, just use the [ ] Save nvrams...... option to indicate where dynamips working files should be kept.

I think the problem stems from the fact that we have had ONE option ([ ] Save nvrams......) to indicte TWO things. (A) whether dynamips working files are kept with your project and (B) whether Qemu working files are kept with your project.

I'm suggesting that Qemu working files should ALWAYS be kept with your project (just like Cisco configs - that seems to work well)

Leave the [ ] Save nvrams...... option simply to indicate if you want dynamips nvrams and disks kept.

@rednectar: I globally agree with what you've said with a few modulations and proposals:

1) Dynamips working files
"[ ] Save nvrams...... option" should be used to do what it says, only for Dynamips, but where?

I understood from what Jeremy told me that the location of working files for Dynamips depends on the "[ ] Save nvrams...... option":
- if not checked, in the global working directory for Dynamips as configured by the user in Dynamips Preferences.
- if checked, in the current project working folder, mixing temporary and non temporary files.

This does not seem to be the most appropriate choice: again, the NVRAMs... files are related to configuration and should be kept somehow in the related folder, i.e ... configs, for example something like configs/nvrams/<whatever the names are>.
And all temporary working Dynamips files (like ghost files and so on...) should be kept in the global working directory for Dynamips as configured by the user in "Dynamips Preferences".

2) Qemu FLASH files
Qemu FLASH drives should always be saved, and in a stable folder (like for startup configuration files for Cisco routers and switches), because they can represent a lot of work (especially for ASAs). This folder cannot be chosen by the user who is unaware of these little details. The only stable one refers to my initial proposal: configs/<device name>/FLASH or configs/qemu/<device name>/FLASH

3) Qemu temporary working files
I'm not sure what they are and if they even exist, but the temporary working Qemu files should be placed in the global working directory for Qemu as configured by the user in "Qemu Preferences".

The global folder organization would look like this:
<Project Name>/topology.net
<Project Name>/topology.png
<Project Name>/configs/<all Cisco routers and switches startup config files>
<Project Name>/configs/qemu/<FLASH files>
<Project Name>/configs/nvrams/<NVRAMs and other related files>

<Global Working Directory for Dynamips>/<all temporary Dynamips working files>
<Global Working Directory for Qemu>/<all temporary Qemu working files> (if that even means something...)

Any comment(s)?

_________________
A Collection of GNS3 Labs: https://learningnetwork.cisco.com/message/232820
i7 4700MQ quad-core 2.6 Ghz and 16 GB RAM
CCNA - CCDA
Beta Test Team
GNS3 0.8.6 on Windows 7 64 bits
GNS3 0.8.6 on Ubuntu 13.10 and Qemu 1.5.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Wed Jul 03, 2013 12:55 am 
Offline

Joined: Fri Mar 05, 2010 11:33 am
Posts: 1494
Location: Australia
@Jeremy. More on gns3-devel-c565d128c4a3

Have now had a chance to test the UDP increment bug. That seems to be fixed.

BUT - the binding to 0.0.0.0 (at least for dynamips) is still broken in this way:

1. Go to GNS3 Preferences, Dynamips settings, [Hypervisor Manager] tab, and set the IP/Host binding to 0.0.0.0

2. Create a topology with a couple of routers

3. Start the routers

4. Find out which port the routers are listening on for console and aux

5. From another PC, telnet to the GNS3 host PC to the console or aux port
Code:
telnet 192.168.226.201 2101
Trying 192.168.226.201...
telnet: connect to address 192.168.226.201: Connection refused
telnet: Unable to connect to remote host


This shouldn't happen once the GNS3 Preferences, Dynamips settings, [Hypervisor Manager] tab, IP/Host binding has been set to 0.0.0.0

_________________
RedNectar
http://rednectar.net
@rednectarchris
GNS3 WorkBench-a VMware image of Ubuntu with GNS3 and VPCS installed and a collection of exercises/labs


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Thu Jul 04, 2013 2:36 pm 
Offline

Joined: Mon Apr 01, 2013 4:38 pm
Posts: 8
Hello Dear ,

Gr8 work doing bro, just want to know is it a bug or what.

When i connecte Vbox Machine -----> with Ethernet Switch ------> then to Router , it ping works fine b/w Router and Vbox Machine but if i disconnect Vbox interface link to Switch and reconnect the cable then Vbox machine can't ping to Router and Vice Vera untill i restart the Vbox Machine . that is it ..

Same problem is in GNS 0.8.3 and till now in version 0.8.4 RC4 i am having

Any solution for this ?


Regards.


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Thu Jul 04, 2013 5:17 pm 
Offline

Joined: Tue Jul 17, 2012 1:34 pm
Posts: 214
grossmj wrote:
@Jason
Can you check if this is correct on FreeBSD or Solaris?
Thanks!


@grossmj
I'm just back from holiday. I'll check it out on both platforms.

_________________
J.Neumann, GNS3 Contributor & Forum Moderator (Minion ID: sin.zx81.1981ad)
Author: Cisco Routers for Small Business (Apress)


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Thu Jul 04, 2013 5:50 pm 
Offline
Site Admin

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

Quote:
1) Dynamips working files
"[ ] Save nvrams...... option" should be used to do what it says, only for Dynamips, but where?

I understood from what Jeremy told me that the location of working files for Dynamips depends on the "[ ] Save nvrams...... option":
- if not checked, in the global working directory for Dynamips as configured by the user in Dynamips Preferences.
- if checked, in the current project working folder, mixing temporary and non temporary files.

This does not seem to be the most appropriate choice: again, the NVRAMs... files are related to configuration and should be kept somehow in the related folder, i.e ... configs, for example something like configs/nvrams/<whatever the names are>.
And all temporary working Dynamips files (like ghost files and so on...) should be kept in the global working directory for Dynamips as configured by the user in "Dynamips Preferences".


This would be the cleanest way to do it but Dynamips only accepts a global working directory. We must modify Dynamips if we want to implement this solution. I will keep the idea for later.

Quote:
2) Qemu FLASH files
Qemu FLASH drives should always be saved, and in a stable folder (like for startup configuration files for Cisco routers and switches), because they can represent a lot of work (especially for ASAs). This folder cannot be chosen by the user who is unaware of these little details. The only stable one refers to my initial proposal: configs/<device name>/FLASH or configs/qemu/<device name>/FLASH


Agreed. Note that in future versions I plan to extract configs from ASA, JunOS etc. So not sure I should put the FLASH files in the configs directory.

Quote:
3) Qemu temporary working files
I'm not sure what they are and if they even exist, but the temporary working Qemu files should be placed in the global working directory for Qemu as configured by the user in "Qemu Preferences".


There are no temporary Qemu files.

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Thu Jul 04, 2013 8:11 pm 
Offline
Site Admin

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

Here it is. The release is scheduled in the next 24h (after I'll be away for the next 3 weeks). Please concentrate on testing the first point.

http://code.gns3.net/gns3-devel/archive ... 38f367.zip

Changelog:

  • Qemu FLASH files are automatically saved in a directory named 'qemu-flash-drives' (in the project directory).
  • Fixed issue with 0.0.0.0 binding for Dynamips
  • Reverted: default file type is *.net;*.png when opening a file.
  • Fixed error on Centos.
  • Moved "show advanced options" to VirtualBox guests tab.

Thanks,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: GNS3 0.8.4 RC4
PostPosted: Fri Jul 05, 2013 4:10 pm 
Offline

Joined: Tue Jul 17, 2012 1:34 pm
Posts: 214
@grossmj
FreeBSD (9.x) is working fine with this release.
<EDIT> This version ALSO WORKS on Solaris 11.1.

Nicely done Jeremy! :D
-Jason



_________________
J.Neumann, GNS3 Contributor & Forum Moderator (Minion ID: sin.zx81.1981ad)
Author: Cisco Routers for Small Business (Apress)


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

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 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