iklanku

kasihku

rinduku

Monday, January 16, 2017

login web page di mikrotik

VIDIO membuat web page login di mikrotik

VIDIO SETTING MIKROTIK RB750 HOTSPOT

VIDIO SETTING MIKROTIK UNTUK RB750 HOTSPOT

 VIDIO SETTING MIKROTIK USER VOUCHER

VIDIO SETTING MIKROTIK DENGAN VIRTUAL BOX VS WINBOX

VIDIO SETTING MIKROTIK DENGAN VIRTUAL BOX 1
VIDIO MIKROTIK 2 DENGN WINBOX

VIDIO INSTAL DEBIAN DENGAN VIRTUAL BOX


CARA INSTAL DEBIAN MENGGUNAKAN VIRTUAL BOX

INSTALASI DEBIAN 8

CARA INSTAL DEBIAN 8

Introduction

When you first create a new Debian 8 server, there are a few configuration steps that you should take early on as part of the basic setup. This will increase the security and usability of your server and will give you a solid foundation for subsequent actions.

Step One — Root Login

To log into your server, you will need to know your server's public IP address and the password for the "root" user's account. If you have not already logged into your server, you may want to follow the first tutorial in this series, How to Connect to Your Droplet with SSH, which covers this process in detail.
If you are not already connected to your server, go ahead and log in as the root user using the following command (substitute the highlighted word with your server's public IP address):
  • ssh root@SERVER_IP_ADDRESS
Complete the login process by accepting the warning about host authenticity, if it appears, then providing your root authentication (password or private key). If it is your first time logging into the server, with a password, you will also be prompted to change the root password.

About Root

The root user is the administrative user in a Linux environment that has very broad privileges. Because of the heightened privileges of the root account, you are actually discouraged from using it on a regular basis. This is because part of the power inherent with the root account is the ability to make very destructive changes, even by accident.
The next step is to set up an alternative user account with a reduced scope of influence for day-to-day work. We'll teach you how to gain increased privileges during the times when you need them.

Step Two — Create a New User

Once you are logged in as root, we're prepared to add the new user account that we will use to log in from now on.
This example creates a new user called "demo", but you should replace it with a user name that you like:
  • adduser demo
You will be asked a few questions, starting with the account password.
Enter a strong password and, optionally, fill in any of the additional information if you would like. This is not required and you can just hit "ENTER" in any field you wish to skip.

Step Three — Root Privileges

Now, we have a new user account with regular account privileges. However, we may sometimes need to do administrative tasks.
To avoid having to log out of our normal user and log back in as the root account, we can set up what is known as "super user" or root privileges for our normal account. This will allow our normal user to run commands with administrative privileges by putting the word sudo before each command.

Install Sudo

Debian 8 doesn't come with sudo installed, so let's install it with apt-get.
First, update the apt package index:
  • apt-get update
Then use this command to install sudo:
  • apt-get install sudo
Now you are able to use the sudo and visudo commands.

Grant Sudo Privileges

To add these privileges to our new user, we need to add the new user to the "sudo" group. By default, on Debian 8, users who belong to the "sudo" group are allowed to use the sudo command.
As root, run this command to add your new user to the sudo group (substitute the highlighted word with your new user):
  • usermod -a -G sudo demo
Now your user can run commands with super user privileges! For more information about how this works, check out this sudoers tutorial.
The next step in securing your server is to set up public key authentication for your new user. Setting this up will increase the security of your server by requiring a private SSH key to log in.

Generate a Key Pair

If you do not already have an SSH key pair, which consists of a public and private key, you need to generate one. If you already have a key that you want to use, skip to the Copy the Public Key step.
To generate a new key pair, enter the following command at the terminal of your local machine (ie. your computer):
  • ssh-keygen
Assuming your local user is called "localuser", you will see output that looks like the following:
ssh-keygen output
Generating public/private rsa key pair. Enter file in which to save the key (/Users/localuser/.ssh/id_rsa):
Hit return to accept this file name and path (or enter a new name).
Next, you will be prompted for a passphrase to secure the key with. You may either enter a passphrase or leave the passphrase blank.
Note: If you leave the passphrase blank, you will be able to use the private key for authentication without entering a passphrase. If you enter a passphrase, you will need both the private key and the passphrase to log in. Securing your keys with passphrases is more secure, but both methods have their uses and are more secure than basic password authentication.
This generates a private key, id_rsa, and a public key, id_rsa.pub, in the .ssh directory of thelocaluser's home directory. Remember that the private key should not be shared with anyone who should not have access to your servers!

Copy the Public Key

After generating an SSH key pair, you will want to copy your public key to your new server. We will cover two easy ways to do this.

Option 1: Use ssh-copy-id

If your local machine has the ssh-copy-id script installed, you can use it to install your public key to any user that you have login credentials for.
Run the ssh-copy-id script by specifying the user and IP address of the server that you want to install the key on, like this:
  • ssh-copy-id demo@SERVER_IP_ADDRESS
After providing your password at the prompt, your public key will be added to the remote user's.ssh/authorized_keys file. The corresponding private key can now be used to log into the server.

Option 2: Manually Install the Key

Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):
  • cat ~/.ssh/id_rsa.pub
