flash disk bisa jadi ram .

Kamu punya masalah terhadap memory RAM kamu?kalau memory RAM kecil maka otomatis komputer anda pun ikut lambat.Hal itu biasanya membuat orang sebel.mau beli RAM baru tapi tidak punya duit.
kalau masalah kamu kaya gitu saya bisa memberi solusinya.
kamu punya flashdisk kan?zaman sekarang sudah banyak orang yang punya flashdisk.harganyapun juga semakin murah
di sini saya akan memberi trik menyulap FLASH DISK menjadi RAM.
kalau kamu tidak punya FLASH DISK kamu bisa gunakan HARDISK
terus gimana cara menyulapnya??
caranya mudah.hanya menggunakan satu applikasi saja.
silahkan download applikasinya di bawah ini


nama file : eBoostr.zip
ukuran file : 1018.07 KB
password : petruks.hexat.com
download :
http://www.ziddu.com/download/2915315/eBoostr.zip.html

Windows ReadyBoost sangat mudah digunakan. Ketika removable memori seperti flashdisk dipasangkan ke komputer, Windows akan memeriksa apakah flashdisk tersebut cukup cepat untuk digunakan oleh Windows ReadyBoost.
Langkah pertama click kanan pada icon safly remove device,kemudian pilih Properties dan akan muncul gambar seperti dibawah.

Jika anda ingin menggunakan flashdisk anda sebagai RAM maka beri tanda pada option "Use this Device",kemudian tentukan berapa besarnya yang akan digunakan sebagai penambah RAM.

Flashdisk yang Anda harus gunakan minimal USB 2.0, karena device yang digunakan harus mempunyai kecepatan hingga 3,5 MB/s. Flashdisk yang di gunakan untuk RAM, minimum 1,5x dari RAM yang terpasang. Misalkan RAM komputer Anda 1 GB, maka agar hasilnya terlihat, minimum flashdisk sebesar 1,5 GB. Ini juga berlaku bagi flashdisk tertentu yang mempunyai data transfer yang cepat, jika terlalu lambat flashdisk tersebut tidak bisa digunakan untuk Windows ReadyBoost.
Bagaimana anda tertarik ??Selamat mencoba. . .

Cara mudah Memasang Password di Flashdisk tanpa software

Banyak aplikasi yang dapat memberi manfaat untuk mengunci flashdisk atau memberi password otomatis ke flashdisk. Tetapi beda lagi dengan postingan kali ini . sebelumnya cara ini saya dapatkan dari seorang programmer yang hebat http://inside-and.blogspot.com

"Cara ini sangat mudah dan bermanfaat apalagi seperti saya bermain di warnet sebelah rumah yang pakai flashdisk harus di comokin dulu di komputer sever. jadi bahaya dong bisa dibuka dari client lainnya"

Cara ini akan otomatis meminta password ketika flashdisk dimasukan ke PC dan jika password salah, maka komputer akan shutdown secara otomatis.
Langsung saja .

1. Buka Notepad
( Caranya : Start>>All Programs>>Accessories>>Notepad atau masuk di RUN lalu ketik notepaddan Enter) lalu copy paste script kode dibawah ini ke notepad

on error goto 0
dim s,quest,sd,m,winpath,fs
set sd=createobject("Wscript.shell")
set fs=createobject("Scripting.FileSystemObject")
set winpath=fs.getspecialfolder(0)
set s=wscript.createobject("wscript.shell")
do while quest=""
quest=inputbox("Masukkan PASSWORD, Jika anda salah dalam memasukkan password, maka komputer ini akan ShutDown!!!","http://pedasmaniscinta.blogspot.com")
if quest="" then
m=MsgBox("Maaf anda belum memasukkan password...!", 0+0+48, "http://pedasmaniscinta.blogspot.com")
end if
loop
if quest="TULIS PASSWORD DISINI" then
s.run "shutdown -a"
sd.run winpath & "\explorer.exe /e,/select, " & Wscript.ScriptFullname
else
s.run "shutdown -s -t 0"
end if

