[2.1.0dev6] : remote server container doesn't talk to local server container

[AJNOURI]

A container on remote server doesn't talk to container from local server.
It is back to back connection

remote-to-remote = OK
local-to-remote = NOK

No error message showed

[grossmj]

I haven't found an issue so far. I have tested between 2 endhost, one running in the GNS3 VM and one running locally.

[AJNOURI]

I could reproduce the same behavior on windows (in addition to linux): devices not installed on the same locations (gns3 VM, local host and remote server) do not talk to each other.

Tested with these devices (cloud/nat/containers/VPCS)

I am suspecting the same problem is lurking behind lots of reported issues like:

• layer2 switch doesn't work
• NAT device doesn't work, cannot access Intenet
• ex IOS device do not ping
• ...

[grossmj]

I will investigate more. On what IP address is the local server bound? You can see this in the GNS3 preferences.

[grossmj]

@AJNOURI :)

[AJNOURI]

Sorry for the delay.
Each time, I am using an ephemeral packet.net installation.

[grossmj]

So if I understand the GNS3 VM runs on packet.net every time? Have you tried with a local GNS3 VM?

[AJNOURI]

Because I don't have Windows installed on hardware machine, and to avoid testing GNS3 on windows VM, each time I create a windows server on packet.net and I install GNS3 + GNS3 VM.
So GNS3 VM was running locally.

[grossmj]

I tested with one local server, a remote server on packet.net and a GNS3 VM running locally in VMware.

The local server was bound to IP address 172.16.253.6 (VPN tunnel address), the GNS3 server on the remote Packet.net host bound to IP address 172.16.253.1 (VPN tunnel address) and the GNS3 server running in the GNS3 VM bound to IP address 172.16.1.128 (DHCP address from vmnet1 interface).

Docker containers gns3-endhost-1 (local server) and gns3-endhost-packet-1 (packet.net) could communicate without any issue, so does R1 (local server) and R2 (packet.net) as well as VPCS-1 (local server) and VPCS-2 (packet.net).

Of course the problem happened when I added and configured gns3-endhost-1 running in the GNS3 VM, this node could not communicate with the 2 other containers on local server and packet.net. Ehlers's advice to change the eth0 IP of the GNS3 VM should work but I am considering if we could have an option to set up a VPN in the VM.

[AJNOURI]

We should think of a scalable solution in which any number of GNS3 node with any combination of (GUI-only, local, GNS3 VM, gns3server-only) could seamlessly work together.

I think openvpn is point-to-point, so not so scalable.