7200emu.hacki.at

[msimone]

Hi, there -
I'm new to GNS3, and the documentation didn't really cover this one. If this has already been covered, I apologize - the search terms I used didn't bring it up well, I guess.

I am trying to gain connectivity between routers on my local instance of Dynamips and my remote instance of it.

Here's what I have:

My workstation: Windows Vista - Windows firewall is off. Running GNS3.0.4.1, with latest Dynamips, Pemu, etc. (I used the full installer package.)

Dynamips server: Fedora Core 7, no iptables, running latest rpms of dynamips and dynagen.

I created one router instance of a 2691 on my Windows box. I can console into it, all looks beautiful. I created one instance of a 2691 on my Linux box. I can console into it, and all looks beautiful.

I did a no shut on the interfaces, gave them unused IP addresses in a network that is not in use in my real environment.

I cannot ping between the two.

So - what am I missing that is preventing communication? Do I need to put a cloud object between them? When I want the routers on the Linux box to be able to connect to a physical NIC on the box (there are 10), will I be able to do that through GNS3?

Thanks so much!
Mike

[gns3dev]

Hi,

I will test this soon to find out what's the problem.

Thanks for reporting.

[thumpercisco]

Here's what I do for pc-pc:
GNS3 latest
- assign phynic's(local/remote) an ipadd/mask in same subnet I will be using (for ping test)
- connect the phynic to remote network phy nic (ipadd/mask in same subnet)
- test ping from local pc phynic to remote pc phynic
-create the topology vrouters and vswitches
- creat cloud and connect/reference the phynic NIO
- connect cloud(phynic) to a vrouter or vswitch
- ping from vrouter to phynic ipadd (the phynic must be connected for ping to work)
- test ping from vrouter to remote phynic and on to remote vrouter

This will give you a network connection between the two pc's.

For the scenario you are stating there are a couple solutions:
Easiest:
- win phynic NIO to a vswitch port, remote phynic to a vswitch port, trunk the ports, connect the other remote nics to the remote vswitch ports(the problem with this is if the remaining phynics are not physically connect they will not work in lab) I assume you will have the remote phynics connected to other devices.

Just remember to test pings at each step from the beginning.

[mikej]

What I noticed is that when using the built-in hyperviser manager, GNS sets dynamips to listen at localhost, which precludes remote communications with external dynamips processes. A nice-to-have feature would be to have the ability to set a default IP address for the hyperviser manager so its still usable in multiserver setups. This especially applies to using PIX in my case, which runs on another box.

[msimone]

Excellent write up, Thumpercisco, thanks!

Next question I have (sorry, I'm new.) How do I control the NIO ports of the Linux box from my GNS3 instance on Windows? Do I need to stop the lab, tweak the .NET files, and restart it? Or is there some way within the GUI to do that?

[thumpercisco]

[msimone]

HA! That did it.
While there's no preference that you can set for it, what I did was created my local IOS image as if it were an external hypervisor with the IP address of my PC. Now the router on my Linux hypervisor communicates with my Windows hypervisor no problem.

Heh heh heh.

I did learn, though, that if I do that, I have to start my Windows "external" hypervisor manually, and have it running before I start. Otherwise, GNS crashes horribly.

Yay!

[thumpercisco]

excellent work - could you document the steps for other forum users to reference, great work.

[msimone]

Here you go!

[gns3dev]

Hi,

I found where is the problem in the GNS3 code, this will be fixed in the next release.

[NoSmile]

Hi,

I have the same issue by using directly the last svn version of Dynagen.

I have a quite strict topolgy to emulate. Could you lead me to the way to fix this issue?

[msimone]