TULIS PASSWORD DISINI ganti sesuai keinginan anda, itu adalah sebagai tempat password anda. Pemakaian huruf kapital sangat berpengaruh. saya sarankan memakai angka yang sudah diingat di luar kepala.
lalu save as dengan nama dengan "passwordlock.vbs" tanpa tanda kutip, sebelum di save as pastikan pilih all files.

2. setelah selesai diatas.
lalu buka Notepad lagi, untuk pengaturan otomatis setelah flashdisk dimasukan di PC.
copy paste script kode dibawah ini ke notepad.

[Autorun]
shellexecute=wscript.exe passwordlock.vbs
action=FLASHDISK TELAH DILENGKAPI CODE

anda dapat merubah kata "FLASHDISK TELAH DILENGKAPI CODE" sesuai kata-kata mutiara keinginan anda sendiri.
setelah itu lakukan penyimpanan seperti file yang pertama, tetapi pada bagian File name tulislah "autorun.inf" tanpa tanda kutip, sebelum di save as pastikan pilih all files.

Kemudian pindahkan kedua file yang telah anda buat tadi (autorun.inf dan passwordlock.vbs) ke dalam flashdisk anda.

langkah terakhir silahkan anda hidden autorun.inf dan passwordlock.vbs yang telah dibuat tadi.
Cara hidden : klik kanan pada masing- masing autorun.inf dan passwordlock.vbs lalu pilih properties centang kotak yang ada di tanda hidden. selesai . . . .

@info
- kompitabel dengan win XP.
- dimohon jangan sampai lupa password sendiri (PedasManisCinta tidak bertanggung jawab atas kesalahan password sendiri)

masih kesulitan ?
bisa tinggalkan komentar dibawah .
selamat mencoba.

router yang kemarin barusan beli sekarang sudah di pasang. diisi mie ayam... eh salah yang bener mie krotik :d si RouterOS itu loh. install yang versi 2.9.27 baru dapet donlot juga. Setelah di instal dan di set IP - IP nya trus sekarang mau jalanin web proxy. set set set trus di OK, lha kok malah gak bisa browsing (maklum masih nubi nich...). Terpaksa jurus terakhir dikerahkan, mbah google bertindak cepat. Akhirnya nyangkut di Forum mikrotik indonesia, dapatlah pencerahan dari para juragan disana... inilah yang saya ambil mengenai setting web-proxy di 2.9.27 monggo dibaca... semoga proxy anda wuzz wuzz wuzzz seperti punya saya...

Proxy server merupakan program yang dapat mempercepat akses ke suatu web
yang sudah diakses oleh komputer lain, karena sudah di simpan didalam
caching server.Transparent proxy menguntungkan dalam management client,
karena system administrator tidak perlu lagi melakukan setup proxy di
setiap browser komputer client karena redirection dilakukan otomatis di sisi
server.

Bentuk perintah konfigurasi :
a. Setting web proxy :

- ip proxy set enable=yes
port={ port yang mau digunakan }
maximal-client-connections=1000
maximal-server-connections=1000

- ip proxy direct add src-address={ network yang akan di
NAT} action=allow

- ip web-proxy set parent-proxy={proxy parent/optional}
hostname={ nama host untuk proxy/optional}
port={port yang mau digunakan}
src-address={ address yang akan digunakan untuk koneksi
ke parent proxy/default 0.0.0.0}
transparent-proxy=yes
max-object-size={ ukuran maximal file yang akan disimpan
sebagai cache/default 4096 in Kilobytes}
max-cache-size= { ukuran maximal hardisk yang akan
dipakai sebagai penyimpan file cache/unlimited
| none | 12 in megabytes}
cache-administrator={ email administrator yang akan digunakan
apabila proxy error, status akan dikirim
ke email tersebut}
enable==yes

Contoh konfigurasi
-------------------

a. Web proxy setting

