unfinished

README.md

+# Netlimiter
+
+Simulates different network conditions by shaping traffic to behave
+like 3G, bad conditions, slow connections, etc.
+
+## Installation
+
+### Bridge method (recommended)
+
+The recommended way to install is to use a dedicated physical machine
+with two bridged NICs. This way all traffic passing would be shaped
+without any client configuration. It is by far the easiest way to
+install and will have the highest throughput.
+
+### Gateway method (for VMs)
+
+Virtual interfaces + client gw
+
+This is the recommended way using a VM and is used when using Vagrant.
+
+    brctl addbr netlim
+    ip link set dev netlim up
+
+### HTTP proxy method
+
+For HTTP-only traffic it supports running as a proxy. Clients need to
+configure their browser to point to the netlimiter instance.
+
+## Vagrant
+
+For testing and/or developing you can use Vagrant, simply run:
+
+    brctl addbr netlim
+    ip link set dev netlim up
+    vagrant up
+
+Two VMs are created: `netlimiter-router` and `netlimiter-guest` where
+the former acts as the actual netlimiter instance and the latter runs
+a desktop environment (LXDE) with chromium.
+
+## Building
+
+    npm install
+    grunt build
+

js/.eslintrc.json

@@ -11,6 +11,7 @@
 		"angular/log": 1,
 		"angular/definedundefined": 1,
 		"angular/timeout-service": 1,
+		"angular/di-unused": 2,
 		"strict": [2]
 	}
 }

js/rules/rules.constants.js

+(function(){
+	'use strict';
+
+
+	angular
+		.module('netlimiter')
+		.const('RULES_LIST_ENDPOINT', '/api/v1/rules')
+	;
+
+})();

js/rules/rules.service.js

+(function(){
+	'use strict';
+
+	angular
+		.module('netlimiter')
+		.factory('Rules', rules)
+	;
+
+	rules.$inject = ['$http', 'RULES_LIST_ENDPOINT'];
+	function rules($http, RULES_LIST_ENDPOINT){
+		return {
+			list: list,
+		};
+
+		function list(){
+			return $http.get(RULES_LIST_ENDPOINT);
+		}
+	}
+
+})();