This should print your public SSH key, which should look something like the following:
id_rsa.pub contents
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local
Select the public key, and copy it to your clipboard.

Add Public Key to New Remote User

To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory.
On the server, as the root user, enter the following command to switch to the new user (substitute your own user name):
  • su - demo
Now you will be in your new user's home directory.
Create a new directory called .ssh and restrict its permissions with the following commands:
  • mkdir .ssh
  • chmod 700 .ssh
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:
  • nano .ssh/authorized_keys
Now insert your public key (which should be in your clipboard) by pasting it into the editor.
Hit CTRL-X to exit the file, then Y to save the changes that you made, then ENTER to confirm the file name.
Now restrict the permissions of the authorized_keys file with this command:
  • chmod 600 .ssh/authorized_keys
Type this command once to return to the root user:
  • exit
Now you may SSH login as your new user, using the private key as authentication.
To read more about how key authentication works, read this tutorial: How To Configure SSH Key-Based Authentication on a Linux Server.

Step Five — Configure SSH

Now that we have our new account, we can secure our server a little bit by modifying its SSH daemon configuration (the program that allows us to log in remotely) to disallow remote SSH access to the rootaccount.
Begin by opening the configuration file with your text editor as root:
  • nano /etc/ssh/sshd_config
Here, we have the option to disable root login through SSH. This is generally a more secure setting since we can now access our server through our normal user account and escalate privileges when necessary.
To disable remote root logins, we need to find the line that looks like this:
/etc/ssh/sshd_config (before)
#PermitRootLogin yes
You can modify this line to "no" like this if you want to disable root login:
/etc/ssh/sshd_config (after)
PermitRootLogin no
Disabling remote root login is highly recommended on every server!
When you are finished making your changes, save and close the file using the method we went over earlier (CTRL-X, then Y, then ENTER).

Reload SSH

Now that we have made our changes, we need to restart the SSH service so that it will use our new configuration.
Type this to restart SSH:
  • systemctl restart ssh
Now, before we log out of the server, we should test our new configuration. We do not want to disconnect until we can confirm that new connections can be established successfully.
Open a new terminal window. In the new window, we need to begin a new connection to our server. This time, instead of using the root account, we want to use the new account that we created.
  • ssh demo@SERVER_IP_ADDRESS
You will be prompted for the new user's password that you configured. After that, you will be logged in as your new user.
Remember, if you need to run a command with root privileges, type "sudo" before it like this:
  • sudo command_to_run
If all is well, you can exit your sessions by typing:
  • exit

Where To Go From Here?

At this point, you have a solid foundation for your Debian 8 server. You can install any of the software you need on your server now.

Thursday, January 12, 2017

LINK BELAJAR MIKROTIK

LUPA USER PASWORD PADA MIKROTIK

Solusi Melihat Username dan Password Mikrotik jika anda Lupa - Manusia memang tidak bisa lepas dari penyakit LUPA. Ya, mungkin anda ada yang mengalami lupa password Mikrotik atau lupa username Mikrotik nya. Lupa username dan password Mikrotik memang umum dan sering terjadi apalagi kalau kita tidak menyimpan data login Mikrotik itu. Namun anda tidak usah khawatir karena jika anda lupa username dan password login Mikrotik, kedua nya bisa di-recovery dengan memanfaatkan file backup Mikrotik dan layanan Mikrotik Backup Password Recovery dari situs mikrotikpasswordrecovery.com.

Oke, berikut cara recovery username dan password Mikrotik dengan Mikrotik Password Recovery Tool :

1. Pastikan anda masih menyimpan file backup dari Router Mikrotik yang anda lupa password nya.
2. Masuk ke situs www.mikrotikwiki.com
3. Klik Choose File dan pilih file backup Mikrotik anda --> Klik Submit.

4. Kemudian Username dan Password Mikrotik anda akan muncul seperti gambar di atas.

Gimana mudah bukan? Yang penting anda harus rajin Backup Konfigurasi Mikrotik anda supaya hal-hal yang tidak diinginkan tidak terjadi dan juga catat username dan password anda supaya ketika lupa tidak repot :D.

Jika cara ini tidak bisa digunakan mungkin karena tidak ada file backup dari Mikrotik anda, cara lainnya adalah dengan mereset Router Mikrotik anda. Saya sudah pernah membahasnya pada artikel ini Tutorial Cara Reset Mikrotik

PEMBATASA BANDWIDTH PADA MIKROTIK

Cara Membatasi (Limit) Bandwidth Mikrotik dengan Simple Queue Mikrotik - Mengatur dan membatasi pemakaian Bandwidth internet memang suatu hal yang penting ketika koneksi internet kita terbatas, misalnya kuota bandwidth yang terbatas dari ISP. Kita perlu membatasi kuota bandwidth tiap user yang terkoneksi ke Router Mikrotik. Pada Router Mikrotik sendiri sudah tersedia fitur yang bisa membatasi (limit) bandwidth yaitu Queue. Ada dua macam Queue pada Mikrotik :
  1. Queue Simple : merupakan cara termudah untuk melakukan management bandwidth yang diterapkan pada jaringan skala kecil sampai menengah untuk mengatur pemakaian bandwidth upload dan download tiap user.
  2. Queue Tree : mirip seperti queue simple tapi lebih rumit, yaitu dapat melakukan pembatasan bandwidth berdasarkan group bahkan secara hierarki. Kita harus mengaktifkan fitur Mangle pada Firewall jika ingin menggunakan Queue Tree.