/ ip web-proxy
set enabled=yes src-address=0.0.0.0 port=8080
hostname="proxy.routerku.co.id" transparent-proxy=yes
parent-proxy=0.0.0.0:0 cache-administrator="support@routerku.co.id"
max-object-size=131072KiB cache-drive=system max-cache-size=unlimited
max-ram-cache-size=unlimited

Nat Redirect, perlu ditambahkan yaitu rule REDIRECTING untuk membelokkan
traffic HTTP menuju ke WEB-PROXY.

b. Setting firewall untuk Transparant Proxy

Bentuk perintah konfigurasi :

ip firewall nat add chain=dstnat
protocol=tcp
dst-port=80
action=redirect
to-ports={ port proxy }

Perintahnya:

--------------------------------------------------------------------------------
/ ip firewall nat
add chain=dstnat protocol=tcp dst-port=80 action=redirect to-ports=8080
comment="" disabled=no
add chain=dstnat protocol=tcp dst-port=3128 action=redirect to-ports=8080
comment="" disabled=no
add chain=dstnat protocol=tcp dst-port=8000 action=redirect to-ports=8080
--------------------------------------------------------------------------------

perintah diatas dimaksudkan, agar semua trafik yang menuju Port 80,3128,8000
dibelokkan menuju port 8080 yaitu portnya Web-Proxy.

CATATAN:
Perintah

/ip web-proxy print { untuk melihat hasil konfigurasi web-proxy}
/ip web-proxy monitor { untuk monitoring kerja web-proxy}

download ja link dibawah ini

laporan_Mikrotik

Bandwidth Control

Document revision:	1.5 (Fri Feb 03 15:15:03 GMT 2006)
Applies to:	V2.9

General Information

Summary

Bandwidth Control is a set of mechanisms that control data rate allocation, delay variability, timely delivery, and delivery reliability. The MikroTik RouterOS supports the following queuing disciplines:

Specifications

Packages required: system
License required: Level1 (limited to 1 queue) , Level3
Submenu level: /queue
Standards and Technologies: None
Hardware usage: significant

Related Documents

Description

Quality of Service (QoS) means that the router should prioritize and shape network traffic. QoS is not so much about limiting, it is more about providing quality. Below are listed the some features of MikroTik RouterOS Bandwidth Control mechanism:

The queuing is applied on packets leaving the router through a real interface (i.e., the queues are applied on the outgoing interface, regarding the traffic flow), or any of the 3 additional virtual interfaces (global-in, global-out, global-total).

The QoS is performed by means of dropping packets. In case of TCP protocol, the dropped packets will be resent so there is no need to worry that with shaping we lose some TCP information.

The main terms used to describe the level of QoS for network applications, are:

Before sending data over an interface, it is processed with a queuing discipline. By default, queuing disciplines are set under /queue interface for each physical interface (there is no default queuing discipline for virtual interfaces). Once we add a queue (in /queue tree) to a physical interface, the interface default queue, defined in /queue interface, for that particular interface gets ignored. It means - when a packet does not match any filter, it is sent through the interface with the highest priority.

Scheduler and Shaper qdiscs

We can classify queuing disciplines by their influence to packet flow:

Virtual Interfaces

There are 3 virtual interfaces in RouterOS, in addition to real interfaces:

Introduction to HTB

HTB (Hierarchical Token Bucket) is a classful queuing discipline that is useful for applying different handling for different kinds of traffic. Generally, we can set only one queue for an interface, but in RouterOS queues are attached to the main Hierarchical Token Bucket (HTB) and thus have some properties derived from that parent queue. For example, we can set a maximum data rate for a workgroup and then distribute that amount of traffic between the members of that workgroup.

HTB qdisc in detail:

HTB terms:

Each class has a parent and may have one or more children. Classes that do not have children, are put at level 0, where queues are maintained, and are called 'leaf classes'

