Echt Dezentrales Netz/ TestInfrastructure: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Demos (Diskussion | Beiträge) |
Demos (Diskussion | Beiträge) |
||
(14 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
Zeile 1: | Zeile 1: | ||
== Hardware == | |||
# Which hardware do we want to integrate? ( | # Which hardware do we want to integrate? (Routers, Rasberri Pis, Smartphones, Laptops, Redlight transmitter, self built antennas, ukw sender/receiver, satellite uplink, Wifi enabled TVs also known as "Smart"TVs, [?]) | ||
# Which extra hardware is required? | #*precondition: hardware must support ad hoc mode (for the mesh) and/or(?) offer an AccessPoint (for Client Net) | ||
# Which extra hardware is required? (wether resistant cases, cables, adapter, power supply) | |||
#* What are the costs for the required parts? | #* What are the costs for the required parts? | ||
#* For which hardware do we want to test EDN? | #* For which hardware do we want to test EDN? | ||
Zeile 12: | Zeile 13: | ||
** Banana Pi Board 1GB RAM, Gigabit Ethernet, ARMv7 Processor, 40€ ohne Extras wie Hülle, Stromversorgungskabel, externer Datenträger | ** Banana Pi Board 1GB RAM, Gigabit Ethernet, ARMv7 Processor, 40€ ohne Extras wie Hülle, Stromversorgungskabel, externer Datenträger | ||
== Software == | |||
# Which | #'' Which Operating System do we want to put on the different hardware?'': '''Openwrt''' ([http://wiki.openwrt.org/toh/start start], [http://wiki.openwrt.org/doc/howto/build build],[http://battlemesh.org/BattleMeshV7/Agenda?action=AttachFile&do=get&target=2014-05-17_wbmv7_DFS.pdf support of 5 GHz on DFS channels by openwrt]), dd-wrt, tomato, CyanogenMod, Replicant, Debian, [http://gluon.readthedocs.org/en/v2014.3/ Gluon](openwrt-based Freifunk Firmware) | ||
#'' 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?'' | |||
# What exactly do we want to test? | #* '''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: | ||
# Which Tools could be useful for testing? | #** The deployment of a testbed without ethernet cables | ||
#* [https://github.com/openwrt/luci '''Luci'''] (web | #** 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'''] (OpenWrt Configuration (web)Interface) | |||
#* [http://aircrack-ng.org/ '''Aircrack''' ]("In fact, Aircrack-ng is a set of tools for auditing wireless networks.") | #* [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'''] | #* [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) | # ''How to manage the test infrastructure?(updating, setting parameters)'' | ||
#* Under which criteria do we put the management of the testing infrastructure? | #* that could also include secure updating which is a criteria of our system | ||
# ''Under which criteria do we put the management of the testing infrastructure?'' | |||
#'' Which projects do we want to include?'' * CJDNS, GNUnet, BALL, Freenet....<br>-> limitation by ressources, starting with sequential testing according to the project's status, assistance by developers extremely helpful<br> | |||
# ''What does '''BattleMesh''' already test by which means?'' | |||
* http://battlemesh.org/BattleMeshV7/Tests | |||
* http://battlemesh.org/BattleMeshV6/ActualTests | |||
* http://downloads.battlemesh.org/WBMv6/test_data/ | |||
* http://battlemesh.org/BattleMeshV3.1416/SpeedTest | |||
== Testing Objectives == | |||
Which of these [https://wiki.c3d2.de/Echt_Dezentrales_Netz/en#Primary_Criteria criteria] are measurable? | Which of these [https://wiki.c3d2.de/Echt_Dezentrales_Netz/en#Primary_Criteria criteria] are measurable? | ||
Zeile 43: | Zeile 48: | ||
# '''Pentesting''' (anonymity, encryption, ...see [https://wiki.c3d2.de/Echt_Dezentrales_Netz/AttackScenarios attack scenarios]) | # '''Pentesting''' (anonymity, encryption, ...see [https://wiki.c3d2.de/Echt_Dezentrales_Netz/AttackScenarios attack scenarios]) | ||
# '''Usability''' of the Gui(s) | # '''Usability''' of the Gui(s) | ||
# Proving that the implementation covers the formal specifications | |||
# Testing of all components (unit test) | |||
# Testing of the overall system (audit) |
Aktuelle Version vom 15. März 2015, 10:09 Uhr
Hardware
- Which hardware do we want to integrate? (Routers, Rasberri Pis, Smartphones, Laptops, Redlight transmitter, self built antennas, ukw sender/receiver, satellite uplink, Wifi enabled TVs also known as "Smart"TVs, [?])
- precondition: hardware must support ad hoc mode (for the mesh) and/or(?) offer an AccessPoint (for Client Net)
- Which extra hardware is required? (wether resistant cases, cables, adapter, power supply)
- What are the costs for the required parts?
- For which hardware do we want to test EDN?
that has been found so far:
- openwrt supported Open Hardware Router: Linksys WRT54G, 4MB Flash, 16MB RAM, akutell Neukauf: 42€
- openwrt supported Raspberry Pis sind A,B (Ethernet 10/100) und B+ (ca. 30€ + 10€ Hülle) mit 256-512 MB RAM,CPU 700Mhz keinen Flashspeicher, Raspberry Pi 2 ist noch nicht bekannt, ob openwrt-fähig, bietet mehr Leistung zu gleichem Preis. 900MHz quad-core ARM Cortex-A7 CPU supported by 1GB LPDDR2 SDRAM
- Banana Pi Board 1GB RAM, Gigabit Ethernet, ARMv7 Processor, 40€ ohne Extras wie Hülle, Stromversorgungskabel, externer Datenträger
Software
- Which Operating System do we want to put on the different hardware?: Openwrt (start, build,support of 5 GHz on DFS channels by openwrt), dd-wrt, tomato, CyanogenMod, Replicant, Debian, Gluon(openwrt-based Freifunk Firmware)
- 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 (github, project confine, pdf)
"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)
- Luci (OpenWrt Configuration (web)Interface)
- Aircrack ("In fact, Aircrack-ng is a set of tools for auditing wireless networks.")
- Json
- ?
- Wibed (github, project confine, pdf)
- Where do we want to test?
- How to manage the test infrastructure?(updating, setting parameters)
- that could also include secure updating which is a criteria of our system
- Under which criteria do we put the management of the testing infrastructure?
- 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?
- http://battlemesh.org/BattleMeshV7/Tests
- http://battlemesh.org/BattleMeshV6/ActualTests
- http://downloads.battlemesh.org/WBMv6/test_data/
- http://battlemesh.org/BattleMeshV3.1416/SpeedTest
Testing Objectives
Which of these criteria are measurable?
- Performance
- Several Routing protocols for messaging.
- ... for telephone
- ?
- Pentesting (anonymity, encryption, ...see attack scenarios)
- Usability of the Gui(s)
- Proving that the implementation covers the formal specifications
- Testing of all components (unit test)
- Testing of the overall system (audit)