chootka / subnodes Goto Github PK

Subnodes is an open source project that configures your Raspberry Pi as a wireless AP, Node.js server, and BATMAN ADV mesh point.

License: Other

JavaScript 23.93% CSS 5.78% HTML 4.32% Shell 65.96%

subnodes's Introduction

subnodes

Subnodes is an open source project that turns your Linux device running the latest Raspbian (as of this writing, Stretch Lite) into an offline mesh node and wireless access point.

This project is an initiative focused on streamlining the process of setting up a Raspberry Pi as a wireless access point for distributing content, media, and shared digital experiences. The device becomes a web server, creating its own local area network, and does not connect with the internet. This is key for the sake of offering a space where people can communicate anonymously and freely, as well as maximizing the portability of the network (no dependibility on an internet connection means the device can be taken and remain active anywhere).

The device can also be configured as a BATMAN Advanced mesh node, enabling it to join with other nearby BATMAN nodes into a greater mesh network, extending the access point range and making it possible to exchange information with each other. Support for Subnodes has been provided by Eyebeam. This code is published under the AGPLv3.

How to Install

Assuming you are starting with a fresh Raspbian Stretch Lite (Latest tested version: November 2017) install on your SD card, these are the steps for setting up subnodes on your Raspberry Pi. It is also assumed that you have two wireless USB adapters attached to your RPi. They both must be running the nl80211 driver. This guide will help you find a suitable radio. If you are running a Raspberry Pi 3 or Pi Zero W, you only need one additional radio for the mesh point. The access point will be set up utilizing the Pi's internal wireless radio.

Also, if this is your first time connecting to your Raspberry Pi headlessly (i.e. via SSH), you must first enable SSH by placing an empty file with no filename extension simple called ssh in the root of your SD card.

set up your Raspberry Pi with a basic configuration
```
  sudo raspi-config
```
update apt-get
```
  sudo apt-get update
```
install git
```
  sudo apt-get install git
```
clone the repository into your home folder (assuming /home/pi)
```
  git clone https://github.com/chootka/subnodes.git
```
configure your wireless access point and mesh network in subnodes.config in any text editor, or in the command line you can use nano
```
  nano subnodes.config
```
run the installation script
```
  cd subnodes
  sudo ./install.sh
```

The installation process takes about 15 minutes. After it has completed, you will have a running node.js web server, wireless access point, and BATMAN Advanced mesh node. Connecting to the network and navigating to a browser page will redirect you to http://www.subnodes.org, where a sample node.js chat client will be running.

From here, fork, build, share your ideas, and have fun!

references

subnodes's People

Contributors

Stargazers

Watchers

subnodes's Issues

README.md has wrong year

How to Install
Assuming you are starting with a fresh Raspbian Stretch Lite (Latest tested version: November 2018) install on your SD card,

Should be: November 2017

chat app does not load after install

settings are all good, set the AP SSID and could connect no problem, but the page does not load anything in browser.

I think this has something to do with node being installed at version 4.x.x and that it's too old to understand let variable definitions

unclear licensing

Hi Chootka,

i looked at your code and i miss a licensing statement. Under which terms are people allowed to use your code? I would suggest AGPLv3 so people have to open up their contributions. That would ensure solidarity and prevent exploitation of your work. As the copyright holder, you could license things under different conditions any time, if needed. If you have any questions regarding the licensing, i can offer you hints and advice.

Cheers,
tpltnt

Node.js 4.0.0 issue

Bit of a newbie here, but it seems that packages in the January version of Raspbian are having issues with the latest deployment of Node(4.0.0). In install.sh, you have on lines 76:

echo "Installing Node.js..."
wget http://node-arm.herokuapp.com/node_latest_armhf.deb
sudo dpkg -i node_latest_armhf.deb

Might be worth just switching latest to archive:

echo "Installing Node.js..."
wget http://node-arm.herokuapp.com/node_archive_armhf.deb
sudo dpkg -i node_archive_armhf.deb

for the 0.12.6 version.

Not sure how to approach this problem from the package end.

npm problems

