Router Control - Revision history

Bigfoot65 at 00:09, 3 April 2014

2014-04-03T00:09:13Z

2010-11-18T02:03:04Z

Reverted edits by Acecydoxose (Talk) to last revision by Cpg

2010-11-17T21:59:56Z

2009-09-12T20:50:05Z

2009-09-12T20:49:26Z

2009-09-12T20:49:07Z

2009-09-12T20:32:35Z

2009-09-12T20:32:00Z

2009-07-13T00:19:25Z

2009-07-09T15:43:42Z

← Older revision		Revision as of 00:09, 3 April 2014
Line 1:		Line 1:
		+	'''NOTE:''' This is an Amahi 6 ONLY feature.
		+
	This feature allows control of supported routers and firewalls from the Amahi HDA Setup pages, under Setup -> Networking -> Firewall and Settings.		This feature allows control of supported routers and firewalls from the Amahi HDA Setup pages, under Setup -> Networking -> Firewall and Settings.

@@ Line 13: / Line 13: @@
 ** Filtering for Ports, IPs and MACs and URLs
->== Writing new Router Modules ==
+== Writing new Router Modules ==
 The modules directory is here:
@@ Line 23: / Line 23: @@
 Each module should provide the following ''class'' (not instance methods!) methods:
-* '''name''' &gt; String: returns the name of the module, typically the brand name of the models supported by this module, e.g. &quot;D-Link&quot;
+* '''name''' > String: returns the name of the module, typically the brand name of the models supported by this module, e.g. "D-Link"
-* '''models''' &gt; String Array: returns an array of names of models of routers supported.
+* '''models''' > String Array: returns an array of names of models of routers supported.
 * '''set_dmz'''(ip: String): set the DMZ to be the ''full'' IP provided. If none provided (nil or empty string), turn off the DMZ feature
 * '''write_rule'''(rule): writes a firewall rule (see below)
@@ Line 34: / Line 34: @@
 There is no support yet for custom admin and password settings in the UI yet to gain administrator permissions to control the router/fw. The default admin username and password for the router should be provided in the '''AUTH''' hash variable for the time being for the case of conventional routers.
 == Firewall Rules ==

@@ Line 13: / Line 13: @@
 ** Filtering for Ports, IPs and MACs and URLs
-== Writing new Router Modules ==
+>== Writing new Router Modules ==
 The modules directory is here:
@@ Line 23: / Line 23: @@
 Each module should provide the following ''class'' (not instance methods!) methods:
-* '''name''' > String: returns the name of the module, typically the brand name of the models supported by this module, e.g. "D-Link"
+* '''name''' &gt; String: returns the name of the module, typically the brand name of the models supported by this module, e.g. &quot;D-Link&quot;
-* '''models''' > String Array: returns an array of names of models of routers supported.
+* '''models''' &gt; String Array: returns an array of names of models of routers supported.
 * '''set_dmz'''(ip: String): set the DMZ to be the ''full'' IP provided. If none provided (nil or empty string), turn off the DMZ feature
 * '''write_rule'''(rule): writes a firewall rule (see below)
@@ Line 34: / Line 34: @@
 There is no support yet for custom admin and password settings in the UI yet to gain administrator permissions to control the router/fw. The default admin username and password for the router should be provided in the '''AUTH''' hash variable for the time being for the case of conventional routers.
 == Firewall Rules ==

@@ Line 72: / Line 72: @@
 A useful tool to discover exactly what URLs are being exercised on during development is [http://portswigger.net/suite/ Burp Suite]
-Quick HOWTO on how to use Burp Suite:
+Quick HOWTO on how to use Burp Suite to see what URLs and form parameters your router requires so that you can put them in your module:
 * start it with java -jar burpsuite_v1.2.01.jar or however you do it

@@ Line 77: / Line 77: @@
 * on burpsuite, go to the "alerts" tab and make sure the proxy is running on 8080
 * all it takes after the proxy is running to use is setup firefox or whatever to use localhost:8080 as the proxy
- * then go to the proxy tab, turn on intercept and you will be prompted to either forward or drop every request that firefox makes
+* then go to the proxy tab, turn on intercept and you will be prompted to either forward or drop every request that firefox makes
 * go to your router and set things up to turn on or off the settings you want to research for adding to your module
 * what i do is this: i leave intercept off until i am just about to hit the button to accept, then turn it on. and then take a look at the variables being sent

← Older revision		Revision as of 20:49, 12 September 2009
Line 70:		Line 70:
	== Tools ==		== Tools ==

−	A useful tool to discover exactly what URLs are being ~~excersized~~ on during development is [http://portswigger.net/suite/ Burp Suite]	+	A useful tool to discover exactly what URLs are being exercised on during development is [http://portswigger.net/suite/ Burp Suite]
		+
		+	Quick HOWTO on how to use Burp Suite:
		+
		+	* start it with java -jar burpsuite_v1.2.01.jar or however you do it
		+	* on burpsuite, go to the "alerts" tab and make sure the proxy is running on 8080
		+	* all it takes after the proxy is running to use is setup firefox or whatever to use localhost:8080 as the proxy
		+	* then go to the proxy tab, turn on intercept and you will be prompted to either forward or drop every request that firefox makes
		+	* go to your router and set things up to turn on or off the settings you want to research for adding to your module
		+	* what i do is this: i leave intercept off until i am just about to hit the button to accept, then turn it on. and then take a look at the variables being sent

← Older revision		Revision as of 20:32, 12 September 2009
Line 70:		Line 70:
	== Tools ==		== Tools ==

−	A useful tool to ~~know~~ what~~'s going~~ on during development is [http://portswigger.net/suite/ Burp Suite]	+	A useful tool to discover exactly what URLs are being excersized on during development is [http://portswigger.net/suite/ Burp Suite]

← Older revision		Revision as of 20:32, 12 September 2009
Line 67:		Line 67:
	* http://www.shorewall.net/		* http://www.shorewall.net/
	* IPTables, the default linux firewall		* IPTables, the default linux firewall
		+
		+	== Tools ==
		+
		+	A useful tool to know what's going on during development is [http://portswigger.net/suite/ Burp Suite]

@@ Line 21: / Line 21: @@
 see the example ruby files there (*.rb).
-Each module should provide the following class methods:
+Each module should provide the following ''class'' (not instance methods!) methods:
 * '''name''' > String: returns the name of the module, typically the brand name of the models supported by this module, e.g. "D-Link"

← Older revision		Revision as of 15:43, 9 July 2009
Line 52:		Line 52:

	the rest of the fields are populated according to the kind field.		the rest of the fields are populated according to the kind field.
		+
		+	== Target Firewalls ==
		+
		+	Ideally we would like to control at least the following routers:
		+
		+	* UPnP routers
		+	* D-Link
		+	* dd-wrt routers
		+	* open-wrt routers
		+
		+	And the following firewalls:
		+
		+	* http://www.pfsense.com/
		+	* http://www.shorewall.net/
		+	* IPTables, the default linux firewall