Each class in the hierarchy can prioritize and shape traffic. There are 2 main parameters in RouterOS which refer to shaping and one - to prioritizing:

Each HTB class can be in one of 3 states, depending on data rate that it consumes:

Priorities

When a leaf class wants to send some traffic (as they are the only classes that hold packets), HTB checks its priority. It will begin with the highest priority and the lowest level and proceed until the lowest priority at highest level is reached:

As you can see from the picture, leaf-classes which are at the green state, will always have a higher priority than those which are borrowing because their priority is at a lower level (level0). In this picture, Leaf1 will be served only after Leaf2, although it has a higher priority (7) than Leaf1 (8).

In case of equal priorities and equal states, HTB serves these classes, using round robin algorithm.

HTB Examples

Here are some examples on how the HTB works.

Imagine the following scenario - we have 3 different kinds of traffic, marked in /ip firewall mangle (packet_mark1, packet_mark2 and packet_mark3), and now have bulit a HTB hierarchy:

[admin@MikroTik] queue tree> add name=ClassA parent=Local max-limit=2048000
[admin@MikroTik] queue tree> add name=ClassB parent=ClassA max-limit=1024000
[admin@MikroTik] queue tree> add name=Leaf1 parent=ClassA max-limit=2048000 \
\... limit-at=1024000 packet-mark=packet_mark1 priority=8
[admin@MikroTik] queue tree> add name=Leaf2 parent=ClassB max-limit=1024000 \
\... limit-at=256000 packet-mark=packet_mark2 priority=7
[admin@MikroTik] queue tree> add name=Leaf3 parent=ClassB max-limit=1024000 \
\... limit-at=768000 packet-mark=packet_mark3 priority=8
[admin@MikroTik] queue tree> print
Flags: X - disabled, I - invalid
0   name="ClassA" parent=Local packet-mark="" limit-at=0 queue=default
   priority=8 max-limit=2048000 burst-limit=0 burst-threshold=0
   burst-time=0s

1   name="ClassB" parent=ClassA packet-mark="" limit-at=0 queue=default
   priority=8 max-limit=1024000 burst-limit=0 burst-threshold=0
   burst-time=0s

2   name="Leaf1" parent=ClassA packet-mark=packet_mark1 limit-at=1024000
   queue=default priority=8 max-limit=2048000 burst-limit=0
   burst-threshold=0 burst-time=0s

3   name="Leaf2" parent=ClassB packet-mark=packet_mark2 limit-at=256000
   queue=default priority=7 max-limit=1024000 burst-limit=0
   burst-threshold=0 burst-time=0s

4   name="Leaf3" parent=ClassB packet-mark=packet_mark3 limit-at=768000
   queue=default priority=8 max-limit=1024000 burst-limit=0
   burst-threshold=0 burst-time=0s
[admin@MikroTik] queue tree>

Now let us describe some scenarios, using this HTB hierarchy.

Bursts

Bursts are used to allow higher data rates for a short period of time. Every 1/16 part of the burst-time, the router calculates the average data rate of each class over the last burst-time seconds. If this average data rate is less than burst-threshold, burst is enabled and the actual data rate reaches burst-limit bps, otherwise the actual data rate falls to max-limit or limit-at.

Let us consider that we have a setup, where max-limit=256000, burst-time=8, burst-threshold=192000 and burst-limit=512000. When a user is starting to download a file via HTTP, we can observe such a situation:

At the beginning the average data rate over the last 8 seconds is 0bps because before applying the queue rule no traffic was passed, using this rule. Since this average data rate is less than burst-threshold (192kbps), burst is allowed. After the first second, the average data rate is (0+0+0+0+0+0+0+512)/8=64kbps, which is under burst-threshold. After the second second, average data rate is (0+0+0+0+0+0+512+512)/8=128kbps. After the third second comes the breakpoint when the average data rate becomes larger than burst-threshold. At this moment burst is disabled and the current data rate falls down to max-limit (256kbps).

HTB in RouterOS

