GNS3 Sporadic LAN Connectivity

marksargent · ‎07-24-2012

Hi All,

I'm using GNS3 0.8.2 on Win7. I have created a local network cloud and given a 7200 an IP of 10.1.1.10/24. ADSL router on this network is at 10.1.1.1. The Win7 machine is at 10.1.1.2. A Linux VM on VMware Server 2.0, on a bridged e1000 is at 10.1.1.4. I can ping 10.1.1.10 from 10.1.1.4 and vice-versa, but cannot ping 10.1.1.1 from either. I also cannot ping 10.1.1.2 from either, and weirder, from the Win7 command prompt, it cannot ping itself on 10.1.1.2 but can ping 10.1.1.1 or 10.1.1.4. I'm considering rebooting the Win7 host machine, but if anyone has any other suggestion, that'd be good. Thanks.

ADSL Router 10.1.1.1

Win7 10.1.1.2

Linux VM on Win7 10.1.1.4

7200 in GNS3 10.1.1.10

Mark

cadet alain · ‎07-25-2012

Hi,

Can you put your NIC as a private network profile on the Windows 7.

Regards.

Alain.

Don't forget to rate helpful posts.

marksargent · ‎07-25-2012

Hi Alain,

apologies, forgot to mention, windows firewall is disabled. I am running a free zonealarm app, but even with it disabled too, problem still exists. Thanks.

Mark

cadet alain · ‎07-25-2012

Hi Mark,

Did you verify the network profile is private though ?

Regards.

Alain.

Don't forget to rate helpful posts.

marksargent · ‎07-25-2012

Below shows the network types. I hope that is what you wanted to see. Thanks.

Mark

cadet alain · ‎07-25-2012

yes that was what I wanted to see. Can you provide a screenshot of the GNS3 topology with the cloud connection.

what is the arp cache on the router telling about the Windows 7 mac address? what is a debug ip pack detail 101 along with access-list 101 permit icmp any any is telling when pinginh the Windows 7 from the router ?

Can you also provide ipconfig and netstat -rn output from the Windows machine.

Regards.

Alain

Don't forget to rate helpful posts.

marksargent · ‎07-26-2012

The ADSL router is not a cisco router where I can insert the access-list you suggest, although I do have cli access to the shell. I disabled/enabled the problem connection to no avail. I'm suspecting it's local to the host machine as it cannot ping itself but has no issue pinging the ADSL router or the linux VM. As you can see from the output, it could at one time ping it's own IP, but then just hangs on the 2nd attempt and continues to do so. Thanks.

Mark

# arp

Address HWtype HWaddress Flags Mask Iface

10.1.1.6 ether 00:22:75:F2:3B:30 C br0

10.1.1.2 ether BC:AE:C5:6D:20:0B C br0

# ping 10.1.1.2

PING 10.1.1.2 (10.1.1.2): 56 data bytes

64 bytes from 10.1.1.2: icmp_seq=0 ttl=128 time=0.0 ms

64 bytes from 10.1.1.2: icmp_seq=1 ttl=128 time=0.0 ms

64 bytes from 10.1.1.2: icmp_seq=2 ttl=128 time=0.0 ms

64 bytes from 10.1.1.2: icmp_seq=3 ttl=128 time=0.0 ms

64 bytes from 10.1.1.2: icmp_seq=4 ttl=128 time=0.0 ms

--- 10.1.1.2 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 0.0/0.0/0.0 ms

# arp

Address HWtype HWaddress Flags Mask Iface

10.1.1.6 ether 00:22:75:F2:3B:30 C br0

10.1.1.2 ether BC:AE:C5:6D:20:0B C br0

#

Connection to host lost.

C:\Users\Mark>ping 10.1.1.1

Pinging 10.1.1.1 with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time=14ms TTL=255

Reply from 10.1.1.1: bytes=32 time=7ms TTL=255

Ping statistics for 10.1.1.1:

Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 7ms, Maximum = 14ms, Average = 10ms

Control-C

^C

C:\Users\Mark>ping 10.1.1.2

Pinging 10.1.1.2 with 32 bytes of data:

