Featured Post
Featured Post
8.4.1.2 Packet Tracer - Skills Integration Challenge
8.4.1.2 Packet Tracer - Skills Integration Challenge Addressing Table Scenario Your company has won a contract to set up a smal...
Entah sudah berapa lama nggak nulis di blog ini, dan nggak tau ada angin apa yang mendorong buat nulis lagi. Sedikit berbagi cerita, sudah agak lama sih sebenarnya, itungan bulan kayaknya. Awal mula bisa tau aplikasi ini karena ketemu error di salah satu perangkat Ubiquity yang dipake, kalo gak salah karna posisi perangkat yang tidak sesuai dan saat itu harus pointing ulang perangkat ubiquitynya.
Nah, saat proses pointing ulang itu si teknisi make salah satu aplikasi yang basisnya Java, jadi kalo mau pake aplikasi ini pastikan sudah terinstall paket Java di komputer. Aplikasi yang tidak lain adalah Ubiquity Discovery Tool. Setelah diliat, aplikasi ini pada dasarnya adalah untuk mengetahui perangkat-perangkat Ubiquity yang terhubung dalam satu jaringan, caranya adalah melakukan scanning perangkat ubiquity yang terpasang, lumayan lengkap informasinya. Ada info tentang nama produknya, ip address nya berapa, MAC Address, dan versi Firmware perangkat Ubiquitynya. Nih contoh gambarnya,
Misalkan dalam satu jaringan itu kita punya 4 buah perangkat Ubiquity, maka yang muncul seperti gambar di atas ya 4 info perangkat. Kalo temen-temen mau atau butuh aplikasi Ubiquity Discovery Tool bisa langsung didownload di websitenya, klik aja link ini (Download), pilih yang paling atas. Yang pasti sih aplikasi ini cukup bermanfaat kalo pas ada gangguan pada perangkat Ubiquity, minimal untuk mengetahui perangkatnya terkoneksi atau tidak. Hehehe... Sekian dulu tulisan untuk kali ini... Nuwun...
Ubiquity Discovery Tool, Tool Scanning Perangkat Ubiquity
Posted by Soni Setiawan on Thursday, 14 September 2017
10.2.2.8 Packet Tracer - DNS and DHCP
Packet Tracer - DHCP and DNS Servers
Objectives
Part 1: Configure Static IPv4 Addressing
Part 2: Configure and Verify DNS Records
Background
In this activity, you will configure and verify static IP addressing and DHCP addressing. You will then configure a DNS server to map IP addresses to the website names.
Note: Packet Tracer only simulates the process for configuring these services. DHCP and DNS software packages each have their own unique installation and configuration instructions.
Part 1: Configure Static IPv4 Addressing
Step 1: Configure the Inkjet printer with static IPv4 addressing.
The home office computers need to know the printer’s IPv4 address to send information to it. The printer, therefore, must use a static (unchanging) IPv4 address.
a. Click Inkjet and click the Config tab, which displays the Global Settings.
b. Statically assign the Gateway address as 192.168.0.1 and the DNS Server address as 64.100.8.8.
c. Click FastEthernet0 and statically assign the IP address as 192.168.0.2 and the Subnet Mask address as 255.255.255.0.
d. Close the Inkjet window.
Step 2: Configure WRS to provide DHCP services.
a. Click WRS and click the GUI tab, and maximize the window.
b. The Basic Setup window displays, by default. Configure the following settings in the Network Setup section:
1) Change the IP Address to 192.168.0.1.
2) Set the Subnet Mask to 255.255.255.0.
3) Enable the DHCP Server.
4) Set the Static DNS 1 address to 64.100.8.8.
5) Scroll to the bottom and click Save.
c. Close the WRS window.
Step 3: Request DHCP addressing for the home laptop.
This activity focuses on the home office. The clients that you will configure with DHCP are Home Laptop and Tablet.
a. Click Home Laptop and click the Desktop tab > IP Configuration.
b. Click DHCP and wait until the DHCP request is successful.
c. Home Laptop should now have a full IP configuration. If not, return to Step 2 and verify your configurations on WRS.
d. Close the IP Configuration window and then close the Home Laptop window.
Step 4: Request DHCP addressing for the tablet.
a. Click Tablet and click the Desktop tab > IP Configuration.
b. Click DHCP and wait until the DHCP request is successful.
c. Tablet should now have a full IP configuration. If not, return to Step 2 and verify your configurations on WRS.
Step 5: Test access to websites.
a. Close the IP Configuration window, and then click Web Browser.
b. In the URL box, type 10.10.10.2 (for the CentralServer website) or 64.100.200.1 (for the BranchServer website) and click Go. Both websites should appear.
c. Reopen the web browser. Test the names for those same websites by entering centralserver.pt.pka and branchserver.pt.pka. Click on Fast Forward Time on the yellow bar below the topology to speed the process.
Part 2: Configure Records on the DNS Server
Step 1: Configure famous.dns.pka with records for CentralServer and BranchServer.
Typically, DNS records are registered with companies, but for the purposes of this activity you control the famous.dns.pka server on the Internet.
a. Click the Internet cloud. A new network displays.
b. Click famous.dns.pka and click the Config tab > DNS.
c. Add the following resource records:
d. Close the famous.dns.pka window.
e. Click Back to exit the Internet cloud.
Step 2: Verify the ability of client computers to use DNS.
Now that you have configured DNS records, Home Laptop and Tablet should be able to access the websites by using the names instead of the IP addresses. First, check that the DNS client is working properly and then verify access to the website.
a. Click Home Laptop or Tablet.
b. If the web browser is open, close it and select Command Prompt.
c. Verify the IPv4 addressing by entering the command ipconfig /all. You should see the IP address for the DNS server.
d. Ping the DNS server at 64.100.8.8 to verify connectivity.
Note: The first two or three pings may fail as Packet Tracer simulates all the various processes that must occur for successful connectivity to a remote resource.
e. Test the functionality of the DNS server by entering the commands nslookup centralserver.pt.pka and nslookup branchserver.pt.pka. You should get a name resolution showing the IP address for each.
f. Close the Command Prompt window and click Web Browser. Verify that Home Laptop or Tablet can now access the web pages for CentralServer and BranchServer.
Soni Setiawan
20:06:00
New Google SEO
Bandung, IndonesiaPacket Tracer - DHCP and DNS Servers
Objectives
Part 1: Configure Static IPv4 Addressing
Part 2: Configure and Verify DNS Records
Background
In this activity, you will configure and verify static IP addressing and DHCP addressing. You will then configure a DNS server to map IP addresses to the website names.
Note: Packet Tracer only simulates the process for configuring these services. DHCP and DNS software packages each have their own unique installation and configuration instructions.
Part 1: Configure Static IPv4 Addressing
Step 1: Configure the Inkjet printer with static IPv4 addressing.
The home office computers need to know the printer’s IPv4 address to send information to it. The printer, therefore, must use a static (unchanging) IPv4 address.
a. Click Inkjet and click the Config tab, which displays the Global Settings.
b. Statically assign the Gateway address as 192.168.0.1 and the DNS Server address as 64.100.8.8.
c. Click FastEthernet0 and statically assign the IP address as 192.168.0.2 and the Subnet Mask address as 255.255.255.0.
d. Close the Inkjet window.
Step 2: Configure WRS to provide DHCP services.
a. Click WRS and click the GUI tab, and maximize the window.
b. The Basic Setup window displays, by default. Configure the following settings in the Network Setup section:
1) Change the IP Address to 192.168.0.1.
2) Set the Subnet Mask to 255.255.255.0.
3) Enable the DHCP Server.
4) Set the Static DNS 1 address to 64.100.8.8.
5) Scroll to the bottom and click Save.
c. Close the WRS window.
Step 3: Request DHCP addressing for the home laptop.
This activity focuses on the home office. The clients that you will configure with DHCP are Home Laptop and Tablet.
a. Click Home Laptop and click the Desktop tab > IP Configuration.
b. Click DHCP and wait until the DHCP request is successful.
c. Home Laptop should now have a full IP configuration. If not, return to Step 2 and verify your configurations on WRS.
d. Close the IP Configuration window and then close the Home Laptop window.
Step 4: Request DHCP addressing for the tablet.
a. Click Tablet and click the Desktop tab > IP Configuration.
b. Click DHCP and wait until the DHCP request is successful.
c. Tablet should now have a full IP configuration. If not, return to Step 2 and verify your configurations on WRS.
Step 5: Test access to websites.
a. Close the IP Configuration window, and then click Web Browser.
b. In the URL box, type 10.10.10.2 (for the CentralServer website) or 64.100.200.1 (for the BranchServer website) and click Go. Both websites should appear.
c. Reopen the web browser. Test the names for those same websites by entering centralserver.pt.pka and branchserver.pt.pka. Click on Fast Forward Time on the yellow bar below the topology to speed the process.
Part 2: Configure Records on the DNS Server
Step 1: Configure famous.dns.pka with records for CentralServer and BranchServer.
Typically, DNS records are registered with companies, but for the purposes of this activity you control the famous.dns.pka server on the Internet.
a. Click the Internet cloud. A new network displays.
b. Click famous.dns.pka and click the Config tab > DNS.
c. Add the following resource records:
d. Close the famous.dns.pka window.
e. Click Back to exit the Internet cloud.
Step 2: Verify the ability of client computers to use DNS.
Now that you have configured DNS records, Home Laptop and Tablet should be able to access the websites by using the names instead of the IP addresses. First, check that the DNS client is working properly and then verify access to the website.
a. Click Home Laptop or Tablet.
b. If the web browser is open, close it and select Command Prompt.
c. Verify the IPv4 addressing by entering the command ipconfig /all. You should see the IP address for the DNS server.
d. Ping the DNS server at 64.100.8.8 to verify connectivity.
Note: The first two or three pings may fail as Packet Tracer simulates all the various processes that must occur for successful connectivity to a remote resource.
e. Test the functionality of the DNS server by entering the commands nslookup centralserver.pt.pka and nslookup branchserver.pt.pka. You should get a name resolution showing the IP address for each.
f. Close the Command Prompt window and click Web Browser. Verify that Home Laptop or Tablet can now access the web pages for CentralServer and BranchServer.
10.2.1.8 Packet Tracer - Web and Mail
Objectives
Part 1: Configure and Verify Web Services
Part 2: Configure and Verify Email Services
Background
In this activity, you will configure HTTP and email services using the simulated server in Packet Tracer. You will then configure clients to access the HTTP and email services.
Note: Packet Tracer only simulates the process for configuring these services.
HTTP and email software packages each have their own unique installation and configuration instructions.
Part 1: Configure and Verify Web Services
Step 1: Configure web services on CentralServer and BranchServer.
a. Click CentralServer and click the Config tab > HTTP.
b. Click On to enable HTTP and HTTP Secure (HTTPS).
c. Optional. Personalize the HTML code.
d. Repeat Step1a – 1c on BranchServer.
Step 2: Verify the web servers by accessing the web pages.
There are many endpoint devices in this network, but for the purposes of this step, use PC3.
a. Click PC3 and click the Desktop tab > Web Browser.
b. In the URL box, enter 10.10.10.2 as the IP address and click Go. The CentralServer website displays.
c. In the URL box, enter 64.100.200.1 as the IP address and click Go. The BranchServer website displays.
d. In the URL box, enter centralserver.pt.pka and click Go. The CentralServer website displays.
e. In the URL box, enter branchserver.pt.pka and click Go. The BranchServer website displays.
f. What protocol is translating the centralserver.pt.pka and branchserver.pt.pka names to IP addresses?
Part 2: Configure and Verify Email Services on Servers
Step 1: Configure CentralServer to send (SMTP) and receive (POP3) Email.
a. Click CentralServer, and then select the Config tab followed by the EMAIL button.
b. Click On to enable the SMTP and POP3.
c. Set the domain name to centralserver.pt.pka and click Set.
d. Create a user named central-user with password cisco. Click + to add the user.
Step 2: Configure BranchServer to send (SMTP) and receive (POP3) Email.
a. Click BranchServer and click the Config tab > EMAIL.
b. Click On to enable SMTP and POP3 .
c. Set the domain name to branchserver.pt.pka and click Set.
d. Create a user named branch-user with password cisco. Click + to add the user.
Step 3: Configure PC3 to use the CentralServer email service.
a. Click PC3 and click the Desktop tab > E Mail.
b. Enter the following values into their respective fields:
1) Your Name: Central User
2) Email Address: central-user@centralserver.pt.pka
3) Incoming Mail Server: 10.10.10.2
4) Outgoing Mail Server: 10.10.10.2
5) User Name: central-user
6) Password: cisco
c. Click Save. The Mail Browser window displays.
d. Click Receive. If everything has been set up correctly on both the client and server, the Mail Browser window displays the Receive Mail Success message confirmation.
Step 4: Configure Sales to use the Email service of BranchServer.
a. Click Sales and click the Desktop tab > E Mail.
b. Enter the following values into their respective fields:
1) Your Name: Branch User
2) Email Address: branch-user@branchserver.pt.pka
3) Incoming Mail Server: 172.16.0.3
4) Outgoing Mail Server: 172.16.0.3
5) User Name: branch-user
6) Password: cisco
c. Click Save. The Mail Browser window displays.
d. Click Receive. If everything has been set up correctly on both the client and server, the Mail Browser window displays the Receive Mail Success message confirmation.
e. The activity should be 100% complete. Do not close the Sales configuration window or the Mail Browser window.
Step 5: Send an Email from the Sales client and the PC3 client.
a. From the Sales Mail Browser window, click Compose.
b. Enter the following values into their respective fields:
1) To: central-user@centralserver.pt.pka
2) Subject: Personalize the subject line.
3) Email Body: Personalize the email.
c. Click Send.
d. Verify that PC3 received the email. Click PC3. If the Mail Browser window is closed, click E Mail.
e. Click Receive. An email from Sales displays. Double-click the email.
f. Click Reply, personalize a response, and click Send.
g. Verify that Sales received the reply.
Soni Setiawan
00:51:00
New Google SEO
Bandung, IndonesiaObjectives
Part 1: Configure and Verify Web Services
Part 2: Configure and Verify Email Services
Background
In this activity, you will configure HTTP and email services using the simulated server in Packet Tracer. You will then configure clients to access the HTTP and email services.
Note: Packet Tracer only simulates the process for configuring these services.
HTTP and email software packages each have their own unique installation and configuration instructions.
Part 1: Configure and Verify Web Services
Step 1: Configure web services on CentralServer and BranchServer.
a. Click CentralServer and click the Config tab > HTTP.
b. Click On to enable HTTP and HTTP Secure (HTTPS).
c. Optional. Personalize the HTML code.
d. Repeat Step1a – 1c on BranchServer.
Step 2: Verify the web servers by accessing the web pages.
There are many endpoint devices in this network, but for the purposes of this step, use PC3.
a. Click PC3 and click the Desktop tab > Web Browser.
b. In the URL box, enter 10.10.10.2 as the IP address and click Go. The CentralServer website displays.
c. In the URL box, enter 64.100.200.1 as the IP address and click Go. The BranchServer website displays.
d. In the URL box, enter centralserver.pt.pka and click Go. The CentralServer website displays.
e. In the URL box, enter branchserver.pt.pka and click Go. The BranchServer website displays.
f. What protocol is translating the centralserver.pt.pka and branchserver.pt.pka names to IP addresses?
Part 2: Configure and Verify Email Services on Servers
Step 1: Configure CentralServer to send (SMTP) and receive (POP3) Email.
a. Click CentralServer, and then select the Config tab followed by the EMAIL button.
b. Click On to enable the SMTP and POP3.
c. Set the domain name to centralserver.pt.pka and click Set.
d. Create a user named central-user with password cisco. Click + to add the user.
Step 2: Configure BranchServer to send (SMTP) and receive (POP3) Email.
a. Click BranchServer and click the Config tab > EMAIL.
b. Click On to enable SMTP and POP3 .
c. Set the domain name to branchserver.pt.pka and click Set.
d. Create a user named branch-user with password cisco. Click + to add the user.
Step 3: Configure PC3 to use the CentralServer email service.
a. Click PC3 and click the Desktop tab > E Mail.
b. Enter the following values into their respective fields:
1) Your Name: Central User
2) Email Address: central-user@centralserver.pt.pka
3) Incoming Mail Server: 10.10.10.2
4) Outgoing Mail Server: 10.10.10.2
5) User Name: central-user
6) Password: cisco
c. Click Save. The Mail Browser window displays.
d. Click Receive. If everything has been set up correctly on both the client and server, the Mail Browser window displays the Receive Mail Success message confirmation.
Step 4: Configure Sales to use the Email service of BranchServer.
a. Click Sales and click the Desktop tab > E Mail.
b. Enter the following values into their respective fields:
1) Your Name: Branch User
2) Email Address: branch-user@branchserver.pt.pka
3) Incoming Mail Server: 172.16.0.3
4) Outgoing Mail Server: 172.16.0.3
5) User Name: branch-user
6) Password: cisco
c. Click Save. The Mail Browser window displays.
d. Click Receive. If everything has been set up correctly on both the client and server, the Mail Browser window displays the Receive Mail Success message confirmation.
e. The activity should be 100% complete. Do not close the Sales configuration window or the Mail Browser window.
Step 5: Send an Email from the Sales client and the PC3 client.
a. From the Sales Mail Browser window, click Compose.
b. Enter the following values into their respective fields:
1) To: central-user@centralserver.pt.pka
2) Subject: Personalize the subject line.
3) Email Body: Personalize the email.
c. Click Send.
d. Verify that PC3 received the email. Click PC3. If the Mail Browser window is closed, click E Mail.
e. Click Receive. An email from Sales displays. Double-click the email.
f. Click Reply, personalize a response, and click Send.
g. Verify that Sales received the reply.
Modul 7 : Snort - Sama halnya dengan Portsentry, Snort juga perangkat lunak yang digunakan sebagai IDS. Namun, saat ini telah mengalami perkembangan sehingga dapat dijadikan sebagai IPS.
Modul 6 : Portsentry - PortSentry adalah sebuah perangkat lunak yang di rancang untuk mendeteksi
adanya port scanning & meresponds secara aktif jika ada port scanning. Port scan adalah
proses scanning berbagai aplikasi servis yang dijalankan di server Internet. Port scan
adalah langkah paling awal sebelum sebuah serangan di lakukan.
Cara kerja port sentry dengan melakukan melihat komputer yang melakukan scan dan
secara aktif akan memblokir mesin penyerang agar tidak dapat masuk & melakukan
transaksi dengan Server kita.
Semoga bermanfaat.
9.1.4.6 Packet Tracer - Subnetting Scenario 1
Soni Setiawan
22:15:00
New Google SEO
Bandung, Indonesia |
| Topologi |
Objectives
Part 1: Design an IP Addressing Scheme
Part 2: Assign IP Addresses to Network Devices and Verify Connectivity
Scenario
In this activity, you are given the network address of 192.168.100.0/24 to subnet and provide the IP addressing for the network shown in the topology. Each LAN in the network requires enough space for, at least, 25 addresses for end devices, the switch and the router. The connection between R1 to R2 will require an IP address for each end of the link.
Part 1: Design an IP Addressing Scheme
Step 1: Subnet the 192.168.100.0/24 network into the appropriate number of subnets.
a. Based on the topology, how many subnets are needed?
b. How many bits must be borrowed to support the number of subnets in the topology table?
c. How many subnets does this create?
d. How many usable hosts does this create per subnet?
Note: If your answer is less than the 25 hosts required, then you borrowed too many bits.
e. Calculate the binary value for the first five subnets. The first subnet is already shown.
Selanjutnya, PAHAMI bagian ini
Step 2: Assign the subnets to the network shown in the topology.
a. Assign Subnet 0 to the LAN connected to the GigabitEthernet 0/0 interface of R1:
b. Assign Subnet 1 to the LAN connected to the GigabitEthernet 0/1 interface of R1:
c. Assign Subnet 2 to the LAN connected to the GigabitEthernet 0/0 interface of R2:
d. Assign Subnet 3 to the LAN connected to the GigabitEthernet 0/1 interface of R2:
e. Assign Subnet 4 to the WAN link between R1 to R2:
Step 3: Document the addressing scheme.
Fill in the Addressing Table using the following guidelines:
a. Assign the first usable IP addresses to R1 for the two LAN links and the WAN link.
b. Assign the first usable IP addresses to R2 for the LANs links. Assign the last usable IP address for the WAN link.
c. Assign the second usable IP addresses to the switches.
d. Assign the last usable IP addresses to the hosts.
Part 2: Assign IP Addresses to Network Devices and Verify Connectivity
Most of the IP addressing is already configured on this network. Implement the following steps to complete the addressing configuration.
Step 1: Configure IP addressing on R1 LAN interfaces.
R1>enable
R1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#interface gigabitEthernet 0/0
R1(config-if)#ip address 192.168.100.1 255.255.255.224
R1(config-if)#no shutdown
R1(config-if)#
R1(config-if)#int g0/1
R1(config-if)#ip address 192.168.100.33 255.255.255.224
R1(config-if)#no shutdown
R1(config-if)#
Step 2: Configure IP addressing on S3, including the default gateway.
S3>enable
S3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
S3(config)#interface vlan 1
S3(config-if)#ip add 192.168.100.66 255.255.255.224
S3(config-if)#no shutdown
S3(config-if)#exit
S3(config)#ip default-gateway 192.168.100.65
S3(config)#
Step 3: Configure IP addressing on PC4, including the default gateway.
Step 4: Verify connectivity.
Part 1: Design an IP Addressing Scheme
Part 2: Assign IP Addresses to Network Devices and Verify Connectivity
Scenario
In this activity, you are given the network address of 192.168.100.0/24 to subnet and provide the IP addressing for the network shown in the topology. Each LAN in the network requires enough space for, at least, 25 addresses for end devices, the switch and the router. The connection between R1 to R2 will require an IP address for each end of the link.
Part 1: Design an IP Addressing Scheme
Step 1: Subnet the 192.168.100.0/24 network into the appropriate number of subnets.
a. Based on the topology, how many subnets are needed?
b. How many bits must be borrowed to support the number of subnets in the topology table?
c. How many subnets does this create?
d. How many usable hosts does this create per subnet?
Note: If your answer is less than the 25 hosts required, then you borrowed too many bits.
e. Calculate the binary value for the first five subnets. The first subnet is already shown.
Sebenarnya agak bingung juga mau jelasin dari mana, namun yang saya pahami ketika mengerjakan latihan ini adalah bagaimana alokasi IP Address dimana disediakan 1 (satu) IP Address yang kemudian dibagi-bagi/di subnet sehingga mencakup seluruh kebutuhan IP Address berdasarkan topologi yang telah ditentukan.
Subnetting
Hal pertama yang terpikirkan olehku adalah subnet. Ya, karena pembagian/alokasi IP Address jika disediakan 1 (satu) IP Address maka berkaitan dengan subnet/subnetting. Maka yang dilakukan adalah mengotak-atik subnet mask dari IP Address yang telah disediakan tadi.
- Dibutuhkan IP Address untuk 25 hosts
- Tentukan subnet yang memenuhi persyaratan di atas
<!-- Cara yang aku lakukan -->
11111111.11111111.11111111.11100000
Untuk mengetahui jumlah host per subnet gunakan rumus :
2^n-2
dimana : n adalah jumlah angka 0 di oktet terakhir
maka
2^5-2 = 30 (memenuhi syarat butuh 25 hosts)
Berdasarkan kebutuhan tersebut, subnet yang memenuhi adalah /27
Terus ???
Yang saya lakukan adalah menentukan range IP Address yang digunakan dalam 1 subnet.
Biar lebih mudah, aku pake LibreOffice Calc (kayak Excel) untuk menentukan range IP Address.
 |
