François Buntschu

Yes, as written. Otherwise the ping from ipterm2 to 10.10.10.95 will not work. ``` root@gns3-ipterm-2:~# ping 10.10.10.95 PING 10.10.10.95 (10.10.10.95) 56(84) bytes of data. 64 bytes from 10.10.10.95: icmp_seq=2 ttl=255...

I made the config you proposed. But I put 10.10.10.10/24 as address for the bridge, as 10.10.10.95 is assigned to a VM in the VMWare cluster. ``` gns3@gns3vm:~$ sudo brctl...

Here some additional troubleshooting steps: it seems that the _gns3tap0-4_ interfaces correspond to the "cable" connected from the Switch1 to Cloud1 and _gns3tap1-4_ is for the connection between ipterm2 and...

Hi, After a new try with a fresh 2.2.20 install, I have the same issues with directly connected ethernet Interfaces via clouds. Also made a try with a bridge with...

Just try right now with the 2.2.21 release (fresh install again). With or without the bridge-workaround, still the same issue.

Has this issue been resolved in 2.2.22 ?

This issue is has been assigned to the 3.1 milestone, when will this new version of GNS-3 be released ?