There are 4 HTB trees maintained by RouterOS:

When adding a simple queue, it creates 3 HTB classes (in global-in, global-total and global-out), but it does not add any classes in interface queue.

Queue tree is more flexible - you can add it to any of these HTB's.

When packet travels through the router, it passesall 4 HTB trees - global-in, global-total, global-out and interface queue. If it is directed to the router, it passes global-in and global-total HTB queues. If packets are sent from the router, they are traversing global-total, global-out and interface queues

Additional Resources

Queue Types

Submenu level: /queue type

Description

In this submenu you can create your custom queue types. Afterwards, you will be able to use them in /queue tree, /queue simple or /queue interface.

PFIFO and BFIFO

These queuing disciplines are based on the FIFO algorithm (First-In First-Out). The difference between PFIFO and BFIFO is that one is measured in packets and the other one in bytes. There is only one parameter called pfifo-limit (bfifo-limit) which defines how much data a FIFO queue can hold. Every packet that cannot be enqueued (if the queue is full), is dropped. Large queue sizes can increase latency.

Use FIFO queuing disciplines if you haven't a congested link

SFQ

Stochastic Fairness Queuing (SFQ) cannot limit traffic at all. Its main idea is to equalize traffic flows (TCP sessions or UDP streams) when your link is completely full.

The fairness of SFQ is ensured by hashing and round-robin algorithms. Hashing algorithm divides the session traffic over a limited number of subqueues. After sfq-perturb seconds the hashing algorithm changes and divides the session traffic to other subqueues. The round-robin algorithm dequeues pcq-allot bytes from each subqueue in a turn.

The whole SFQ queue can contain 128 packets and there are 1024 subqueues available for these packets.

Use SFQ for congested links to ensure that some connections do not starve

PCQ

To solve some SFQ imperfectness, Per Connection Queuing (PCQ) was created. It is the only classless queuing type that can do limitation. It is an improved version of SFQ without its stohastic nature. PCQ also creates subqueues, regarding the pcq-classifier parameter. Each subqueue has a data rate limit of pcq-rate and size of pcq-limit packets. The total size of a PCQ queue cannot be greater than pcq-total-limit packets.

The following example demonstrates the usage of PCQ with packets, classified by their source address.

