The Trust Router currently supports static peering. This means that the peer, or upstream, Trust Router, is statically defined in the peering configuration. Static peering currently only supports a hub-and-spoke model, of which tr.moonshot.ja.net
is the hub. We are working on dynamic peering, in which Trust Routers can dynamically build routes to other Trust Routers in the system.
The peering configuration is stored in peering.cfg
, which is placed next to main.cfg
in /etc/trust_router/conf.d/[instance]
An example static peering.cfg
is below:
peering.cfg
{ "default_servers":[ "tr1.moonshot.ja.net" ] }
Static peering
Static peering also has some performance implications that affect authentication performance. Please see Trust Router Static Peering Performance Statistics for more information.
This page is still being written. Check back soon...