vendredi 3 février 2012

Connecting a computer running Windows to GNS3

Connecting a computer to GNS3 (PC running under Windows)

+ Loopback interface installation

- From the RUN dialog
- Open the "hdwwiz.exe" command
- Next ...
- Is the hardware connected? --> "Yes, I have already connected the hardware"
- Select from the bottom of the list: "Add a new hardware device"
- Option: "Install the hardware that I manually select from a list (Advanced)"
- Select "Network Adapters", Next...
- Select "Microsoft" and then "the Microsoft Loopback Adapater", and then click Next... Next ...
And Finish


http://support.microsoft.com/kb/839013

+ Loopback interface IP configuration

C:\Windows>netsh int ip set address Loopback static 172.29.16.1/24

+ Add route to the Cisco router network IP

C:\Windows>route add 172.29.16.0 mask 255.255.255.0 172.29.16.1
                                        ** DST_ADDR**                           **Loopback_interface_IP-ADDR**
+ Netmap
To create the netmap:

++ Add a router
++ Add a Cloud
+++ Cloud configuration: Double click on the Cloud
+++ Select from "Generic Ethernet NIO" the loopback interface and click on ADD, OK
++ Connect The cloud to the router
++ Start all devices
++ Configure the router interface (FastEthernet 0/0 IP address: 172.29.16.254/24)

Now, You're able to ping the router on GNS3 from your PC.

Next: Connect a computer running Linux to GNS3

CISCO Router: Enable SSHv2

CISCO Router: Enable SSHv2


Enable SSHv2


R1#
R1#conf t
R1(config)#ip ssh version 2
Please create RSA keys (of atleast 768 bits size) to enable SSH v2.




RSA keys creation

R1#
R1#conf t

R1(config)#crypto key generate rsa usage-keys label ssh_keys modulus 1024
The name for the keys will be: ssh_keys

% The key modulus size is 1024 bits
% Generating 1024 bit RSA keys, keys will be non-exportable...[OK]
% Generating 1024 bit RSA keys, keys will be non-exportable...[OK]

crypto_lib_keypair_get failed to get ssh_keys

R1(config)#
*Mar  1 00:07:43.895: %SSH-5-ENABLED: SSH 2.0 has been enabled
R1(config)#


Other config

line vty 0 4
 login local
 transport preferred ssh
 transport input telnet ssh
!

mercredi 1 février 2012