Thursday, September 17th, 2015 | Author:
  • Parte 1 – Introduction – Occasus sursum Simple Queues (Post haec)
  • Parte 2 – Firmissimeque Identifying traffic – Occasus sursum Mangle Regulis (Cras interdum sollicitudin TM)
  • Parte 3 – Bonorumque limitibus – Occasus sursum Queue arbores (Cras interdum sollicitudin TM)
  • Parte 4 – Monitoring Usage – Queues redefining – Limiting Abusive Devices (Cras interdum sollicitudin TM)
  • Parte 5 – ??? Quaestus ???

Introduction

The first problem one usually comes across after being tasked with improving an Internet connection is that the connection is overutilised. Nemo scit quid typice, qui, aut quod est causa forsit – except of course everyone blames the ISP. Quandoque vero est ISP – but typically you can’t prove that without having an alternative connection immediately available. I currently manage or help manage four “sites / premissis” qui usi QoS ad eorum tractarent Internet connectivity. Una est workplace, two are home connections, and the last one is a slightly variable one – sed plerumque iustus a nexu domum alternatively, for a weekend every few months, it becomes a 140-hominis (et crescit) LAN. Fun. 🙂

Et MikroTik RouterOS

MikroTik'S RouterOS is very powerful in the right hands. Many other routers support QoS but not with the fine-grain control MikroTik provides. Alternatively you could utilise other Linux-based router OS’s, qualis DD-WRT, Smoothwall, Untangle, et sic porro,. Plerique ex his typice postulo ut vos have a parce server circa caesae aut compatitur hardware router. Mikrotik vendit RouterBoards qui RouterOS builtin – et sunt relative insumptuosus.

Quid mihi usu venerit cum iter est cum primo Scelerisque vitae et MikroTik – and my experience with QoS is primarily with Disponis scriptor NetEnforcer / NetXplorer ratio et MikroTik. Maxime popularis cogitationibus MikroTik in experientia (aliud quam diu range bezvadu artibus dediti) fuisse rb750 (novus poema poematis nomine “CANTATRIX“) et rb950-dicentur tabulata. Habent multis aliis available and are relatively inexpensive. In historical comparison with Cisco’s premium devices, Ive 'tendebat describere MikroTik scriptor artes non “90% at liniamenta 10% sumptus”. Sicut dux est hoc maxime spectant SME / Home use, inexpensive makes more sense. If you’re looking at getting a MikroTik device, notandum quod MikroTik iter facere non typically include DSL modems, sic existens apparatum est typice adhuc necessarium. Sciendum est etiam quod haec est non a doceo in occasus sursum a MikroTik variis artibus demorari ne VULNUS. Sunt enim multa iam duces online.

Ratio in usu – primus gradus

Erigat QoS recte, you need to have an idea of a policy that takes into account the following:

  • Altiore nexu celeritate
  • Quot users / confidit cogitationibus exsisto usura nexu
  • The users/devices/services/protocols that should be prioritised for latency and/or throughput

Ad ipsum quoque exemplo supra, Adsumem sequentibus:

  • Et cum erigitur MikroTik defectu loci ubi figura network retiacula 192.168.88.0/24 et datur via Penitus iunctio PPPoE.
  • Nexum celeritas X / 2Mbps (10 Mbps download celeritatum; 2 Mbps upload celeritas)
  • Ibi erit 5 cum users quotquot 15 cogitationes (multiple computers / tabulas / mobile phones / WiFi etc)
  • Typicam downloads requirunt excelsum prioritate cum throughput sed low-prioritate cum latency
  • Gaming/Skype/Administrative protocols require high priority with both latency and throughput
  • No users sint prae aliis prioritized

The first and probably quickest step is to set up what RouterOS refers to as a Simple Queue.

Feci brevi script remisisse meo MikroTik cogitationes erigat simplices queues. Ea est huiusmodi:

:nam x ex 1 ad 254 do ={
 /queue simplex add name ="internet usage- $ x-" dst ="pppoe" max terminum = 1900k / 9500k target ="192.168.88.$x"
}

Quod superius limitem agit maxima arte cuiquam posse “1900k” (1.9Mb) et upload “9500k” (9.5Mb) download.

Notes:

  • Ratio est cur max limites sunt 95% of the line’s maximum speed is that this guarantees no single device can fully starve the connection, negatively affecting the other users. With a larger userbase I would enforce this limit further. Verbigratia, apud 100 users in ministerium 20MB ut adponam terminum 15MB vel etiam ut paulo 1Mb. Hoc est omnino dependens in quam “abusive” users sunt et, ut et vos instar sicco qua quanto abusum contingit, you can adjust it appropriately.
  • Praepositione “internet usu-” Lorem modularis in nomine. Ego typice posuit referre ad premissa vocatis nomine. Verbigratia, with premises named “alpha” et “beta”, Ego typice posuit “internet alpha-” et “internet beta-”. Hoc iuvat cum instinctu differentiam inter sites.
  • Lineamento dst parameter habet “pppoe” in exemplum. Hoc nomine substituantur interface that provides the Internet connection.

Mos accumsan scriptum esse convenientia configuration. Salvum MikroTik et currere ad scriptionem – directe vel crustulum in MikroTik sui terminale mihi facturos confirmaverunt.

In my next post I will go over setting up what RouterOS refers to as Colluvione prognati fuerint praecepta. Has regulas inserviunt identify / classify retiacula in traffic ut pulchrius-far adoreum QoS possibile.

Share
Category: random
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, aut trackback from your own site.
Leave a Reply » Log in