2014-03-31 23:18:29 +02:00
|
|
|
# Freifunk Gateway Module
|
|
|
|
|
|
|
|
Martin Schütte <info@mschuette.name>
|
|
|
|
|
|
|
|
This module tries to automate the configuration of a Freifunk (Hamburg) Gateway.
|
2014-04-01 00:31:06 +02:00
|
|
|
The idea is to implement the step-by-step guide on http://wiki.freifunk.net/Freifunk_Hamburg/Gateway
|
2014-03-31 23:18:29 +02:00
|
|
|
|
2014-04-01 00:31:06 +02:00
|
|
|
A generalization for other communities would be nice, but right now this is all
|
|
|
|
experimental and we will be glad when it works for our own gateways.
|
|
|
|
|
|
|
|
Also note that this is a really ugly puppet module that ignores all principles
|
|
|
|
of modularity and interoperability; instead it follows the "Big ball of mud"
|
|
|
|
design pattern.
|
|
|
|
|
2014-05-19 20:15:21 +02:00
|
|
|
## Open Problems
|
|
|
|
|
|
|
|
* The apt repository at http://bird.network.cz/debian/ does not use PGP
|
|
|
|
signatures, so `bird` and `bird6` will not be installed automatically.
|
|
|
|
* Setting the hostname should occur before everything else. So either
|
|
|
|
do that manually or run a small `ff_gw::sysadmin`-only manifest before the
|
|
|
|
main `ff_gw` manifest.
|
|
|
|
* User root requires ssh access to the git repository
|
|
|
|
`git@freifunk-gw01.hamburg.ccc.de:fastdkeys` --
|
|
|
|
so create a key and have it authorized beforehand.
|
|
|
|
|
2014-04-01 00:31:06 +02:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
Install as a puppet module, then include with node-specific parameters.
|
|
|
|
|
2014-04-23 17:30:01 +02:00
|
|
|
### Dependencies
|
|
|
|
|
|
|
|
Install Puppet and some required modules with:
|
|
|
|
|
|
|
|
```
|
2014-05-18 22:03:57 +02:00
|
|
|
apt-get install puppet git
|
2014-04-23 17:30:01 +02:00
|
|
|
puppet module install puppetlabs-stdlib
|
|
|
|
puppet module install puppetlabs-apt
|
|
|
|
puppet module install puppetlabs-vcsrepo
|
|
|
|
puppet module install saz-sudo
|
|
|
|
puppet module install torrancew-account
|
|
|
|
```
|
|
|
|
|
|
|
|
Then add this module (which is not in the puppet forge, so it has to be
|
|
|
|
downloaded manually):
|
|
|
|
|
|
|
|
```
|
|
|
|
cd /etc/puppet/modules
|
|
|
|
git clone https://github.com/freifunkhamburg/puppet-ff_gw.git ff_gw
|
|
|
|
```
|
|
|
|
|
|
|
|
### Parameters
|
|
|
|
|
|
|
|
Now include the module in your manifest and provide all parameters.
|
2014-04-01 00:31:06 +02:00
|
|
|
Basically there are three kinds of parameters: user accounts (optional if you
|
|
|
|
do manual user management), network config (has to be in sync with the wiki
|
|
|
|
page), and credentials for fastd and openvpn.
|
|
|
|
|
2014-04-23 17:30:01 +02:00
|
|
|
|
|
|
|
Example puppet code (save e.g. as `/etc/puppet/gw.pp`):
|
2014-04-01 00:31:06 +02:00
|
|
|
|
2014-04-01 00:34:06 +02:00
|
|
|
```
|
2014-05-04 23:18:42 +02:00
|
|
|
|
|
|
|
class { 'ff_gw::sysadmin':
|
|
|
|
# both optional, used for FFHH monitoring:
|
|
|
|
zabbixserver => 'argos.mschuette.name',
|
|
|
|
muninserver => '78.47.49.236',
|
|
|
|
|
2014-05-18 20:59:41 +02:00
|
|
|
# optional, configure hostname and public IP
|
|
|
|
sethostname => 'gw12.hamburg.freifunk.net',
|
|
|
|
setip => '5.45.105.34',
|
|
|
|
|
2014-05-04 23:38:58 +02:00
|
|
|
# also optional, let puppet control user accounts:
|
2014-04-01 00:31:06 +02:00
|
|
|
accounts => {
|
|
|
|
mschuett => {
|
|
|
|
comment => 'Martin Schuette',
|
|
|
|
ssh_key => 'AAAAB3NzaC1yc2EAAAADAQABAAABAQC4qcAOjmLCv+DaF405K9/napCQCq8qJnTJtkbeQR+PGLHAR3kxXFh5rQXKp5n3IxEhZt4js7yin5EBmfCMv+CHYSndT4BGVDarjqIoM7RAKI8MyJUus0SOf5WsnAGamp97mCh8iWHg7v+emqYcF308FFkubKzFLdHjdLGZBCduClUvkyuuUc7vtkXZ3IkInXGkrN5hn388/lHsT1ewUva7j2fZmbVou8P2FHC4+azPInoyezwiIE6YrFKAyquDhuFRDir5QqlFaZpD6C8T+vEiqWRyqPxI7YVGBudh2oec5m99VTWkrPw7cOsC92ndLAgQ2MjxEeDhPh/Tgxly6flb',
|
|
|
|
groups => ['sudo', 'users'],
|
|
|
|
}
|
|
|
|
},
|
2014-05-04 23:38:58 +02:00
|
|
|
}
|
2014-04-01 00:31:06 +02:00
|
|
|
|
2014-05-04 23:38:58 +02:00
|
|
|
class { 'ff_gw':
|
2014-04-26 14:46:32 +02:00
|
|
|
# freifunk config
|
|
|
|
# the network assigned to the ff community
|
|
|
|
ff_net => '10.112.0.0/16',
|
|
|
|
# the network actually used in the mesh might be smaller than ff_net
|
|
|
|
ff_mesh_net => '10.112.0.0/18',
|
|
|
|
# as number for icvpn peering
|
|
|
|
ff_as => '65112',
|
|
|
|
|
2014-04-01 00:31:06 +02:00
|
|
|
# network config (example data for gw12)
|
|
|
|
mesh_mac => 'de:ad:be:ef:01:14',
|
|
|
|
gw_ipv4 => '10.112.30.1',
|
|
|
|
gw_ipv6 => 'fd51:2bb2:fd0d::501',
|
|
|
|
dhcprange_start => '10.112.30.2',
|
|
|
|
dhcprange_end => '10.112.31.254',
|
|
|
|
|
|
|
|
# secret credentials for fastd and vpn
|
|
|
|
secret_key => '...',
|
|
|
|
vpn_ca_crt => '-----BEGIN CERTIFICATE-----
|
|
|
|
MIIE ...
|
|
|
|
-----END CERTIFICATE-----',
|
|
|
|
vpn_usr_crt => '-----BEGIN CERTIFICATE-----
|
|
|
|
MIIE ...
|
|
|
|
-----END CERTIFICATE-----',
|
2014-05-04 23:48:36 +02:00
|
|
|
vpn_usr_key => '-----BEGIN PRIVATE KEY-----
|
2014-04-01 00:31:06 +02:00
|
|
|
MIIE ...
|
2014-05-04 23:48:36 +02:00
|
|
|
-----END PRIVATE KEY-----',
|
2014-04-01 00:31:06 +02:00
|
|
|
}
|
|
|
|
```
|
2014-04-01 00:34:06 +02:00
|
|
|
|
2014-04-23 17:30:01 +02:00
|
|
|
### Run Puppet
|
|
|
|
|
|
|
|
To apply the puppet manifest (e.g. saved as `gw.pp`) run:
|
|
|
|
|
|
|
|
```
|
|
|
|
puppet apply --verbose gw.pp
|
|
|
|
```
|
|
|
|
|
|
|
|
The verbose flag is optional and shows all changes.
|
|
|
|
To be even more catious you can also add the `--noop` flag to only show changes
|
|
|
|
but not apply them.
|
|
|
|
|