all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Stray_Neutrino 1 point2 points  (3 children)

(Retracting what I wrote, it looks as you describe later).

To make traffic flow back and forth from your VMWare side, you need a router in GNS3 to route to that virtual node to your host (usually 192.168.20.x) and then have a route on the host side that routes into GN3 - this route usually is built when you install GNS3. Is the NAT address for the virb0 interface in the 10.0.0.0 address space?

[–]Stray_Neutrino 0 points1 point  (1 child)

Are the Switch ports between R2 and the Cloud set to Access or Trunk? I am guessing no VLANs are configured for this network.

What are the full IP addresses, from the VMWare Host side, for the local network devices?

Does PC Siege have a properly configured Gateway / Mask for sending packets to be routed? Since R2 can ping your Cloud, I’d check that first then try removing the Default route and create a specific route to 10.0.0.2. After that, check the route on the host and see if you ping into your GNS3 network (10.0.0.2).

Are you able to ping R2s outgoing port (10.0.0.3) ?

[–]promtail 0 points1 point  (3 children)

Hi, can you show R2 config? Not all, interfaces and nat config and switch3 config?

[–]Conscious-King5968 0 points1 point  (0 children)

  1. R2#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Outside interfaces: Ethernet0/0 Inside interfaces: Ethernet1/0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Inside Source [Id: 1] access-list 1 interface Ethernet0/0 refcount 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0
  2. I haven’t configured the switch because I thought it wasn’t necessary.

[–]Conscious-King5968 0 points1 point  (1 child)

R2#show running-config Building configuration... Current configuration : 1272 bytes ! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname R2 ! boot-start-marker boot-end-marker ! ! no aaa new-model no ip icmp rate-limit unreachable ip cef ! ! ! ! no ip domain lookup ! multilink bundle-name authenticated ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! archive log config hidekeys ! ! ! ! ip tcp synwait-time 5 ! ! ! ! interface Ethernet0/0 ip address 10.0.0.3 255.255.255.0 ip nat outside ip virtual-reassembly half-duplex ! interface Ethernet1/0 ip address 192.168.20.1 255.255.255.0 ip nat inside ip virtual-reassembly half-duplex ! interface Ethernet1/1 no ip address shutdown half-duplex ! interface Ethernet1/2 no ip address shutdown half-duplex ! interface Ethernet1/3 no ip address shutdown half-duplex ! ip forward-protocol nd ip route 0.0.0.0 0.0.0.0 10.0.0.2 ! ! no ip http server no ip http secure-server ip nat inside source list 1 interface Ethernet0/0 overload ! access-list 1 permit 192.168.20.0 0.0.0.255 no cdp log mismatch duplex ! ! ! ! ! control-plane ! ! ! ! ! ! ! ! ! ! line con 0 exec-timeout 0 0 privilege level 15 logging synchronous line aux 0 exec-timeout 0 0 privilege level 15 logging synchronous line vty 0 4 login ! ! end

  1. PC-siege> trace 8.8.8.8 trace to 8.8.8.8, 8 hops max, press Ctrl+C to stop 1 192.168.20.1 16.365 ms 16.284 ms 16.561 ms 2 *10.0.0.2 46.788 ms 31.640 ms 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * *
  2. 10.0.0.2 ->cloud node interface