Having little knowledge of npm...
This happens when I run the install script, and following your tutorial.

npm ERR! System Linux 3.18.7+
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/pi/www/subnodes
npm ERR! node -v v0.9.9
npm ERR! npm -v 1.2.10
npm ERR! path /home/pi/www/subnodes/node_modules/jade/node_modules/mkdirp/test/return_sync.js
npm ERR! code ENOENT
npm ERR! errno 34
npm http 200 https://registry.npmjs.org/promise
npm http 200 https://registry.npmjs.org/uglify-js
npm http 200 https://registry.npmjs.org/css
npm ERR! Error: No compatible version found: acorn-globals@'^1.0.3'
npm ERR! Valid install targets:
npm ERR! ["1.0.0","1.0.1","1.0.2","1.0.3","1.0.4"]
npm ERR! at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:676:10)
npm ERR! at /usr/local/lib/node_modules/npm/lib/cache.js:591:10
npm ERR! at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR! at Object.oncomplete (fs.js:93:15)
npm ERR! at process._makeCallback (node.js:318:24)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

sudo npm install -g nodemon
npm http GET https://registry.npmjs.org/nodemon
npm http 304 https://registry.npmjs.org/nodemon
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/ps-tree
npm http GET https://registry.npmjs.org/touch
npm http GET https://registry.npmjs.org/update-notifier
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/ps-tree
npm http 304 https://registry.npmjs.org/touch
npm http 304 https://registry.npmjs.org/update-notifier
npm ERR! Error: No compatible version found: update-notifier@'^0.3.0'
npm ERR! Valid install targets:
npm ERR! ["0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.1.8","0.1.9","0.1.10","0.2.0","0.2.1","0.2.2","0.3.0","0.3.1","0.3.2"]
npm ERR! at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:676:10)
npm ERR! at /usr/local/lib/node_modules/npm/lib/cache.js:591:10
npm ERR! at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR! at Object.oncomplete (fs.js:93:15)
npm ERR! at process._makeCallback (node.js:318:24)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

npm ERR! System Linux 3.18.7+
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "nodemon"
npm ERR! cwd /home/pi/www/subnodes
npm ERR! node -v v0.9.9
npm ERR! npm -v 1.2.10
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/www/subnodes/npm-debug.log
npm ERR! not ok code 0

Many thanks in advance.

No IP address assigned

using a Pi 2, and Jessie there are a couple of issues:

the node version is pretty out of date and currently breaks the node app
connected clients aren't issued IP addresses
the DNSMASq isn't getting requests from connected clients

Any ideas? I'll try it with wheezy now

Meshing with LibreMesh

Hey, I'm trying to use subnodes to mesh a Raspberry 3 using a TL-WN722N dongle to a router with a Libre Mesh firmware installed.

I'm not so familiar with how to get the information for the config file to setup subnodes.

# To-Do: Specify exact device you would like to use for mesh point
#MESH_PHY="phy2"

By using the lsusb command I get the usb devices, but none of the information looks like phy2. And since it has a To-Do, is this implemented?

Mesh Network and AP from the single built-in wifi (RaspberryPi 3) (?)

I was able to run the Raspberry Pi 3 as a Wifi client (station) and access point (ap) from the single built-in wifi. See this instruction: https://github.com/peebles/rpi3-wifi-station-ap-stretch

Do you think it is possible to use the single built in wifi for the ap and b.a.t.m.a.n. mesh network?
So the wlan0 would change from client network to the b.a.t.m.a.n. mesh network.

Perhaps it is possible to use the additional uap0 interface (which uses the same internal wifi):

/etc/udev/rules.d/90-wireless.rules

ACTION=="add", SUBSYSTEM=="ieee80211", KERNEL=="phy0", \
    RUN+="/sbin/iw phy %k interface add uap0 type __ap"

No DHCPOFFERS received

The installation appeared to go successfully (on a fully updated version of Weezy), but when I reboot I get the following messages:

Listening on LPF/eth0/b8:27:eb:82:ea:1d
Sending on LPF/eth0/b8:27:eb:82:ea:1d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received

