IT-Syndikat/its-ap-builder
14
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
Automated build of OpenWrt based firmware
9 commits 1 branch 7 tags 190 KiB
Shell 85.6%
Makefile 14.4%
Find a file
Daniel Gröber bee056f4cd unifiac: Change 5Ghz channel to 48 
108 is a DFS channel which is annoying and probably broken. For 80Mhz bandwidth
you have to specify the upper channel apparently so 48-36 should be fine.
2018-05-06 21:00:47 +02:00
control Add support for Ubiquity Unifi AC LITE 2018-04-14 00:37:10 +02:00
files unifiac: Change 5Ghz channel to 48 2018-05-06 21:00:47 +02:00
images aps: Release v0.20180414 2018-04-14 01:26:55 +02:00
.gitignore Automate access-point image build 2017-10-04 22:33:53 +02:00
build-image.sh Append profile name to image-manifest 2018-04-14 01:00:40 +02:00
doc-ap-reinstall.txt Automate access-point image build 2017-10-04 22:33:53 +02:00
doc-ap-reset.txt Automate access-point image build 2017-10-04 22:33:53 +02:00
Makefile aps: Add Makefile for sequencing multiple profiles 2018-04-14 01:27:50 +02:00
README.md Add READMEs 2018-04-14 01:43:37 +02:00

README.md

ITS WiFi Access Points Setup

We build the access points in use at the space using the LEDE/OpenWrt image builder. The deployed images are completely hands-off no configuration of the running firmware should be necessary as all the device specific setup is done using /etc/uci-defaults/ by keying off the MAC address.

See files/common/its/etc/uci-defaults/50-config-from-mac for details.

Building Images

To build the its images, run:

$ make its

the resulting images land in images/v0.$(date +'%Y%m%d'). The build system also produces a *.image-manifest file which contains the URL to the ImageBuilder used as well its hash and the corresponding image's hash.

Using Released Binaries

The offically released and deployed images are added to the repo using git annex since this will not actually add the files to git but rather just a symlink containing its hash. The actual binary images can then be uploaded to an internal server.

We also use git-annex to add secrets to the repo which will then only be available to authorized people using the internal git-annex store. For an example, see files/common/its/etc/uci-defaults/51-secrets. This file just sets up secrets, such as the WiFi/root password.