Pada artikel kali ini kita akan membahas fitur Queue Simple dulu. Oke, mari kita belajar mikrotik bersama :)

Untuk pembahasan Queue Simple kali ini kita akan mencoba praktek membuat limit Bandwidth semua user dengan mikrotik. Silakan buka Winbox nya dan pilih menu Queues, maka akan muncul tampilan berikut :

Sebelum kita mulai membatasi Bandwidth internet dengan mikrotik, pastikan dulu berapa Bandwidth Internet yang anda dapat dari ISP yang anda pakai. Sehingga nantinya nilai Bandwidth yang dilimit tidak melebihi alokasi Bandwidth dari ISP. Misalnya bandwidth dari ISP sebesar 1 Mbps, maka limit bandwidth nya diset lebih kecil atau sama dengan 1 Mbps.

Untuk menambahkan Simple Queue baru klik tombol +, maka akan muncul tempilan seperti berikut :


Ada beberapa tab di jendela Simple Queue tersebut, namun kita hanya akan menggunakan tab General dan Advanced saja. 

Tab General
Pada tab General ada beberapa pilihan yang dapat diseting. Yang perlu kita perhatikan dengan seksama yaitu pilihan Target Address dan Max Limit. 

Target Address

Anda dapat mengisis Target Address dengan IP address tertentu yang ingin anda batasi Bandwidth nya, misal 192.168.100.0/24. Dari gambar di atas bisa dilihat untuk Target Address kosong, ini berarti konfigurasi limit Bandwidth ini berlaku untuk semua alamat IP. 

Max Limit

Max Limit adalah alokasi bandwidth maksimal yang bisa didapatkan user, dan biasanya akan didapatkan user jika ada alokasi bandwidth yang tidak digunakan lagi oleh user lain. Jangan lupa centang Target Upload dan Target Download untuk mengaktifkan fitur ini, pilih besar Bandwidth yang ingin dilimit pada Max Limit. Misalnya upload : 256kbps download : 1Mbps.
Besar limit Bandwidth untuk upload lebih rendah daripada download nya karena memang user biasanya lebih banyak melakukan download (browsing, download musik, file, dll) daripada upload. Anda dapat memilih sesuai keinginan.

Anda juga dapat menentukan waktu kapan dan berapa lama Simple Queue ini akan mulai berjalan dengan memilih opsi Time.

Tab Advanced


Pada tab Advanced hal yang perlu diperhatikan pada opsi Interface dan Limit At. 

Interface
Pilih interface mana yang ingin dibatasi bandwidth nya, misalnya interface Wlan1 untuk membatasi koneksi internet via wireless. Jika ingin membatasi bandwidth di semua Interface pilih all.

Limit At
Limit At adalah alokasi bandwidth trendah yang bisa didapatkan oleh user jika traffic jaringan sangat sibuk. Seburuk apapun keadaan jaringan, user tidak akan mendapat alokasi bandwidth dibawah nilai Limit At ini. Jadi Limit At ini adalah nilai bandwidth terendah yang akan didapatkan oleh user. Nilai nya terserah anda mau diisi berapa. Misalnya diisi upload 128kbps download : 512kbps.

Untuk opsi lainnya akan dibahas pada artikel Tutorial Mikrotik Indo selanjutnya.

Nah, dari konfigurasi tersebut, maka hasilnya jika semua user sedang memakai koneksi internet dan kondisi jaringan sibuk maka tiap user akan mendapatkan bandwidth sebesar 128kbps/512kbps. Jika satu atau beberapa user tidak sedang menggunakan koneksi maka alokasi bandwidth akan diberikan ke user yang sedang terkoneksi. Dan jika hanya satu user yang menggunakan koneksi maka user itu akan mendapatkan alokasi bandwidth maksimal 256kbps/1Mbps.

Klik ok untuk menambahkan Simple Queue tersebut, sehingga akan muncul di queue list.


Pada gambar di atas, ada dua Simple Queue, yaitu Simple Queue yang terbentuk secara otomatis oleh Hotspot di artikel sebelumnya Cara Membuat Hotspot di Mikrotik : Seting dasar Hotspot Mikrotik
dan Simple Queue yang baru dibuat. Jika ada dua konfigurasi berbeda maka akan dieksekusi dari atas ke bawah (top to bottom), jadi Simple Queue hotspot dieksekusi dulu baru kemudian Simple Queue Mikrotik Indo. Walaupun Simple Queue hotspot Tx Rx Max limit nya unlimited, tapi semua user hotspot akan mendapatkan bandwidth Max Tx Rx 256k/1M dari Simple Queue MikrotikIndo, sehingga Simple Queue hotspot itu tidak berlaku.