| Alokasi IP Address |
Step 2: Assign the subnets to the network shown in the topology.
a. Assign Subnet 0 to the LAN connected to the GigabitEthernet 0/0 interface of R1:
b. Assign Subnet 1 to the LAN connected to the GigabitEthernet 0/1 interface of R1:
c. Assign Subnet 2 to the LAN connected to the GigabitEthernet 0/0 interface of R2:
d. Assign Subnet 3 to the LAN connected to the GigabitEthernet 0/1 interface of R2:
e. Assign Subnet 4 to the WAN link between R1 to R2:
Step 3: Document the addressing scheme.
Fill in the Addressing Table using the following guidelines:
a. Assign the first usable IP addresses to R1 for the two LAN links and the WAN link.
b. Assign the first usable IP addresses to R2 for the LANs links. Assign the last usable IP address for the WAN link.
c. Assign the second usable IP addresses to the switches.
d. Assign the last usable IP addresses to the hosts.
Part 2: Assign IP Addresses to Network Devices and Verify Connectivity
Most of the IP addressing is already configured on this network. Implement the following steps to complete the addressing configuration.
Step 1: Configure IP addressing on R1 LAN interfaces.
R1>enable
R1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#interface gigabitEthernet 0/0
R1(config-if)#ip address 192.168.100.1 255.255.255.224
R1(config-if)#no shutdown
R1(config-if)#
R1(config-if)#int g0/1
R1(config-if)#ip address 192.168.100.33 255.255.255.224
R1(config-if)#no shutdown
R1(config-if)#
Step 2: Configure IP addressing on S3, including the default gateway.
S3>enable
S3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
S3(config)#interface vlan 1
S3(config-if)#ip add 192.168.100.66 255.255.255.224
S3(config-if)#no shutdown
S3(config-if)#exit
S3(config)#ip default-gateway 192.168.100.65
S3(config)#
Step 3: Configure IP addressing on PC4, including the default gateway.
 |
