In my VMware Virtual Network Editor configuration, eth1 of the cloud is connect to eth1 of the gns3 vm. Eth1 of the GNS3 VM is connected to VMware VMnet8 - which is a NAT interface. Simple ip connectivity works from inside the gns3 topology on eth1 of the cloud to the internet. But HTTPS websites can not be reached because of TLSv1.3 Change Cipher Spec Protocol: Change Cipher Spec. I think TLS is detecting the GNS3 VM as a MITM, or the GNS3 VM has a bug in it somewhere.
However the NAT appliance is specifically designed to do this task, and it works.
Using the NAT appliance and the VMware VMnet8 capability will generate 2 default routes.
That is a nonsensical design.
In my VMware Virtual Network Editor configuration, eth1 of the cloud is connect to eth1 of the gns3 vm. Eth1 of the GNS3 VM is connected to VMware VMnet8 - which is a NAT interface. Simple ip connectivity works from inside the gns3 topology on eth1 of the cloud to the internet. But HTTPS websites can not be reached because of TLSv1.3 Change Cipher Spec Protocol: Change Cipher Spec. I think TLS is detecting the GNS3 VM as a MITM, or the GNS3 VM has a bug in it somewhere.
However the NAT appliance is specifically designed to do this task, and it works. Using the NAT appliance and the VMware VMnet8 capability will generate 2 default routes. That is a nonsensical design.
Nirmal fixed this issue by using internet connection sharing on his windows 10 host https://gns3.com/community/featured/nat-issue-in-gns3
I am not changing my host to use internet connection sharing.
He wants to use the cloud. I put a VM in vmware and vmnet8 works okay fine. I am not troubleshooting this any more because the NAT appliance works.
If it is broke, you can open it up as a bug, or close it as a "won't fix".