Hi, I'm working on a project which connects the host in GNS3 with a remote computer. It's like when you send a ping to a host, actually a remote machine answers it. This project is supposed to combine the physical computer world with the "virtual" GNS3 device world. And I use the driver forwarding technique to achieve the goal of connecting. My driver could capture the in-going eth packets and out-going eth packets for every physical NIC in my Windows OS.

Here's the problem. I have built an experimental network in GNS3 as below. I have bind a GNS3 cloud node with an actual NIC (Loopback adapter in windows, IP: 192.168.2.128), When I ping the cloud node within the GNS3 device world (e.g. 192.168.2.2), I thought my driver software could have captured the ICMP packets from the NIC, but actually my driver could only catch the packet which the actual NIC sent back (from 192.168.2.128 to 192.168.2.2), but miss the one which the actual NIC received (from 192.168.2.2 to 192.168.2.128). This doesn't match my imagine for the principle of GNS3 NIC binding. Can anyone explain? Thx..