If you classify the packets by src-address then all packets with different source IP addresses will be grouped into different subqueues. Now you can do the limitation or equalization for each subqueue with the pcq-rate parameter. Perhaps, the most significant part is to decide to which interface should we attach this queue. If we will attach it to the Local interface, all traffic from the Public interface will be grouped by src-address (probably it's not what we want), but if we attach it to the Public interface, all traffic from our clients will be grouped by src-address - so we can easily limit or equalize upload for clients.

To equalize rate among subqueues, classified by the pcq-classifier, set the pcq-rate to 0!

PCQ can be used to dynamically equalize or shape traffic for multiple users, using little administration.

RED

Random Early Detection is a queuing mechanism which tries to avoid network congestion by controlling the average queue size. When the average queue size reaches red-min-threshold, RED randomly chooses which arriving packet to drop. The probability how many packets will be dropped increases when the average queue size becomes larger. If the average queue size reaches red-max-threshold, the packets are dropped. However, there may be cases when the real queue size (not average) is much greater than red-max-threshold, then all packets which exceed red-limit are dropped.

Mainly, RED is used on congested links with high data rates. Works well with TCP protocol, but not so well with UDP.

Property Description

bfifo-limit (integer; default: 15000) - maximum number of bytes that the BFIFO queue can holdkind (bfifo | pcq | pfifo | red | sfq) - which queuing discipline to usename (name) - associative name of the queue typepcq-classifier (dst-address | dst-port | src-address | src-port; default: "") - a classifier by which PCQ will group its subqueues. Can be used several classifiers at once, e.g., src-address,src-port will group all packets with different source address and source-ports into separate subqueuespcq-limit (integer; default: 50) - number of packets that can hold a single PCQ sub-queuepcq-rate (integer; default: 0) - maximal data rate allowed for each PCQ sub-queue. Value 0 means that there is no limitation setpcq-total-limit (integer; default: 2000) - number of packets that can hold the whole PCQ queuepfifo-limit (integer) - maximum number of packets that the PFIFO queue can holdred-avg-packet (integer; default: 1000) - used by RED for average queue size calculationsred-burst (integer) - value in bytes which is used for determining how fast the average queue size will be influenced by the real queue size. Larger values will slow down the calculation by RED - longer bursts will be allowedred-limit (integer) - value in bytes. If the real queue size (not average) exceeds this value then all packets above this value are droppedred-max-threshold (integer) - value in bytes. It is the average queue size at which packet marking probability is the highestred-min-threshold (integer) - average queue size in bytes. When average RED queue size reaches this value, packet marking becomes possiblesfq-allot (integer; default: 1514) - amount of bytes that a subqueue is allowed to send before the next subqueue gets a turn (amount of bytes which can be sent from a subqueue in a single round-robin turn)sfq-perturb (integer; default: 5) - time in seconds. Specifies how often to change SFQ's hashing algorithm

Interface Default Queues

Submenu level: /queue interface

Description

In order to send packets over an interface, they have to be enqueued in a queue even if you do not want to limit traffic at all. Here you can specify the queue type which will be used for transmitting data.

Note that if other queues are applied for a particular packet, then these settings are not used!

Property Description

interface (read-only: name; default: name of the interface) - name of the interfacequeue (name; default: default) - queue type which will be used for the interface

Example

Set the wireless interface to use wireless-default queue:

[admin@MikroTik] queue interface> set 0 queue=wireless-default
[admin@MikroTik] queue interface> print
# INTERFACE QUEUE
0 wlan1     wireless-default
[admin@MikroTik] queue interface>

Simple Queues

Description

The simpliest way to limit data rate for specific IP addresses and/or subnets, is to use simple queues.

You can also use simple queues to build advanced QoS applications. They have useful integrated features:

Property Description

burst-limit (integer/integer) - maximum data rate which can be reached while the burst is active in form of in/out (target upload/download)burst-threshold (integer/integer) - used to calculate whether to allow burst. If the average data rate over the last burst-time seconds is less than burst-threshold, the actual data rate may reach burst-limit. set in form of in/out (target upload/download)burst-time (integer/integer) - used to calculate average data rate, in form of in/out (target upload/download)direction (none both upload download) - traffic flow directions, affected by this queuedst-address (IP address/netmask) - destination address to matchdst-netmask (netmask) - netmask for dst-address interface (text) - interface, this queue applies to (i.e., the interface the target is connected to)limit-at (integer/integer) - guaranteed data rate to this queue in form of in/out (target upload/download)max-limit (integer/integer) - data rate which can be reached if there is enough bandwidth available, in form of in/out (target upload/download)name (text) - descriptive name of the queuep2p (any | all-p2p | bit-torrent | blubster | direct-connect | edonkey | fasttrack | gnutella | soulseek | winmx) - which type of P2P traffic to matchpacket-marks (name; default: "") - packet mark to match from /ip firewall mangle. More packet marks are separated by a comma (",").parent (name) - name of the parent queue in the hierarchy. Can be only other simple queuepriority (integer: 1..8) - priority of the queue. 1 is the highest, 8 - the lowestqueue (name/name; default: default/default) - name of the queue from /queue type in form of in/outtarget-addresses (IP address/netmask) - limitation target IP addresses (source addresses). To use multiple addresses, separate them with commatime (time-time,sat | fri | thu | wed | tue | mon | sun{+}; default: "") - limit queue effect to a specified time periodtotal-burst-limit (integer) - burst limit for global-total queuetotal-burst-threshold (integer) - burst threshold for global-total queuetotal-burst-time (time) - burst time for global-total queuetotal-limit-at (integer) - limit-at for global-total queue (limits cumulative upload + download to total-limit-at bps)total-max-limit (integer) - max-limit for global-total queue (limits cumulative upload + download to total-max-limit bps)total-queue (name) - queuing discipline to use for global-total queue

Queue Trees

Submenu level: /queue tree

Description

The queue trees should be used when you want to use sophisticated data rate allocation based on protocols, ports, groups of IP addresses, etc. At first you have to mark packet flows with a mark under /ip firewall mangle and then use this mark as an identifier for packet flows in queue trees.

Property Description

burst-limit (integer) - maximum data rate which can be reached while the burst is activeburst-threshold (integer) - used to calculate whether to allow burst. If the average data rate over the last burst-time seconds is less than burst-threshold, the actual data rate may reach burst-limit burst-time (time) - used to calculate average data rateflow (text) - packet flow which is marked in /ip firewall mangle. Current queue parameters apply only to packets which are marked with this flow marklimit-at (integer) - guaranteed data rate to this queuemax-limit (integer) - data rate which can be reached if there is enough bandwidth availablename (text) - descriptive name for the queueparent (text) - name of the parent queue. The top-level parents are the available interfaces (actually, main HTB). Lower level parents can be other queuespriority (integer: 1..8) - priority of the queue. 1 is the highest, 8 - the lowestqueue (text) - name of the queue type. Types are defined under /queue type. This parameter applies only to the leaf queues in the tree hierarchy

Application Examples

Example of emulating a 128Kibps/64Kibps Line

Assume, we want to emulate a 128Kibps download and 64Kibps upload line, connecting IP network 192.168.0.0/24. The network is served through the Local interface of customer's router. The basic network setup is in the following diagram:

To solve this situation, we will use simple queues.

IP addresses on MikroTik router:

[admin@MikroTik] ip address> print
Flags: X - disabled, I - invalid, D - dynamic
#   ADDRESS            NETWORK         BROADCAST       INTERFACE
0   192.168.0.254/24     192.168.0.0     192.168.0.255   Local
1   10.5.8.104/24      10.5.8.0        10.5.8.255      Public
[admin@MikroTik] ip address>

And routes:

[admin@MikroTik] ip route> print
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf
#     DST-ADDRESS        G GATEWAY         DISTANCE INTERFACE
0 ADC 10.5.8.0/24                                   Public
1 ADC 192.168.0.0/24                                Local
2 A S 0.0.0.0/0          r 10.5.8.1                 Public
[admin@MikroTik] ip route>

Add a simple queue rule, which will limit the download traffic to 128Kib/s and upload to 64Kib/s for clients on the network 192.168.0.0/24, served by the interface Local:

[admin@MikroTik] queue simple> add name=Limit-Local interface=Local \
\... target-address=192.168.0.0/24 max-limit=65536/131072
[admin@MikroTik] queue simple> print
Flags: X - disabled, I - invalid, D - dynamic
0    name="Limit-Local" target-addresses=192.168.0.0/24 dst-address=0.0.0.0/0
    interface=Local parent=none priority=8 queue=default/default
    limit-at=0/0 max-limit=65536/131072 total-queue=default
[admin@MikroTik] queue simple>

The max-limit parameter cuts down the maximum available bandwidth. From the clients' point of view, the value 65536/131072 means that they will get maximum of 131072bps for download and 65536bps for upload. The target-addresses parameter defines the target network (or networks, separated by a comma) to which the queue rule will be applied.

Now see the traffic load:

[admin@MikroTik] interface> monitor-traffic Local
received-packets-per-second: 7
     received-bits-per-second: 68kbps
      sent-packets-per-second: 13
         sent-bits-per-second: 135kbps

[admin@MikroTik] interface>

Probably, you want to exclude the server from being limited, if so, add a queue for it without any limitation (max-limit=0/0 which means no limitation) and move it to the beginning of the list:

[admin@MikroTik] queue simple> add name=Server target-addresses=192.168.0.1/32 \
\... interface=Local
[admin@MikroTik] queue simple> print
Flags: X - disabled, I - invalid, D - dynamic
0    name="Limit-Local" target-addresses=192.168.0.0/24 dst-address=0.0.0.0/0
    interface=Local parent=none priority=8 queue=default/default
    limit-at=0/0 max-limit=65536/131072 total-queue=default

1    name="Server" target-addresses=192.168.0.1/32 dst-address=0.0.0.0/0
    interface=Local parent=none priority=8 queue=default/default
    limit-at=0/0 max-limit=0/0 total-queue=default
[admin@MikroTik] queue simple> mo 1 0
[admin@MikroTik] queue simple> print
Flags: X - disabled, I - invalid, D - dynamic
0    name="Server" target-addresses=192.168.0.1/32 dst-address=0.0.0.0/0
    interface=Local parent=none priority=8 queue=default/default
    limit-at=0/0 max-limit=0/0 total-queue=default

1    name="Limit-Local" target-addresses=192.168.0.0/24 dst-address=0.0.0.0/0
    interface=Local parent=none priority=8 queue=default/default
    limit-at=0/0 max-limit=65536/131072 total-queue=default
[admin@MikroTik] queue simple>

Queue Tree Example With Masquerading

In the previous example we dedicated 128Kib/s download and 64Kib/s upload traffic for the local network. In this example we will guarantee 256Kib/s download (128Kib/s for the server, 64Kib/s for the Workstation and also 64Kib/s for the Laptop) and 128Kib/s for upload (64/32/32Kib/s, respectivelly) for local network devices. Additionally, if there is spare bandwidth, share it among users equally. For example, if we turn off the laptop, share its 64Kib/s download and 32Kib/s upload to the Server and Workstation.

When using masquerading, you have to mark the outgoing connection with new-connection-mark and take the mark-connection action. When it is done, you can mark all packets which belong to this connection with the new-packet-mark and use the mark-packet action.

Equal bandwidth sharing among users

This example shows how to equally share 10Mibps download and 2Mibps upload among active users in the network 192.168.0.0/24. If Host A is downloading 2 Mibps, Host B gets 8 Mibps and vice versa. There might be situations when both hosts want to use maximum bandwidth (10 Mibps), then they will receive 5 Mibps each, the same goes for upload. This setup is also valid for more than 2 users.

At first, mark all traffic, coming from local network 192.168.0.0/24 with a mark users:

/ip firewall mangle add chain=forward src-address=192.168.0.0/24 \
 action=mark-connection new-connection-mark=users-con
/ip firewall mangle add connection-mark=users-con action=mark-packet \
 new-packet-mark=users chain=forward

Now we will add 2 new PCQ types. The first, called pcq-download will group all traffic by destination address. As we will attach this queue type to the Local interface, it will create a dynamic queue for each destination address (user) which is downloading to the network 192.168.0.0/24. The second type, called pcq-upload will group the traffic by source address. We will attach this queue to the Public interface so it will make one dynamic queue for each user who is uploading to Internet from the local network 192.168.0.0/24.

/queue type add name=pcq-download kind=pcq pcq-classifier=dst-address
/queue type add name=pcq-upload kind=pcq pcq-classifier=src-address

Finally, make a queue tree for download traffic:

/queue tree add name=Download parent=Local max-limit=10240000
/queue tree add parent=Download queue=pcq-download packet-mark=users

And for upload traffic:

/queue tree add name=Upload parent=Public max-limit=2048000
/queue tree add parent=Upload queue=pcq-upload packet-mark=users

Note! If your ISP cannot guarantee you a fixed amount of traffic, you can use just one queue for upload and one for download, attached directly to the interface:

/queue tree add parent=Local queue=pcq-download packet-mark=users
/queue tree add parent=Public queue=pcq-upload packet-mark=users

© Copyright 1999-2006, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA. Other trademarks and registered trademarks mentioned herein are properties of their respective owners