|
|
| Line 4: |
Line 4: |
| | - c<br> | | - c<br> |
| | | | |
| − | =What is QoS= | + | =What is Admin Projects= |
| − | Qos (Quality of Service) is the means of shaping traffic to give certain traffic priority above other. In most cases bulk traffic like p2p, FTP or any other bandwidth consuming transfer protocols gets the lowest priority. By doing this we enable latency dependent protocols like ssh, irc, and gaming to work like it should.
| + | Admin Projects is projects and things to do that was either identified by the Committee members, Admin or users. |
| | | | |
| − | CTWUG uses a combination of WMM, DSCP marks, and queues to prioritise traffic. Traffic is divided into 3 groups namely Bulk, Interactive and Realtime. Bulk traffic has the lowest priority on the network and like its name suggest all bulk traffic, like torrents and DC, goes into this group. Interactive traffic has a high priority, this group is for protocols that require low latency and sometimes higher bandwidth, traffic like games and irc will go into this group. The last group is Realtime, this group is more for low latency dependant traffic like VOIP and has the highest priority.
| + | =Heading= |
| | + | dsafjdsamvkamdsivomsavlkamdskmdsav |
| | | | |
| − | =Identified Ports= | + | =heading= |
| − | Here is a list of ports currently being identified by our QoS rules, please note that of a port is not listed here it will automatically fall withing in the Bulk group. To request new ports to be added please use the discussion page, and specify the application using the port.
| + | dflknmdsavfnmslkdaf |
| | | | |
| | + | ==other heading== |
| | | | |
| | + | ===Wireless Interface Config=== |
| | + | dsavfdsajkfmdsalkfjkdsamfsamd. |
| | | | |
| − | =Current implementation of QoS=
| + | :1. adsfdsafsadf |
| − | This is the current implementation of QoS on all the CTWUG highsites. Due to each highsite having different interfaces the queue trees need to be set up manualy and can't be rolled in with a script, the queue tree scrip posted here is just a template to work from. Please note that these scripts are written for ROS3 and will not work with previous versions.
| + | :2. iloiylkihjkjkhjkhj |
| − | | + | :3. cdscdscdsacsa |
| − | ==QoS for Gaming on Client Side==
| + | :4. ewrtrewtrewtrewt435t54 |
| − | | + | :4.1 kjcksdlkjvckds |
| − | ===Wireless Interface Config===
| + | :5. ncknwlknlkewc |
| − | WMM Needs to be enabled on your Wireless interfaces. This allows the traffic to be prioritised on a wireless level.
| + | :6. cwdkjcwlkmclkw |
| | | | |
| − | :1. Click Wireless
| + | ===heading other=== |
| − | :2. Open the configuration of the wireless interface (wlanX if you've got the default names)
| + | okcjmlkmas |
| − | :3. Go to the Wireless Tab
| + | asclksalkjcsa |
| − | :4. Look for the WMM Support option
| + | acdsaklcjlksamc |
| − | :4.1 If you dont have WMM Support listed, click on the Advanced Setup button on the right
| |
| − | :5. Set WMM Support to enabled
| |
| − | :6. Click okay
| |
| | | | |
| − | ===Mangle Rules===
| + | dksajmcxlksakc: |
| − | Mikrotik Firewall Mangle (ROS3.x)
| + | :1. y,kjyumytm |
| − | These rules will NOT working on 2.9.x versions of RouterOS
| + | :2. yumytmytm |
| | | | |
| − | How to apply the new rules:
| + | Moet asb nie die page delete nie, ek is besig met die ding. |
| − | :1. Open Winbox
| |
| − | :2. Connect to your Mikrotik Router
| |
| − | :3. Go to IP > Firewall
| |
| − | :4. Select the mangle tab
| |
| − | :5. If you have old rules in there from the previous QoS scripts, delete them
| |
| − | :6. Open a New Terminal (Its in the menu on the left)
| |
| − | :7. Copy everything in the box below
| |
| − | :8. Paste into Terminal (right click, and paste)
| |
Admin Projects is projects and things to do that was either identified by the Committee members, Admin or users.