I have two wireless adaptors plugged into the Pi, and they both work under normal circumstances. If I edit the interfaces file, and change 'eth0' to 'wlan0' then it will receive an IP address upon reboot, however I don't think it's working as a mesh node at this point.

Any ideas?

Installation process, possible node issue.

Hi. I am having an issue with the installation process of subnodes on my raspberry pi. It takes only a few minutes for that I am asked: "Do you wish to reboot now? [N]" and I am not prompted to name my mesh network at all. Can you kindly please help me with the issue I am having? Thank you.

This is the entire script that is shown in my terminal after running the installation script:

Checking that USB wifi radio is available for access point...[OK]
Checking that USB wifi radio is available for mesh point...[OK]
Updating apt-get and installing iw package for network interface configuration...
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
iw is already the newest version.
iw set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 233 not upgraded.

Loading the subnodes configuration file...
Installing latest Node.js for arm...
--2017-11-17 19:47:16-- http://node-arm.herokuapp.com/node_latest_armhf.deb
Resolving node-arm.herokuapp.com (node-arm.herokuapp.com)... 54.225.138.190, 54.225.121.197, 54.225.128.217, ...
Connecting to node-arm.herokuapp.com (node-arm.herokuapp.com)|54.225.138.190|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5617566 (5.4M) [application/x-debian-package]
Saving to: ‘node_latest_armhf.deb’

node_latest_armhf.d 100%[=====================>] 5.36M 2.97MB/s in 1.8s

2017-11-17 19:47:18 (2.97 MB/s) - ‘node_latest_armhf.deb’ saved [5617566/5617566]

Selecting previously unselected package node.
dpkg: regarding node_latest_armhf.deb containing node:
nodejs-legacy conflicts with node
node (version 4.2.1-1) is to be installed.
node provides node and is to be installed.

dpkg: error processing archive node_latest_armhf.deb (--install):
conflicting packages - not installing node
Errors were encountered while processing:
node_latest_armhf.deb

