Echt Dezentrales Netz/ TestInfrastructure
Zur Navigation springen
Zur Suche springen
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, [?])
- 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 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
- Openwrt (start, build), 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:
- Wibed (github, project confine, pdf)
- 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)
- 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? * 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)