| | 80 | Definition of the {{{bootstrap.hints}}} property is the same as the endpoints format but with some extensions. First, bootstrap hints are defined per SpoVNet instance, second, configuration of automatic bootstrap modules is available. |
| | 81 | |
| | 82 | You define the {{{bootstrap.hints}}} property using |
| | 83 | {{{ |
| | 84 | spovnet1{,,,};spovnet2{...}; |
| | 85 | }}} |
| | 86 | And insert the hints in the format same as the endpoints. The following defines a bootstrap hint the connect to port 5003 using tcp on the local machine: |
| | 87 | {{{ |
| | 88 | ariba.bootstrap.hints=pingpong{ip{127.0.0.1};tcp{5002}}; |
| | 89 | }}} |
| | 90 | |
| | 91 | Ariba provides several automatic bootstrapping modules: |
| | 92 | * A periodic broadcasting protocol using IPv4 and IPv6 - {{{broadcast}}} |
| | 93 | * Multicast DNS using the Avahi library - {{{mdns}}} |
| | 94 | * Bluetooth service discovery protocol - {{{sdp}}} |
| | 95 | |
| | 96 | All three search for bootstrapping information and allow to automatically connect to running SpoVNets. Note, that the bootstrapping mechanism is independent of the actual protocol used to join the SpoVNet. E.g. you can find a SpoVNet using SDP and then connect using IPv4 through the LAN. A bootstrap module is named using the {{{protocol{address}}}} naming. |
| | 97 | |
| | 98 | ariba.bootstrap.hints=pingpong{ip{127.0.0.1};tcp{5002};broadcast{x xx};sdp{30s} ; mdns{ asd }} |
| | 99 | |
