X-Git-Url: http://www.project-moonshot.org/gitweb/?p=devwiki.git;a=blobdiff_plain;f=trustrouterinfo.mdwn;fp=trustrouterinfo.mdwn;h=c1e0da708a10122d1b6a7bfbdf3f13027264b1da;hp=93938fb4799db6a20352dc42fc74c89395d7dca7;hb=9a33216d570d8afe222b3e5dbe6cf2db0259de2f;hpb=e665fd44567569678f3b88cfcb84e8360d5b8679
diff --git a/trustrouterinfo.mdwn b/trustrouterinfo.mdwn
index 93938fb..c1e0da7 100644
--- a/trustrouterinfo.mdwn
+++ b/trustrouterinfo.mdwn
@@ -8,14 +8,14 @@ git clone --recursive git://git.project-moonshot.org/moonshot.git
The Trust Router depends on MIT Kerberos, OpenSSL, jansson and SQLite Version 3. The dependencies for freeradius are discussed in the freeradius documentation.
-To build and install a Trust Router, you need to separately 'make' and 'make install' in both the moonshot/trust_router and moonshot/freeradius-server directories, in that order.
+To build and install a Trust Router, you need to separately 'make' and 'make install' in both the moonshot/trust_router and moonshot/freeradius-server directories, in that order. The Moonshot Debian repositories include a moonshot-trust-router package and a freeradius package with Trust Router integration. The Centos repository includes trust router packages but not Freeradius packages.
CONFIGURING A TRUST ROUTER
In addition to having a valid freeradius TLS/PSK configuration, a set of Trust Router and TID-specific configuration is required in order to use the Trust Router.
The Trust Router reads its configuration from a set of JSON configuration files (anything with a .cfg file extension) in the directory from which it is run. These files can be generated by the
-Moonshot Management Portal or configured by hand.
+Moonshot Management Portal or configured by hand. An example is found in the tr/portal.cfg and tr/manual.cfg files in the trust_router sources. Both files are needed.
The TIDC also requires specific configuration in the freeradius raddb/mods-available/realm configuration file. Three new parameters have been added to the realm configuration: a default community (default_community), an RP realm (rp_realm) and a trust router (trust_router). The default community will be used when no community is specified in a AAA request (over-riding on a per-request basis is TBD). The RP realm is used in all TID requests from this proxy, and the trust_router is the IP address to which those requests will be sent.
@@ -29,6 +29,8 @@ realm suffix {
trust_router = "10.0.2.15"
}
+In addition, the Freeradius RP will need credentials with which to access the trust router. These credentials can be installed using the moonshot-webp command run as the same user freeradius runs as. On debian, this is "freerad".
+
BRINGING UP/VERIFYING A TRUST ROUTER
To run all of the components needed to test the Trust Router, you will need to have at least two different nodes (or VMs) at different IP addresses.