Getting used to GNS3

danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
So I put 3 routers up. R1 F0/0:192.168.2.1 /24, S0/0:10.1.1.2 /30
R2 S0/1:10.1.1.1 /30, S0/0:10.2.2.1 /30
R3 S0/0:10.2.2.2 /30

with a loopback I made on my desktop. The Lo1 can ping 192.168.2.1 but can't ping any other IPs. I put 3 router configs below:
Ethernet adapter Loopback 1:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::28bc:5b16:97de:c850%22
IPv4 Address. . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DID I DO SOMETHING WRONG WITH THE LOOPBACK ? I guess you can't control what type of cable from the Cloud (my physical loopback on my PC) to R1.
So I put a switch in between and still can't ping past gateway IP on R1.
I know I'm probably missing something obvious but can't be sure


Router 1
interface FastEthernet0/0
ip address 192.168.2.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
ip address 10.1.1.2 255.255.255.252
clock rate 64000
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
clock rate 2000000
!
router eigrp 1
network 10.1.1.0 0.0.0.3
network 192.168.1.0
network 192.168.2.0
no auto-summary




Router 2
interface Serial0/0
ip address 10.2.2.1 255.255.255.252
clock rate 64000
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
ip address 10.1.1.1 255.255.255.252
clock rate 2000000
!
router eigrp 1
network 10.1.1.0 0.0.0.3
network 10.2.2.0 0.0.0.3
no auto-summary




Router 3
interface FastEthernet0/0
ip address 192.168.3.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
ip address 10.2.2.2 255.255.255.252
clock rate 2000000
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
clock rate 2000000
!
router eigrp 1
network 10.2.2.0 0.0.0.3
network 192.168.3.0
no auto-summary


R1 SHOW IP ROUTE
R1(config)#do sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route


Gateway of last resort is not set


10.0.0.0/30 is subnetted, 2 subnets
D 10.2.2.0 [90/2681856] via 10.1.1.1, 00:02:36, Serial0/0
C 10.1.1.0 is directly connected, Serial0/0
C 192.168.2.0/24 is directly connected, FastEthernet0/0
D 192.168.3.0/24 [90/2707456] via 10.1.1.1, 00:02:36, Serial0/0

ROUTER 2 or BB
BB#SH IP ROUTE
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route


Gateway of last resort is not set


172.30.0.0/24 is subnetted, 8 subnets
C 172.30.2.0 is directly connected, Loopback2
C 172.30.3.0 is directly connected, Loopback3
C 172.30.0.0 is directly connected, Loopback0
C 172.30.1.0 is directly connected, Loopback1
C 172.30.6.0 is directly connected, Loopback6
C 172.30.4.0 is directly connected, Loopback4
C 172.30.5.0 is directly connected, Loopback5
C 172.30.8.0 is directly connected, Loopback8
172.39.0.0/24 is subnetted, 1 subnets
C 172.39.7.0 is directly connected, Loopback7
10.0.0.0/30 is subnetted, 2 subnets
C 10.2.2.0 is directly connected, Serial0/0
C 10.1.1.0 is directly connected, Serial0/1
D 192.168.2.0/24 [90/2195456] via 10.1.1.2, 00:26:56, Serial0/1
D 192.168.3.0/24 [90/2195456] via 10.2.2.2, 00:31:25, Serial0/0

ROUTER 3
R2#SH IP ROUTE
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route


Gateway of last resort is not set


10.0.0.0/30 is subnetted, 2 subnets
C 10.2.2.0 is directly connected, Serial0/0
D 10.1.1.0 [90/2681856] via 10.2.2.1, 00:28:39, Serial0/0
D 192.168.2.0/24 [90/2707456] via 10.2.2.1, 00:28:32, Serial0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0


Well, I put in a Host instead of a Cloud and used the Virtual PC feature in GNS3 and it worked. But it would sure be cool if I could ping through my computer's physical Loopback I created with hardware wizard.

