MikroTik Router OS V3.0 User Manual

							[admin@MikroTik] ip traffic-flow> printenabled: yesinterfaces: allcache-entries: 1kactive-flow-timeout: 30minactive-flow-timeout: 15s[admin@MikroTik] ip traffic-flow>
2.! *$ 	 	
 
  
 
   ( 	7# 	

[admin@MikroTik] ip traffic-flow target> add address=192.168.0.2:2055 \\... version=9[admin@MikroTik] ip traffic-flow target> printFlags: X - disabled# ADDRESS VERSION0 192.168.0.2:2055 9[admin@MikroTik] ip traffic-flow target>
9 
 
 
	
 
 
 	
 
 	7# 
	


! 

  9 	  	 	
 	7# 
	

   
 	

	 
 
 
 	 	
 
	

 # 	  	
 
  
	 	 

 
 
  	 	
 
	 	 


Page 270 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							 (	 

 	 	 


	 	  	 

Page 271 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							Page 272 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							Log Management
Document revision 2.4 (February 6, 2008, 1:40 GMT)
This document applies to MikroTik RouterOS V3.0
Table of Contents
TableofContents
Summary
Specifications
Description
GeneralSettings
PropertyDescription
Example
Actions
PropertyDescription
Notes
Example
LogMessages
Description
PropertyDescription
Example
General Information
Summary
O	 
 (

 	
 
	
 
	

 	
   A 	
  	( 
 	 
 
	 
 
 

 
 	
 	  
 	 
 ( 


 	  	
  ( 	
		 6
 ! 	
  	
  
	 

Specifications
Packages required:system
License required:level1
Home menu level:/system logging, /log
Standards and Technologies:Syslog
Hardware usage:Not significant
Description
A 	( 

   
 A  	 
 	
  
 
  	  	
 
 A	   	
  
 
  &	
  	 
 
 
   
	 

 	 ( &

 
	  	
 	  	  	 
General Settings
Home menu level:/system logging
Page 273 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							Property Description
action(name; default:memory) - specifies one of the system default actions or user specified
action listed in /system logging action
prefix(text) - local log prefix
topics(info|critical|firewall|keepalive|packet|read|timer|write|ddns|hotspot|l2tp|ppp|
route|update|account|debug|ike|manager|pppoe|script|warning|async|dhcp|notification
|pptp|state|watchdog|bgp|error|ipsec|radius|system|web-proxy|calc|event|isdn|ospf|
raw|telephony|wireless|e-mail|gsm|mme|ntp|open|ovpn|pim|radvd|rip|sertcp|ups;
default:info) - specifies log group or log message type
Example
  	 
	
 	 
	
  	  	(
 
 
 	 
[admin@MikroTik] system logging> add topics=firewall action=memory[admin@MikroTik] system logging> printFlags: X - disabled, I - invalid# TOPICS ACTION PREFIX0 info memory1 error memory2 warning memory3 critical echo4 firewall memory[admin@MikroTik] system logging>
Actions
Home menu level:/system logging action
Property Description
disk-lines(integer; default:100) - number of records in log file saved on the disk (only if action
target is set to disk)
disk-stop-on-full(yes | no; default:no) - whether to stop to save log messages on disk after the
specified disk-lines number is reached
email-to(name) - email address logs are sent to (only if action target is set to email)
memory-lines(integer; default:100) - number of records in local memory buffer (only if action
target is set to memory)
memory-stop-on-full(yes | no; default:no) - whether to stop to save log messages in local buffer
after the specified memory-lines number is reached
name(name) - name of an action
remember(yes | no; default:yes) - whether to keep log messages, which have not yet been
displayed in console (only if action target is set to echo)
remote(IP addressport; default:0.0.0.0:514) - remote logging servers IP address and UDP port
(only if action target is set to remote)
target(disk|echo|email|memory|remote; default:memory) - log storage facility or target
•disk- logs are saved to the hard drive
•echo- logs are displayed on the console screen
Page 274 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							•email- logs are sent by email
•memory- logs are saved to the local memory buffer
•remote- logs are sent to a remote host
Notes
E 	


 
  
	 	
 	


Example
 	 	 
 	

 
 
	 
 
	
  	(  
 	   
   
  	
 
	
  add name=short \\... target=memory memory-lines=50 memory-stop-on-full=yes[admin@MikroTik] system logging action> printFlags: * - default# NAME TARGET REMOTE0 * memory memory1 * disk disk2 * echo echo3 * remote remote 0.0.0.0:5144 short memory[admin@MikroTik] system logging action>
Log Messages
Home menu level:/log
Description
5	 	 
  	
Property Description
message(read-only: text) - message text
time(read-only: text) - date and time of the event
topics(read-only: text) - topic list the message belongs to
Example
 ( 
 	 
[admin@MikroTik] > log printTIME MESSAGEdec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:20:36 log configuration changed by admin-- [Q quit|D dump]
 

 
 
 
Page 275 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							[admin@MikroTik] > log print followTIME MESSAGEdec/24/2003 08:20:36 log configuration changed by admindec/24/2003 08:24:34 log configuration changed by admindec/24/2003 08:24:51 log configuration changed by admindec/24/2003 08:25:59 log configuration changed by admindec/24/2003 08:25:59 log configuration changed by admindec/24/2003 08:30:05 log configuration changed by admindec/24/2003 08:30:05 log configuration changed by admindec/24/2003 08:35:56 system starteddec/24/2003 08:35:57 isdn-out1: initializing...dec/24/2003 08:35:57 isdn-out1: dialing...dec/24/2003 08:35:58 Prism firmware loading: OKdec/24/2003 08:37:48 user admin logged in from 10.1.0.60 via telnet-- Ctrl-C to quit. New entries will appear at bottom.
Page 276 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							Bandwidth Control
Document revision 2.2 (November 28, 2007, 10:45 GMT)
This document applies to MikroTik RouterOS V3.0
Table of Contents
TableofContents
Summary
Specifications
Description
AdditionalDocuments
QueueTypes
Description
PropertyDescription
InterfaceDefaultQueues
Description
PropertyDescription
Example
SimpleQueues
Description
PropertyDescription
QueueTrees
Description
PropertyDescription
Exampleofemulatinga128Kibps/64KibpsLine
QueueTreeExampleWithMasquerading
Equalbandwidthsharingamongusers
General Information
Summary
)	

 3

  	 
  	
 
	
 

 	
	 	
 		

 	 (		
 
 (
	
 ( 	
   
 ! 
 
 
 8
 

•5H4H
						

							Packages required:system
License required:level1 (limited to 1 queue), level3
Home menu level:/queue
Standards and Technologies:None
Hardware usage:significant
Description
@	
  !( &@! 	
 
	
 
 
  
2 	
 	 

 
	 @!  

 
 	
 

 
   	
 (
 8	
 ( 
 
 

  ! 	
 
 
 ! 
	 

 	
 	 
 
•
 	
	 	
  
	
 *$ 	 

 
 
 	
 
 		

•
 7
7 
	
•
2  	
  ( 

• 8 
  	
  

•	 8 
  
 

(	
•	 	(		 
	 	
  8	  

 
 
 	  
 	


 8
  	 
 	
 	(
 
 
 
 	 	 

	 & 
 8 	 	 


 

 

	 	
 
 
	   	
  
 : 	

	 (
	 

	 &	7

	7
 	7

	
 @!    	
  
 	
 *
 	  3$ 
 
  	
  


 
 	  	
  
  
 
 
  
	
 
 	
    3$ 
	


 	
 
  
  
 (  @!  

 		

 	
•queuing discipline (qdisc)- an algorithm that holds and maintains a queue of packets. It
accumulates the packets and decides the order of the outgoing packets (it means that queuing
discipline can reorder packets). Qdisc also decides which packets to drop if there is no space for
them.
•CIR (Committed Information Rate)- the guaranteed data rate. It means that traffic rate, not
exceeding this value should always be delivered
•MIR (Maximal Information Rate)- the maximal data rate router will provide
•Priority- the order of importance in what traffic will be processed. You can give priority to
some traffic in order it to be handeled before some other traffic
•Contention Ratio- the ratio to which the defined data rate is shared among users (when a
certain data rate is allocated to a number of subscribers). It is the number of subscribers that
have a single speed limitation, applied to all of them together. For example, the contention ratio
of 1:4 means that the allocated data rate may be shared between no more than 4 users
) 

 	
	 ( 	
 

	 
   
 	 8
 
  	
  
 

8
 
  

	   	
  
 
: 

	 	 	


	 &
  
 	
 8
 
  (
	 

	  
  	 	 
 8 &
:

: 
 
 	 	 

	 
 

	 	
 8  	  ,) 	

 
	
 8 
 
 
 
 
: 

	 
	
 	
	 

	  
  	
(
Page 278 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners. 
						

							Scheduler and Shaper qdiscs
6 	
 	 8
 
  
 

 
 	
 
•schedulers- queuing disciplines only reschedule packets regarding their algorithm and drop
packets which do not fit in the queue. Scheduler queuing disciplines are: PFIFO, BFIFO, SFQ,
PCQ (both scheduler and shaper), RED
•shapers- queuing disciplines that also perform the limitation. Shapers are PCQ (both scheduler
and shaper) and HTB
Virtual Interfaces
 	 : (
	 

	 
 
 ! 
 	

 
 	 

	
•global-in- represents all the input interfaces in general (INGRESS queue). Please note that
queues attached to global-in apply to traffic that is received by the router, before the packet
filtering. global-in queueing is executed just after mangle and dst-nat
•global-out- represents all the output interfaces in general (EGRESS queue). Queues attached to
it apply before the ones attached to a specific interface
•global-total- represents a virtual interface through which all the data, going through the router,
is passing. When attaching a qdisc to global-total, the limitation is done in both directions. For
example, if we set a total-max-limit to 256000, we will get upload+download=256kbps
(maximum)
Introduction to HTB
,) &,		 
 )
  	 	 8
 
 
	
    	
 

 	


 

 
  
	  8  	 
: 
	
: 
	 	

	 
 

	
 ,		 
 )
 &,) # 	  	
 
 	 	 	
	 	
  	  	



 

 
	
 	

  
	 

 
   
	
 
,) 8 
 
	
Page 279 of 480Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.Other trademarks and registred trademarks mentioned herein are properties of their respective owners.