Cloud Computing Lab Assignment
Cloud Computing Lab Assignment
1
2. Hardware Requirement:
Device name DESKTOP-HA44D82
Processor 11th Gen Intel(R) Core (TM) i5-1135G7 @ 2.40GHz 2.42 GHz
Installed RAM 16.0 GB (15.7 GB usable)
Device ID E1504907-3A30-4145-BC13-729ADC88C450
Product ID 00342-42610-20593-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
4. Lab Tasks:
Create three virtual machines using VirtualBox. Choose any guest operating system
(e.g., Kali, Fedora).
2
a. VM1: Use Bridged Adapter
b. VM2: Use NAT
c. VM3: Use Host-Only Adapter
3
Assign unique static IP addresses to each VM based on the network configuration.
4
5
Ensure that all VMs can ping each other and access the internet (if applicable) based
on the network settings.
6
Table illustrating the connectivity between various VM Network Settings, indicating which
settings can successfully ping each other:
Network Bridged-Adapter NAT Host-Only Adapter
Bridged-Adapter yes no no
NAT yes yes yes
Host-Only Adapter no no yes
7
Setting up ssh in for file transfer in VM1 (Bridged Network Adapter).
8
Creating a file ‘test.txt’ in VM2 (NAT Network Adapter) and sending it to VM1
(Bridged Network Adapter) via scp command.
9
5. Observations:
I was unable to use a wired (Ethernet) connection in a virtual machine due to
incorrect network settings. This was resolved by correctly configuring VM's network
adapter in VirtualBox.
I faced ‘port 22: Connection refused error’ while executing file transfer as SSH
service on the remote machine is either not running, blocked by a firewall which was
bypassed by a series of steps and enabling ssh on the VM.
10
After correct installation and configuration of open-ssh-server, I was able to perform
file transfer from VM2 to VM1:
11
7. Conclusion:
Network Configuration Skills: Developed the capability to install and configure
different types of network adapters for various purposes in a virtual environment.
IP Management: Learned how to provide and control static IP addresses for various
network adapters.
Connectivity Testing: Pinged and tested the network connectivity that VM share with
different VM network adapter configurations.
File Transfer: Gained experience in transferring files from one VM to another.
8. References:
https://cloud.google.com/compute/docs/instances/transfer-files
https://www.youtube.com/watch?v=a1eLHscKN2k
https://serverfault.com/questions/812882/how-to-move-files-from-one-vm-to-other-
vm-in-a-linux-basedserver-using-ssh
https://uoa-eresearch.github.io/vmhandbook/doc/copy-file-linux.html
https://chatgpt.com/
9. Appendix:
NAT (Network Address Translation): This mode allows VMs access to the internet
while concealing the IP of the VM behind the Host Internet IP. Nevertheless, the VMs
cannot talk to each other or external physical machines apart from the host. A VMs'
IP addresses are provided by a specialized DHCP such that, even if the VMs have the
same IP, they cannot interfere with one another.
Host-Only Network: VMs operate in this scope where they and the host can talk to
one another but not to outside networks or the internet. Here again, a virtual DHCP
server is used to give every single one of the VMs an address which disables the
access of VMs to the outside world for protection purposes.
Bridged Network: In this mode, the VMs act like physical devices connected to a
physical network with other Network devices, VMs, and the internet. VMs receive
direct individual IPs from the real router. The security feature is the use of strong
isolation to ensure that there is no ingress and egress of traffic without permission
and connectivity is undaunted.
12