Echt Dezentrales Netz/ TestInfrastructure: Unterschied zwischen den Versionen

Aus C3D2
Zur Navigation springen Zur Suche springen
Zeile 16: Zeile 16:
#* '''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]
#* '''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?''
#'' How many nodes do we want to install at least to have a realistic test field?''
# What exactly do we want to test?
# ''What exactly do we want to test?''
#'' Which Tools could be useful for testing?''
#'' 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>
#* '''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
** The deployment of a testbed without ethernet cables
* Use very cheap commodity hardware (AR71xx recomended such as TL-4300)
** Use very cheap commodity hardware (AR71xx recomended such as TL-4300)
* Perform experiments and manage the nodes from a central controller
**Perform experiments and manage the nodes from a central controller
* Perform multiple experiments in paralel"(citation from github repository)
** Perform multiple experiments in paralel"(citation from github repository)
#* [https://github.com/openwrt/luci '''Luci'''] (web interface)
#* [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.")
#* [http://aircrack-ng.org/ '''Aircrack''' ]("In fact, Aircrack-ng is a set of tools for auditing wireless networks.")
Zeile 28: Zeile 28:
#* '''?'''
#* '''?'''
#'' 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?
# ''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....<br>-> limitation by ressources, starting with sequential testing according to the project's status, assistance by developers extremely helpful<br>
#* CJDNS, GNUnet, BALL, Freenet....
# ''What does '''BattleMesh''' already test by which means?''
-> 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/BattleMeshV7/Tests
* http://battlemesh.org/BattleMeshV6/ActualTests
* http://battlemesh.org/BattleMeshV6/ActualTests

Version vom 15. März 2015, 08:56 Uhr

Hardware

  1. 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, [?])
  2. 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

  1. Which OSs and Systems do we want to put on the hardware?
    • Openwrt (start, build), dd-wrt, tomato, CyanogenMod, Replicant, Debian, Gluon(openwrt-based Freifunk Firmware)
      OpenWRT/linux-wireless support for running adhoc mode on DFS channels in 5GHz by Simon Wunderlich
  2. How many nodes do we want to install at least to have a realistic test field?
  3. What exactly do we want to test?
  4. 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 (web interface)
    • Aircrack ("In fact, Aircrack-ng is a set of tools for auditing wireless networks.")
    • Json
    • ?
  2. Where do we want to test?
  3. How to manage the test infrastructure?(updating, setting parameters)
  4. Under which criteria do we put the management of the testing infrastructure?
  5. 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
  6. What does BattleMesh already test by which means?

Testing Objectives

Which of these criteria are measurable?

  1. Performance
    • Several Routing protocols for messaging.
    • ... for telephone
  2. ?
  3. Pentesting (anonymity, encryption, ...see attack scenarios)
  4. Usability of the Gui(s)
  5. Proving that the implementation covers the formal specifications
  6. Testing of all components (unit test)
  7. Testing of the overall system (audit)
Abgerufen von „https://wiki.c3d2.de/w/index.php?title=Echt_Dezentrales_Netz/_TestInfrastructure&oldid=20601“