/* Software */

This commit is contained in:
Demos 2015-03-15 08:49:42 +00:00
parent ee7e2e7ab1
commit 25546b7b56
1 changed files with 11 additions and 13 deletions

View File

@ -12,26 +12,24 @@ that has been found so far:
** Banana Pi Board 1GB RAM, Gigabit Ethernet, ARMv7 Processor, 40€ ohne Extras wie Hülle, Stromversorgungskabel, externer Datenträger
== Software ==
# Which OSs and Systems do we want to put on the hardware?
#* '''Openwrt''' [http://wiki.openwrt.org/toh/start, http://wiki.openwrt.org/doc/howto/build], dd-wrt, tomato, CyanogenMod, Replicant, Debian, [http://gluon.readthedocs.org/en/v2014.3/ Gluon](openwrt-based Freifunk Firmware)
#** OpenWRT/linux-wireless support for running adhoc mode on DFS channels in 5GHz by [http://battlemesh.org/BattleMeshV7/Agenda?action=AttachFile&do=get&target=2014-05-17_wbmv7_DFS.pdf Simon Wunderlich]
''# How many nodes do we want to install at least to have a realistic test field?''
#'' Which OSs and Systems do we want to put on the hardware?''
#* '''Openwrt''' ([http://wiki.openwrt.org/toh/start start], [http://wiki.openwrt.org/doc/howto/build build]), dd-wrt, tomato, CyanogenMod, Replicant, Debian, [http://gluon.readthedocs.org/en/v2014.3/ Gluon](openwrt-based Freifunk Firmware)<br>OpenWRT/linux-wireless support for running adhoc mode on DFS channels in 5GHz by [http://battlemesh.org/BattleMeshV7/Agenda?action=AttachFile&do=get&target=2014-05-17_wbmv7_DFS.pdf Simon Wunderlich]
#'' How many nodes do we want to install at least to have a realistic test field?''
# What exactly do we want to test?
''# Which Tools could be useful for testing?''
#* '''Wibed''' [https://github.com/battlemesh/wibed,http://wiki.confine-project.eu/wibed:start, http://wiki.confine-project.eu/_media/wibed:wibed-7pages.pdf]<br>
"The Wireless testBed is a platform based on OpenWRT Linux to the easy and quick deployment of infrastructures to perform experiments (such as WiFi or routing). Among many other features WiBed allows:
#** The deployment of a testbed without ethernet cables
#** Use very cheap commodity hardware (AR71xx recomended such as TL-4300)
#** Perform experiments and manage the nodes from a central controller
#** Perform multiple experiments in paralel"(citation from github repository)
#'' Which Tools could be useful for testing?''
#* '''Wibed''' ([https://github.com/battlemesh/wibed github], [http://wiki.confine-project.eu/wibed:start project confine], [http://wiki.confine-project.eu/_media/wibed:wibed-7pages.pdf pdf])<br>"The Wireless testBed is a platform based on OpenWRT Linux to the easy and quick deployment of infrastructures to perform experiments (such as WiFi or routing). Among many other features WiBed allows:<br>
* The deployment of a testbed without ethernet cables
* Use very cheap commodity hardware (AR71xx recomended such as TL-4300)
* Perform experiments and manage the nodes from a central controller
* Perform multiple experiments in paralel"(citation from github repository)
#* [https://github.com/openwrt/luci '''Luci'''] (web interface)
#* [http://aircrack-ng.org/ '''Aircrack''' ]("In fact, Aircrack-ng is a set of tools for auditing wireless networks.")
#* [https://github.com/interop-dev/json-for-networks '''Json''']
#* '''?'''
''# Where do we want to test?''
#'' Where do we want to test?''
# How to manage the test infrastructure?(updating, setting parameters)
#* Under which criteria do we put the management of the testing infrastructure?
''# Which projects do we want to include?''
#'' Which projects do we want to include?''
#* CJDNS, GNUnet, BALL, Freenet....
-> limitation by ressources, starting with sequential testing according to the project's status, assistance by developers extremely helpful
#''What does '''BattleMesh''' already test by which means?''