Comments

  • jdballingerjdballinger Member Posts: 252
    Danny, if you right-click on the Cloud in GNS3, you can select 'Configure'. In there you should see a drop down box that will let you select whatever network adapter you would like on your computer. Give this a go and see if that helps.
  • JustFredJustFred Member Posts: 678 ■■■□□□□□□□
    Danny in case you are not able to add the network adapter, you will have to open GNS3 by right clicking on it and choosing runas admin.
    [h=2]"After a time, you may find that having is not so pleasing a thing, after all, as wanting. It is not logical, but it is often true." Spock[/h]
  • danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
    Ok, I just tried that and still no go: I followed some online advice and put in a persistent route to see if that would make it happen. But the only way I can get in is by putting a cloud pointing to my Local Area Connection, which of course knocks me off the net.


    Here is my command line Route Print output: While with 192.168.2.1 as my f0/0 in GNS3
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    169.254.0.0 255.255.0.0 192.168.1.5 1
    169.254.0.0 255.255.0.0 192.168.1.8 1
    192.168.1.49 255.255.255.0 192.168.1.11 1
    192.168.2.0 255.255.255.0 192.168.2.1 1
    0.0.0.0 0.0.0.0 192.168.2.1 Default
    ==================================================================


    IPv6 Route Table
    ==================================================================
    Active Routes:
    If Metric Network Destination Gateway
    1 306 ::1/128 On-link
    31 276 fe80::/64 On-link
    22 286 fe80::/64 On-link
    10 276 fe80::/64 On-link
    24 276 fe80::/64 On-link
    25 276 fe80::/64 On-link
    22 286 fe80::28bc:5b16:97de:c850/128
    On-link
    10 276 fe80::a018:26ce:ab1a:4680/128
    On-link
    31 276 fe80::a8f2:12df:4b10:9a79/128
    On-link
    24 276 fe80::a94a:61ff:3b98:c13/128
    On-link
    25 276 fe80::c179:e3a4:9a8f:81d/128
    On-link
    1 306 ff00::/8 On-link
    31 276 ff00::/8 On-link
    22 286 ff00::/8 On-link
    10 276 ff00::/8 On-link
    24 276 ff00::/8 On-link
    25 276 ff00::/8 On-link
    ==================================================================
    Persistent Routes:
    None

    THIS IS A PING FROM CMD TO ANOTHER ROUTER IN MY NETWORK
    C:\Users\NewOwner>ping 10.1.1.1


    Pinging 10.1.1.1 with 32 bytes of data:
    Request timed out.
  • danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
    Below I pasted someones solution but when I try to share from my Local Area Connection and put my Adapter on obtain address automatically, I get Autoconfiguration IPv4 Address. . : 169.254.200.80, instead of a routable IP. (See below Paste)


    Simple solution for you to fix this issue. just you need to use sharing in your wireless nic or physical nic which ever you using for internet.

    follow below steps

    Step 1: first remove all ip address from you loopback adapter as its default.
    Step 2 : then click loopback adapter properties-->Sharing--> check the box (Allow network users to connect through this computer's internet connections.
    Step 3 : after you follow above 2 step, your loopback adapter automatic will assign ip address. That subnet ip address you need to configure in GNS3 devices which ever you have connected with cloud.
    Step 4: configure static ip address for your wireless nic subnet inside GNS3 to pointing to loopback ip address.

    Step 5: Configure gateway on loopback adapter as gns3 device ip address. Then bindo you will able to ping.

    For example here you go my config for refer.

    GNS3 router

    interface FastEthernet0/0
    ip address 192.168.137.2 255.255.255.0
    duplex auto
    speed auto

    ip route 192.168.233.0 255.255.255.0 192.168.137.1

    R1#ping 192.168.233.132

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.233.132, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 16/26/44 ms

    MY WIFI NIC IP ADDRESS 192.168.233.132.


  • networker050184networker050184 Mod Posts: 11,962 Mod
    I think you are making this more complicated than it needs to be. If you can ping the directly connected router you have connectivity. Do you have a route for the other subnets though? Where is the default route on your PC pointing? It's all about the routing.
    An expert is a man who has made all the mistakes which can be made.
  • danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
    That may be True. I tend to split hairs the first time I try something. I have 3 routers up:
    R1 F0/0:192.168.2.1 /24, S0/0:10.1.1.2 /30
    R2 S0/0:10.2.2.1 /30 S0/1:10.1.1.1 /30,
    R3 S0/0:10.2.2.2 /30


    I agree with you. This is my ping output and the IPs and EIGRP routes are in my 1st post along with my loopback settings. My default route on my loopback is 192.168.2.1.
    C:\>ping 192.168.2.1


    Pinging 192.168.2.1 with 32 bytes of data:
    Request timed out.
    Reply from 192.168.2.1: bytes=32 time=29ms TTL=255
    Reply from 192.168.2.1: bytes=32 time=22ms TTL=255


    Ping statistics for 192.168.2.1:
    Packets: Sent = 3, Received = 2, Lost = 1 (33% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 29ms, Average = 25ms
    Control-C
    ^C
    C:\>ping 10.1.1.1


    Pinging 10.1.1.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    1.png 23.9K
  • networker050184networker050184 Mod Posts: 11,962 Mod
    So look at your PC and routers route tables. Where is the PC going to send packets addressed to 10.1.1.1? Where is that router going to send packets addressed to your PC?
    An expert is a man who has made all the mistakes which can be made.
  • danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
    Well I first added this route in the windows command line to get to GW
    route ADD 192.168.2.0 MASK “255.255.255.0 192.168.2.1

    For R1 I have:
    R1(config)#do sh run | section eigrp 1
    router eigrp 1
    network 10.1.1.0 0.0.0.3
    network 192.168.1.0
    network 192.168.2.0
    no auto-summary
    Which gets the packet to R2's 10.1.1.1

    The routes are in the tables. I can ping anywhere from within GNS3.
    R1
    Gateway of last resort is not set


    10.0.0.0/30 is subnetted, 2 subnets
    D 10.2.2.0 [90/2681856] via 10.1.1.1, 1d04h, Serial0/0
    C 10.1.1.0 is directly connected, Serial0/0
    C 192.168.2.0/24 is directly connected, FastEthernet0/0
    D 192.168.3.0/24 [90/2707456] via 10.1.1.1, 1d04h, Serial0/0

    On R2
    Gateway of last resort is not set


    10.0.0.0/30 is subnetted, 2 subnets
    C 10.2.2.0 is directly connected, Serial0/1
    C 10.1.1.0 is directly connected, Serial0/0
    S 192.168.2.0/24 [1/0] via 10.1.1.2
    D 192.168.3.0/24 [90/2195456] via 10.2.2.2, 1d04h, Serial0/1

    allows me to get back to R1 and then back to the loopback. Am I right?

    I agree that if I can get to 192.168.2.1, which is R1, I should be able to get to the others, so I'm doing something wrong.
  • networker050184networker050184 Mod Posts: 11,962 Mod
    Ok so where is the PC going to route 10.1.1.1?
    An expert is a man who has made all the mistakes which can be made.
  • danyzukodanyzuko Member Posts: 40 ■■□□□□□□□□
    Router 1
    192.168.2.0 255.255.255.0 192.168.2.1 1
    0.0.0.0 0.0.0.0 192.168.2.1 Default

    I know this is a probing question. I would think it will check it's Routing table and use the default route to get to R1 at 192.168.2.1 - Is that not right?
    Then R1 will see in it's table that 10.1.1.1 needs to go out port S0/0 10.1.1.2 to R2 on S0/1 at 10.1.1.1
    What am I missing?
Sign In or Register to comment.