| PC4 IP Address |
Step 4: Verify connectivity.
 |
| Tes Koneksi PC4 ke PC1 |
9.1.4.6 Packet Tracer - Subnetting Scenario 1
Posted by Soni Setiawan on Wednesday, 10 February 2016
Adapun Ubuntu 14.04 juga memiliki beberapa jenis, diantaranya Dekstop dan Server. Keduanya memiliki kegunaan masing-masing. Berikut website yang menyediakan download iso Ubuntu 14.04 LTS.
Sebelum mendownload, pastikan memiliki akses internet yang memadai karena file yang akan di download berukuran lumayan besar.
Running Packet Tracer 6.3 on Ubuntu 14.04 - Setelah beberapa hari terakhir mengalami kesulitan untuk menjalankan packet tracer ver 6.3 di Ubuntu yang saya gunakan, akhirnya setelah saya reinstall dengan langkah instalasi yang berbeda sukses di lakukan.
Beberapa bulan terakhir sedang menyusun tugas akhir alias skripsi menjadikan jarang menggunakan packet tracer untuk belajar materi jaringan. Terlebih lagi saya mengganti laptop, iya bener saya ganti laptop karena laptop yang sudah diinstal packet tracer sebelumnya sudah rusak. Jadi mau tidak mau harus ganti laptop.
Ini tampilan packet tracer yang berhasil dijalankan pada Ubuntu 14.04 yang saya pake.
 |