Control-C

^C

C:\Users\Mark>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::f0e2:f04:878a:7844%11

IPv4 Address. . . . . . . . . . . : 10.1.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.1.1.1

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::cc1b:14e5:1906:df5f%16

IPv4 Address. . . . . . . . . . . : 192.168.193.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::e8e8:3f3c:6fab:984d%17

IPv4 Address. . . . . . . . . . . : 192.168.85.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{42929810-6959-45F7-9500-BAE17466D29F}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{8B1BB3B1-6182-4214-8794-5FC20B26F8CC}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{A105DD13-D001-4FAD-BC5A-D50AE2244003}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:14f5:3f1:8356:65d9

Link-local IPv6 Address . . . . . : fe80::14f5:3f1:8356:65d9%14

Default Gateway . . . . . . . . . : ::

C:\Users\Mark>netstat -rn

===========================================================================

Interface List

11...bc ae c5 6d 20 0b ......Realtek PCIe GBE Family Controller

16...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1

17...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8

1...........................Software Loopback Interface 1

12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3

14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

===========================================================================

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.2 20

10.1.1.0 255.255.255.0 On-link 10.1.1.2 276

10.1.1.2 255.255.255.255 On-link 10.1.1.2 276

10.1.1.255 255.255.255.255 On-link 10.1.1.2 276

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306

127.0.0.1 255.255.255.255 On-link 127.0.0.1 306

127.255.255.255 255.255.255.255 On-link 127.0.0.1 306

192.168.85.0 255.255.255.0 On-link 192.168.85.1 276

192.168.85.1 255.255.255.255 On-link 192.168.85.1 276

192.168.85.255 255.255.255.255 On-link 192.168.85.1 276

192.168.193.0 255.255.255.0 On-link 192.168.193.1 276

192.168.193.1 255.255.255.255 On-link 192.168.193.1 276

192.168.193.255 255.255.255.255 On-link 192.168.193.1 276

224.0.0.0 240.0.0.0 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 10.1.1.2 276

224.0.0.0 240.0.0.0 On-link 192.168.193.1 276

224.0.0.0 240.0.0.0 On-link 192.168.85.1 276

255.255.255.255 255.255.255.255 On-link 127.0.0.1 306

255.255.255.255 255.255.255.255 On-link 10.1.1.2 276

255.255.255.255 255.255.255.255 On-link 192.168.193.1 276

255.255.255.255 255.255.255.255 On-link 192.168.85.1 276

===========================================================================

Persistent Routes:

None

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

14 58 ::/0 On-link

1 306 ::1/128 On-link

14 58 2001::/32 On-link

14 306 2001:0:9d38:953c:14f5:3f1:8356:65d9/128

On-link

11 276 fe80::/64 On-link

16 276 fe80::/64 On-link

17 276 fe80::/64 On-link

14 306 fe80::/64 On-link

14 306 fe80::14f5:3f1:8356:65d9/128

On-link

16 276 fe80::cc1b:14e5:1906:df5f/128

On-link

17 276 fe80::e8e8:3f3c:6fab:984d/128

On-link

11 276 fe80::f0e2:f04:878a:7844/128

On-link

1 306 ff00::/8 On-link

14 306 ff00::/8 On-link

11 276 ff00::/8 On-link

16 276 ff00::/8 On-link

17 276 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

C:\Users\Mark>

marksargent · ‎07-26-2012

System reboot has not resolved the issue of pinging itself, but I can now ping 10.1.1.2 from both the ADSL router, 10.1.1.1, and the linux VM, 10.1.1.4. I can also ping from the GNS3 R1 to the linux VM and the ADSL router but not the host IP 10.1.1.2. Thanks.

Mark

marksargent · ‎07-26-2012

Put the host machine into "sleep" mode overnight and when waking it up, I can no longer ping from the linux VM to the ADSL router or R1 in GNS3. Can ping the host machine on 10.1.1.2, though. Still the host machine cannot ping itself but it can ping the ADSL router and linux vm. It cannot ping Syd1 router in GNS3. Syd1 cannot ping anyone now. Weird. Thanks.

Mark