Lab 1.3 Internet Access

Lab 1.3 | Internet Access

Name : Yunita Prima Rizka

Class : X TKJ A

>Adding devices in pnetlab

1. Next we will add the device to pnetlab.

2.  Close the lab first and then select the device tab.

3. Add the chrome device to pnetlab, by clicking get device in the chrome box.

4. Wait for the Chrome download process to complete After that, also make sure that the Chrome installation process has been fully completed without any interruptions or errors. As a sign that the installation was successful, make sure the added to pnetlab notification appears.

5. In the next step, we will create a new exercise again.

6. The name to use for the new exercise is latihan2, then click add.

7. If you have entered the PNET interface, right-click to add a device, then select node.

8. 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 docker.io option.

9. Add one of the client nodes in pnetlab, follow as shown below in the red box, then click select.

10. Click the device that has been added, then scroll down, in the primary console section select RDP to remote the device, then click save.

11.  Make sure a PC-01 appears in the workspace.

12. Click on the device then click start to make sure the color turns green. This is the client that will be used as a test later.

13. To remotely click on the device an rdp will appear like this click ok.

14. This warning reminds users to be cautious before continuing the connection to the remote computer. If the IP is from a trusted network, users can select Connect.

15. Then the rdp will appear again, continue by clicking ok to enter the remote session.

16. Next, chrome will appear like a Windows PC client. Google Chrome runs in a virtual environment in PNetLab.

17.  If you want to check the connection via terminal close first chrome and then right-click run terminal. For example ping test.

18. If you want to exit the terminal after you have finished using it, you can do so by selecting the File menu located at the top of the terminal window. After that, locate and click the Close Tab option to close the current terminal session.

19. Once the terminal is successfully closed, select run chrome again.

>Connecting mikrotik with vpcs in pnetlab.

1. Return to home to create a new workspace or reuse an old one

2. Create a new lab name, here I use the name: admin, then click add.

3. If you have entered the PNET interface, right-click to add a device, then select node.

4. Add a new node for the mikrotik router os that we just uploaded.

5. After selecting the Mikrotik RouterOS, scroll down the settings in the RAM = 64 and interface = 5 section, then scroll down again and click save.

6. Add another device, by right-clicking and selecting node.

7. After clicking the node, just scroll down and click save.

8. Connect between the proxy and the pc, if so, a display like this will appear and click save to connect it.

9. Next step Activate the HTML Console first.

10. Then start both devices so that what was previously on each device is still red, after starting it will become green.

11. Adding a label click on the cable wait for the signature to appear pointing then right-click, and select the edit option.

12. In the type section, select straight, and in the label type the network you want, for example 192.168.1.0/24, then click apply on the right.

13. Setting Ip address on the mikrotik tab, before setting the ip address, first give a name to the router with the command system identity set name=(name to be used), click enter. Then add an ip address with the command ip address add adrress= 192.168.1.1/24 interface=ether1, click enter, and type the command ip address pr to display IP address information from all network interfaces, click enter.

14. Setting the ip address on the client on the VPC tab, by adding the command ip 192.168.1.2/24 192.168.1.1, click enter. Why are there 2 ip in the command? because the ip whose last octet is the number 2 belongs to the client, while the one whose last octet is the number 1 is the ip on the proxy tab. Then type the save command, and to check the ip, you can enter the show ip command.

15. On the VPC tab, verify the connection with a ping test from the client. By entering the command ping 192.168.1.1, then enter. Why use that ip? because that ip is the ip of the proxy tab / admin ip. If the display appears as shown below, it is successful.

16. On the microctic tab, verify the router with a ping test. By entering the command ping 192.168.1.2, then enter. Why use that ip? because that ip is the ip of the vpc / ip client tab. If the display appears as shown below, it is successful.