From k-space wiki
Revision as of 07:12, 6 September 2018 by Lauri (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Using existing equipment build surveillance system capable of detecting potentially anomalious events based on wireless traffic and video feeds.

Hardware provided by the hackerspace:

  • 6pcs 120degree FullHD dome cameras with IR lights, AR0330 chipset, USB interface
  • 2pcs+ TP-Link Archer C7 v2, has two USB ports suitable for connecting cameras whilst creating wireless coverage
  • 6pcs+ GL iNet routers with built-in PoE splitter, has USB port suitable for connecting cameras
  • PoE switch
  • Server or virtual machine for collecting events

General plan:

  • [done] Deploy LEDE on Archer and GL iNet devices, create reusable site-specific script for /etc/uci-defaults/
  • [done] Configure motion on Archer or GL iNet to detect events, or configure mjpg-streamer to provide the stream and motion on a central server to detect and store events
  • Use syslog to aggregate events to a central server
  • Use SEC to find anomalious events
  • Rank events by severity, submit some events to Slack channel, submit others via e-mail to staff


  • Configure hostapd to submit wireless associate/deassoc events to webapp, notify Slack channel if someone has entered/left the building. Add database tables to associate MAC addresses with hackerspace members.
  • Monitor wireless signals transmitted by devices which have never associated with any of our AP-s. Presumably needs dozen of wireless devices in montior mode. Yet again every decent hackerspace needs a WiFiCactus
  • Identify persons based on the video feed
  • Attempt to map user location based on the WiFi signal, based on RSSI and associated wireless AP presumably

Thesis ideas: research how many cybersecurity solutions actually interface with physical world, in this case video surveillance, wifi monitoring and other presence detection mechanisms. Can we improve

Supervisor: Lauri