Installing chat room...
./install.sh: line 155: npm: command not found
./install.sh: line 156: npm: command not found
Synchronizing state for dhcpcd.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d dhcpcd defaults
Executing /usr/sbin/update-rc.d dhcpcd disable
insserv: warning: current start runlevel(s) (empty) of script dhcpcd' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script dhcpcd' overrides LSB defaults (0 1 6).
Synchronizing state for networking.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d networking defaults
Executing /usr/sbin/update-rc.d networking enable
�[3;J
Configuring Access Point...

Reading package lists... Donetl, hostapd and dnsmasq...
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
dns-root-data dnsmasq-base libmnl0 libnetfilter-conntrack3 libnl-route-3-200
The following NEW packages will be installed:
batctl bridge-utils dns-root-data dnsmasq dnsmasq-base hostapd libmnl0
libnetfilter-conntrack3 libnl-route-3-200
0 upgraded, 9 newly installed, 0 to remove and 233 not upgraded.
Need to get 1,096 kB of archives.
After this operation, 2,679 kB of additional disk space will be used.
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main libmnl0 armhf 1.0.3-5 [10.9 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian/ jessie/main libnetfilter-conntrack3 armhf 1.0.4-1 [40.0 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ jessie/main libnl-route-3-200 armhf 3.2.24-2 [99.5 kB]
Get:4 http://mirrordirector.raspbian.org/raspbian/ jessie/main bridge-utils armhf 1.5-9 [32.1 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian/ jessie/main dns-root-data all 2014060201+2 [14.9 kB]
Get:6 http://mirrordirector.raspbian.org/raspbian/ jessie/main dnsmasq-base armhf 2.72-3+deb8u2 [375 kB]
Get:7 http://mirrordirector.raspbian.org/raspbian/ jessie/main dnsmasq all 2.72-3+deb8u2 [15.8 kB]
Get:8 http://mirrordirector.raspbian.org/raspbian/ jessie/main hostapd armhf 1:2.3-1+deb8u5 [460 kB]
Get:9 http://mirrordirector.raspbian.org/raspbian/ jessie/main batctl armhf 2014.3.0-2 [48.6 kB]
Fetched 1,096 kB in 3s (312 kB/s)
Selecting previously unselected package libmnl0:armhf.
(Reading database ... 121961 files and directories currently installed.)
Preparing to unpack .../libmnl0_1.0.3-5_armhf.deb ...
Unpacking libmnl0:armhf (1.0.3-5) ...
Selecting previously unselected package libnetfilter-conntrack3:armhf.
Preparing to unpack .../libnetfilter-conntrack3_1.0.4-1_armhf.deb ...
Unpacking libnetfilter-conntrack3:armhf (1.0.4-1) ...
Selecting previously unselected package libnl-route-3-200:armhf.
Preparing to unpack .../libnl-route-3-200_3.2.24-2_armhf.deb ...
Unpacking libnl-route-3-200:armhf (3.2.24-2) ...
Selecting previously unselected package bridge-utils.
Preparing to unpack .../bridge-utils_1.5-9_armhf.deb ...
Unpacking bridge-utils (1.5-9) ...
Selecting previously unselected package dns-root-data.
Preparing to unpack .../dns-root-data_2014060201+2_all.deb ...
Unpacking dns-root-data (2014060201+2) ...
Selecting previously unselected package dnsmasq-base.
Preparing to unpack .../dnsmasq-base_2.72-3+deb8u2_armhf.deb ...
Unpacking dnsmasq-base (2.72-3+deb8u2) ...
Selecting previously unselected package dnsmasq.
Preparing to unpack .../dnsmasq_2.72-3+deb8u2_all.deb ...
Unpacking dnsmasq (2.72-3+deb8u2) ...
Selecting previously unselected package hostapd.
Preparing to unpack .../hostapd_1%3a2.3-1+deb8u5_armhf.deb ...
Unpacking hostapd (1:2.3-1+deb8u5) ...
Selecting previously unselected package batctl.
Preparing to unpack .../batctl_2014.3.0-2_armhf.deb ...
Unpacking batctl (2014.3.0-2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Processing triggers for systemd (215-17+deb8u5) ...
Setting up libmnl0:armhf (1.0.3-5) ...
Setting up libnetfilter-conntrack3:armhf (1.0.4-1) ...
Setting up libnl-route-3-200:armhf (3.2.24-2) ...
Setting up bridge-utils (1.5-9) ...
Setting up dns-root-data (2014060201+2) ...
Setting up dnsmasq-base (2.72-3+deb8u2) ...
Setting up dnsmasq (2.72-3+deb8u2) ...
Setting up hostapd (1:2.3-1+deb8u5) ...
Setting up batctl (2014.3.0-2) ...
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Processing triggers for systemd (215-17+deb8u5) ...
[OK]
Creating backup of network interfaces configuration file...[OK]
Creating default hostapd file...[OK]
�[3;J
Checking whether to configure mesh point or not...
�[3;J

Configuring Raspberry Pi as a BATMAN-ADV mesh point...

Enabling the batman-adv kernel module...
Creating dnsmasq configuration file...[OK]
Creating new network interfaces with your settings...[OK]
Creating hostapd.conf file...[OK]

Adding startup scripts to init.d...
�[3;J

Do you wish to reboot now? [N]

Unable to load Node.js chat client after installing Subnodes on Raspberry Pi 3B

Hi there. Not sure where I'm going wrong in my installation setup here, but I've been attempting to set up Subnodes on a Raspberry Pi 3B running Raspbian Stretch (not Lite), where I'm using the Pi's built in wifi-adapter (which I believe is wlan0), and an Adafruit wifi adapter (https://www.adafruit.com/product/814) as wlan1 (I believe this also has the correct driver). In the subnodes.config file, I commented out the last four lines under "# SET THE DHCP RANGE IF WE ARE ONLY SETTING UP AN AP", since I was trying to setup both an access point and a mesh.

Afterwards I ran the install script, and a network called submesh showed up on my laptop (but not on my Android phone, any idea why that might be?). I connected and tried to browse to http://www.subnodes.org and it would not load. Any ideas as to what I'm doing incorrectly? Thank you!