| Packet Tracer v6.3 on Ubuntu 14.04 |
Sudah terinstal, saatnya kembali belajar. Jangan pernah berhenti belajar, guys! Belajar tentang segala hal. Hehee ;)
[SOLVED] Could not open configuration file /etc/apache2/conf-enabled/owncloud.conf: No such file or directory - Selamat pagi, semoga segala aktivitas yang dilakukan dapat lancar dan diberi kemudahan. Pada kesempatan yang baik ini, saya sedikit berbagi informasi mengenai troubleshooting yang dilakukan ketika menemui sebuah error. Di mana error kali ini berkaitan dengan salah satu service dalam web server, yaitu apache2.
Pesan error muncul ketika saya mencoba menjalankan perintah sudo /etc/init.d/apache2 start.
Berikut pesan error ketika saya menjalankan perintah tersebut.
apache2: Syntax error on line 216 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/conf-enabled/owncloud.conf: No such file or directory
Action 'configtest' failed.
Setelah proses pencarian menggunakan google, ternyata masalah yang menyebabkan hal ini terjadi adalah sebelumnya saya telah menginstall Owncloud namun saat proses uninstall owncloud belum secara menyeluruh. Dalam arti, directory owncloud masih ada yang tersisa sehingga harus dihapus terlebih dahulu.
Untuk uninstall Owncloud lakukan perintah di bawah ini:
sudo apt-get purge owncloud
sudo rm -rf /var/www/owncloud
sudo /etc/apache2/conf-enabled/owncloud.conf
Setelah directory owncloud sudah dihapus, saya coba jalankan kembali service apache2 dan berhasil.
[SOLVED] etc/apache2/conf-enabled/owncloud.conf
Posted by Soni Setiawan on Saturday, 12 December 2015
6.5.1.2 Packet Tracer Skills Integration Challenge
Objectives
Finish the network documentation.
Perform basic device configurations on a router and a switch.
Verify connectivity and troubleshoot any issues.
Scenario
Your network manager is impressed with your performance in your job as a LAN technician. She would like you to now demonstrate your ability to configure a router connecting two LANs. Your tasks include configuring basic settings on a router and a switch using the Cisco IOS. You will then verify your configurations, as well as configurations on existing devices by testing end-to-end connectivity.
Note: After completing this activity, you can choose to click the Reset Activity button to generate a new set of requirements. Variable aspects include device names, IP addressing schemes, and the topology.
Requirements
· Provide the missing information in the Addressing Table.
#You will find a miss configuration on Reception-B
#Change to correct ip address configuration : 10.10.11.102
Name the router Floor14 and the second switch Room-146. You will not be able to access Room-145.
#router Floor14
Router>enable
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname Floor14
Floor14(config)#exit
Floor14#
#switch Room-146
Switch#enable
Switch#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#hostname Room-146
Room-146(config)#exit
Room-146#
Use cisco as the user EXEC password for all lines.
Use class as the privileged EXEC password.
Encrypt all plain text passwords.
Configure an appropriate banner.
Configure addressing for all devices according to the Addressing Table.
Document interfaces with descriptions, including the Room-146 VLAN 1 interface.
Save your configurations.
Verify connectivity between all devices. All devices should be able to ping any other device.
#router Floor14
Floor14>enable
Floor14#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Floor14(config)#line console 0
Floor14(config-line)#password cisco
Floor14(config-line)#login
Floor14(config-line)#exit
Floor14(config)#line vty 0
Floor14(config-line)#password cisco
Floor14(config-line)#login
Floor14(config-line)#exit
Floor14(config)#enable secret class
Floor14(config)#service pass
Floor14(config)#service password-encryption
Floor14(config)#banner motd &
Enter TEXT message. End with the character '&'.
Authorized Access Only! &
Floor14(config)#
Floor14(config)#interface gigabitEthernet 0/0
Floor14(config-if)#ip add 10.10.10.1 255.255.255.0
Floor14(config-if)#no shutdown
Floor14(config-if)#exit
Floor14(config)#interface gigabitEthernet 0/1
Floor14(config-if)#ip add 10.10.11.1 255.255.255.0
Floor14(config-if)#no shutdown
Floor14(config-if)#exit
Floor14(config)#do write
#switch Room-146
Room-146#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Room-146(config)#line console 0
Room-146(config-line)#password cisco
Room-146(config-line)#login
Room-146(config-line)#exit
Room-146(config)#line vty 0
Room-146(config-line)#password cisco
Room-146(config-line)#login
Room-146(config-line)#exit
Room-146(config)#enable secret class
Room-146(config)#service password-encryption
Room-146(config)#banner motd &
Enter TEXT message. End with the character '&'.
Authorized Access Only! &
Room-146(config)#
Room-146(config)#ip default-gateway 10.10.11.1
Room-146(config)#interface vlan 1
Room-146(config-if)#ip address 10.10.11.100 255.255.255.0
Room-146(config-if)#no shutdown
Room-146(config)#do write
# Setup Default Gateway for Device Manager-A and Reception-A use ip address on interface GigabitEthernet 0/0
# Setup Default Gateway for Device Manager-B and Reception-B use ip address on interface GigabitEthernet 0/1
Troubleshoot and document any issues.
Implement the solutions necessary to enable and verify full end-to-end connectivity.
Note: Click Check Results button to see your progress. Click the Reset Activity button to generate a new set of requirements.
Soni Setiawan
23:59:00
New Google SEO
Bandung, IndonesiaObjectives
Finish the network documentation.
Perform basic device configurations on a router and a switch.
Verify connectivity and troubleshoot any issues.
Scenario
Your network manager is impressed with your performance in your job as a LAN technician. She would like you to now demonstrate your ability to configure a router connecting two LANs. Your tasks include configuring basic settings on a router and a switch using the Cisco IOS. You will then verify your configurations, as well as configurations on existing devices by testing end-to-end connectivity.
Note: After completing this activity, you can choose to click the Reset Activity button to generate a new set of requirements. Variable aspects include device names, IP addressing schemes, and the topology.
Requirements
· Provide the missing information in the Addressing Table.
#You will find a miss configuration on Reception-B
#Change to correct ip address configuration : 10.10.11.102
 |
