Difference between revisions of "Mesh/Bandwidth Quotas"
Jump to navigation
Jump to search
(Created page with "See Also: Technical Documentation, Monitoring notes about bandwidth monitoring and quotas The goal is to find a way...") |
|||
| Line 1: | Line 1: | ||
See Also: [[Mesh#Technical_Documentation | Technical Documentation]], [[Mesh/ | See Also: [[Mesh#Technical_Documentation | Technical Documentation]], [[Mesh/Monitoring | Monitoring]] | ||
notes about bandwidth monitoring and quotas | notes about bandwidth monitoring and quotas | ||
Revision as of 23:53, 19 February 2015
See Also: Technical Documentation, Monitoring
notes about bandwidth monitoring and quotas
The goal is to find a way to cap bandwidth usage, in and out. The system can apportion the shareable bandwidth to a percentage of total bandwidth available. Here we research how this can be done.
tc − show / manipulate traffic control settings
Tc is used to configure Traffic Control in the Linux kernel.
- man page for tc: http://man.cx/tc
- Ixgr's setup using tc to fix bufferfloat: http://blog.lxgr.net/posts/2013/01/28/my-openwrt-setup/
monitoring
to track bandwidth we need a way to quantify it. Here are some likely candidates:
- bandwidthd - very popular, but apparently it is resource heavy
- bmon - download it
- iftop, man page - "iftop does for network usage what top(1) does for CPU usage. It listens to network traffic on a named interface and displays a table of current bandwidth usage by pairs of hosts."
ubus
OpenWrt micro bus architecture - there is a Lua module for ubus...