![]() ![]() Open a command prompt as an Administrator and issue the following sudo /etc/init.d/networking restart If the virtual NIC was already installed, a reboot is not required. (Optional) If you’ve just installed/enabled the virtual NIC for the first time, you will need to reboot your PC so that the NIC is visible in GNS3.Next, ensure the virtual adapter is up and running on the host machine. Please see the appendix for more information.Įnsure that the NIC is set to “Host Only” and that the “Connect a host virtual adapter to this network” box is ticked. Note: You can achieve lab isolation while maintaining internet connectivity by installing a second network card in the VM. Having said that, the NIC can be switched back to “Bridge” or “NAT” mode at any time should you need to (e.g for software downloads and/or updates).Īs isolating a lab from a production environment is more important the Ansible VM having internet access, this tutorial will cover the use of a “Host Only” NIC. The only downside of using “Host Only” mode is that your VM loses connectivity to the internet. You would like to use multiple subnets in your Ansible lab network without having to make changes to your VM’s route table.You would like to completely isolate your production environment from your Ansible lab network.You would make the move if either of the following is true: Sudo apt-add-repository ppa:ansible/ansibleĪt this point you have the option to move the VM’s NIC to “Host Only” mode or leave it in its current mode. Sudo apt-get install software-properties-common ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |