| | 1 | == [http://www.genericproxy.org Generic Proxy project] == |
| | 2 | The goal of the parallel [http://www.genericproxy.org/ Generic Proxy Project] is the development and implementation of a (prototype) device that provides internet proxy functionality to a (community) (wireless) network, supplementary equipped with a simple user (web) interface and management features for the network operator. The device should be a self contained and embedded board. If there are a limited number of gateways to the public internet, the bandwidth to the internet is proportionally limited and randomly distributed. Balancing the load over the available bandwidth will decrease congestion on the relatively small (wireless) backbone. The "Generic Proxy" appliance aims at resolving this issue in a flexible manner. Adding bandwidth and/or extra gateways to the network will become a manageable function of the network. |
| | 3 | |
| | 4 | The project is an initiative of Hogeschool Leiden and is sponsored by [http://www.nlnet.nl Stichting NLnet]. Project results and prototype equipment are donated to Stichting Wireless Leiden and all software developments are made available to the Open Source Community. |
| | 5 | |
| | 6 | The project started in July 2009. |
| | 7 | |
| | 8 | From the website we quote freely: |
| | 9 | === web interface === |
| | 10 | One of the features of the 'generic proxy' is a web interface for easy of administration. |
| | 11 | |
| | 12 | The functionality present in the 'generic proxy' appliance overlaps with existing applications such as [http://www.pfsense.org pfSense] and m0n0wall. These are distributed under the BSD open-source license. The implementation of the Generic Proxy appliance is based upon these proven concepts and techniques. |
| | 13 | Upon looking through the back end code of pfsense and monowall it was concluded that using these directly or adding to these would harm maintainability of the code in the long run. Both pfsense and monowall, albeit being working solutions, have not structured their code such that it is easy to remove from, or add to, the base functionality. |
| | 14 | |
| | 15 | With that in mind the decision has been made to merely use pfsense as a baseline on how to get specific tasks done, while attempting to set up a structured and easily maintained version. This is not intended to be a fork or competitor to pfsense or monowall, as only a subset of their features is implemented. But we do strive to set up the system so that the code can be re-used easily. |
| | 16 | |
| | 17 | For present status see the project website and FunctionalRequirements and WebInterface pages. |
| | 18 | |
