Lab 1.2 Installation of Pnetlab & upload chr on Pnetlab

LAB 1.2 | Installation of Pnetlab & upload chr on Pnetlab

Name : Yunita Prima Rizka

Class : X TKJ A

>PNETLAB installation

1.  First download the file in the form of ova type on the site: https://pnetlab.com/pages/download

2. After the file is downloaded, enter the file manager then click PNET_4.2.10, then open using open with vmware player.

3. Perform the import process of the machine name name let default. Wait for the pnetlab import process to complete.

4. The result will be a new vm with the name vnetlab according to what we imported earlier with an ip address of 192.168.150.128 , Before running pnetlab there are several steps that need to be installed or activated.

5. Turn off the machine first, by clicking the X on the right side and then clicking power off.

6. Make sure the wm name appears, then continue with the setting changes. By clicking on the name of the vm that was created, then click edit virtual machine settings.

7.  First checklist intel VT-x or AMD-V/RVI virtualization on the virtual machine settings menu⇒ select processor⇒ give a check mark to intel VT-X/EPT or AMD-V?RVI virtualization.

8. To start the PNETLab installation process again, please click the Start button.

9.  Use user root and password pnet as shown in the login view here it can be seen that the user= root and the password is pnet.

10. Please enter a new root password  according to your preference. For example, you can use 123 as the password. Be sure to remember this password well, as it will be used to access important settings in PNETLab. After entering the password, proceed to the next step by clicking ok.

11. Re-enter the new password as before here it can be seen that the password will not appear but it is still inputted because the password will not appear, then click ok.

12. Please enter the domain name you want to use, such as pimaw.net, so we can help you check its availability and make sure it fits your needs, then click ok.

13. Because the ip address used to remote pnetlab is the use of ip, we can choose the one that uses ip dhcp, then click ok.

14. Please enter the Network Time Protocol (NTP) that corresponds to your region. However, if you do not want to change the settings, you can leave them in the default state, so that the system will automatically use the predefined default settings, then click ok.

15. In terms of connection, we will choose direct connection directly to remote pnetlab, wait for the pnetlab reboot process, then click ok.

16.  Enter the root user and password that was entered earlier. Here it can be seen that the ip address of pnetlab already exists, namely 192.168.150.128. The display if successfully logged in will be as shown below:

17.  Enter the web browser then enter your pnetlab ip address Because we don't have a user we can use online mode. Select online mode.

18. Enter the username admin and password pnet enter the captcha code that appears then login. Here can be seen on the display. Login using admin password pnet, captcha fill in first. 

19. The dashboard PNETLab display has been successfully accessed, indicating that the system is running normally and is ready to be used for configuration, network simulation, and various other activities according to your needs.

>Upload in pnetlab

1. Upload the chr file to pnetlab first. Download chr at https://mikrotik.com/download select raw dist image. After the chr file has been downloaded, the next step is to extract the chr file.

2. Download win scp with link: https://winscp.net/eng/download.php then download it as shown in the picture, by clicking download winscp 6.3.7.

3. install the win scp that has been downloaded, by clicking the winscp file in the file manager, then the Select Setup Install Mode will appear, select Install For All Users.

4. After clicking Install For All Users, a display will appear like this, in the License Agreement section click accept to continue the installation process.

5. In the setup type section, select an option typical installation (recommended), then click next to continue the installation process.

6. In the User interface style section, select an option comander, then click next to continue the installation process.

7. The WinSCP installation process has reached the final stage, which is Ready to Install, to continue the installation process click install.

8. The image below is the final stage of the WinSCP installation process, called Completing the WinSCP Setup Wizard, click finish to complete the winscp installation process.

9. After the winscp installation process is complete, the next step is to log in to winscp, in the file protocol section select SFTP, in the ip section enter the ip that was on vmware earlier, then enter the user and password that is on vmware, then click login.

10. The image below shows the security warning when first trying to log in to the server via WinSCP, The figure below shows the security warning when first trying to login to the server via WinSCP, select accept so that the login process will continue, and users can start using WinSCP to transfer files to/from the server.

11. Enter the opt/unitlab/addons/qemu folder and then create the proxy folder, by right-clicking on the ... file, then select the new option and select the directory option.

12. for proxy we create a folder along with the version. for example mikrotik-6.49, then click ok.

13. The process of uploading CHR files (.img) to the server using WinSCP, by means of the left panel, the user selects the chr-6.49.13.img file, which will be sent to the server seen in the right panel. After that click Upload at the top of the WinSCP toolbar to start the upload process, an Upload window will appear displaying the destination path on the server, which is /opt/unetlab/addons/qemu/mikrotik-6.49/. then click ok.

14. Make sure the file is uploaded on the right panel.

15. Change the file extension to hda.qcow2 because it is based on qemu.

16. Reload the file on the server. Change the file permissions with the command : /opt/unetlab/wrappers/unl_wrapper-a fixpermissions.

17. Enter the PNETLAB platform, here I use the firefox browser. Then click new lab.

18. Create a new lab, here I give an example with the name: latihan. then click add to add the new lab that we want to create.

19. The figure below is the interface of PNETLab, a network virtualization platform for simulating and testing network devices.

20. Add a device, by right-clicking on the PNETLAB interface, then selecting the node option.

21. In the ADD A NEW NODE window, there is a Template option that allows users to select the type of device they want to add. In the list of available devices, select the MikroTik RouterOS option, which is used to add a MikroTik-based router to the network simulation.

22. Here I added a router device, change the ram to 64 gb first.

23. After replacing the ram, click save to have the device added.

24. The picture below is a display of the proxy router os that has been created.

25. If you want to add a device, add the device again then pull the cable as shown below then connect it to the device with the specified interface.

26. if you have connected the two devices by pulling the plug-shaped cable to the destination device then specify the interface, then click save.

27. On the left navigation bar enable HTML Console, The function of HTML Console in PNETLab is to provide direct access to network devices that have been added in the simulation lab through a web-based interface. With this feature, users can access and configure devices without the need to use additional applications such as PuTTY or SecureCRT. 

28. After connecting the lines between the devices we activate the two devices. How to activate it click on the proxy select start.

29. If the color of the device indicator in PNETLab turns green, it indicates that the device is running normally or is on.

30. The remote process to the MikroTik device has been successful, meaning users can now access and manage the device remotely. With this success, users can begin to perform configuration, network settings, and other administrative tasks through available interfaces, such as WinBox, WebFig, or SSH/Telnet Terminal, according to their needs and preferences.

31. Then shutting it down is to click on the proxy and then select stop.