| Reception-B |
Name the router Floor14 and the second switch Room-146. You will not be able to access Room-145.
#router Floor14
Router>enable
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname Floor14
Floor14(config)#exit
Floor14#
#switch Room-146
Switch#enable
Switch#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#hostname Room-146
Room-146(config)#exit
Room-146#
Use cisco as the user EXEC password for all lines.
Use class as the privileged EXEC password.
Encrypt all plain text passwords.
Configure an appropriate banner.
Configure addressing for all devices according to the Addressing Table.
Document interfaces with descriptions, including the Room-146 VLAN 1 interface.
Save your configurations.
Verify connectivity between all devices. All devices should be able to ping any other device.
#router Floor14
Floor14>enable
Floor14#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Floor14(config)#line console 0
Floor14(config-line)#password cisco
Floor14(config-line)#login
Floor14(config-line)#exit
Floor14(config)#line vty 0
Floor14(config-line)#password cisco
Floor14(config-line)#login
Floor14(config-line)#exit
Floor14(config)#enable secret class
Floor14(config)#service pass
Floor14(config)#service password-encryption
Floor14(config)#banner motd &
Enter TEXT message. End with the character '&'.
Authorized Access Only! &
Floor14(config)#
Floor14(config)#interface gigabitEthernet 0/0
Floor14(config-if)#ip add 10.10.10.1 255.255.255.0
Floor14(config-if)#no shutdown
Floor14(config-if)#exit
Floor14(config)#interface gigabitEthernet 0/1
Floor14(config-if)#ip add 10.10.11.1 255.255.255.0
Floor14(config-if)#no shutdown
Floor14(config-if)#exit
Floor14(config)#do write
#switch Room-146
Room-146#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Room-146(config)#line console 0
Room-146(config-line)#password cisco
Room-146(config-line)#login
Room-146(config-line)#exit
Room-146(config)#line vty 0
Room-146(config-line)#password cisco
Room-146(config-line)#login
Room-146(config-line)#exit
Room-146(config)#enable secret class
Room-146(config)#service password-encryption
Room-146(config)#banner motd &
Enter TEXT message. End with the character '&'.
Authorized Access Only! &
Room-146(config)#
Room-146(config)#ip default-gateway 10.10.11.1
Room-146(config)#interface vlan 1
Room-146(config-if)#ip address 10.10.11.100 255.255.255.0
Room-146(config-if)#no shutdown
Room-146(config)#do write
# Setup Default Gateway for Device Manager-A and Reception-A use ip address on interface GigabitEthernet 0/0
# Setup Default Gateway for Device Manager-B and Reception-B use ip address on interface GigabitEthernet 0/1
Troubleshoot and document any issues.
Implement the solutions necessary to enable and verify full end-to-end connectivity.
Note: Click Check Results button to see your progress. Click the Reset Activity button to generate a new set of requirements.
6.5.1.2 Packet Tracer Skills Integration Challenge
Posted by Soni Setiawan on Monday, 23 November 2015
Cara Ekstrak File .Rar di Linux - Kebutuhan akan kompresi data menjadikan pengguna komputer merasa terbantu, terlebih dengan banyaknya file-file yang ada di komputer menjadikan arsip menjadi sesuatu yang penting. Adanya pengarsipan yang baik tentu akan mempermudah pengguna komputer dalam pengelolaan dokumen sehingga lebih mudah ketika dicarai maupun agar tertata rapi.
Berbagai jenis format penyimpanan berupa arsip dapat dijumpai ketika menggunakan komputer. Sebagai contoh, file dengan ekstensi .rar, .zip, .tar.gz dan lain-lainya. Adapun cara untuk mengekstrak file dengan ekstensi terkait juga berbeda-beda. Namun, pada kesempatan kali ini, saya akan berbagi cara ekstrak file .rar di linux terutama ubuntu menggunakan aplikasi tambahan.
Perlu diketahui bahwa untuk proses ekstrak file berekstensi .rar sedikit berbeda jika dibandingkan ketika menggunakan OS Windows. Pada windows, program yang biasa digunakan untuk ekstrak file terutama berekstensi .rar adalah WinRar. Maka ketika menggunakan os Linux, WinRar tidak akan bisa berjalan kecuali dengan bantuan aplikasi yang disebut dengan Wine. Wine merupakan sebuah aplikasi yang digunakan sebagai 'translator' program aplikasi Windows sehingga dapat berjalan di Linux. Namun, ada cara lain yang lebih mudah ketimbang harus instal Wine lalu baru instal WinRar.
Di Linux sudah tersedia program untuk menangani permasalahan ektraksi file dengan ekstensi .rar. Salah satu yang dapat digunakan adalah unrar. Untuk mengintall unrar lakukan perintah dibawah ini.
 |
| Gambar 1. Cara Instal unrar |
Adapun cara untuk menggunakan unrar adalah sebagai berikut.
Untuk mengekstrak file.rar file ke direktori dimana file tersebut diletakkan, masukkan:
$ unrar e file.rar
Nah, itu dia cara untuk ekstrak file.rar. Selamat mencoba dan semoga berhasil.
Referensi:
http://www.cyberciti.biz/faq/open-rar-file-or-extract-rar-files-under-linux-or-unix/ (diakses pada 19 November 2015 pukul 22.09 WIB)
Pengelolaan service ini bisa melakukan blocking service tertentu kepada client atau nomor IP tertentu.
