106 | | The configuration file can hold several parameters, the [wiki:Documentation/Configuration main documentation is here]. |
107 | | |
108 | | |
109 | | |
110 | | |
111 | | |
| 106 | The configuration file can hold several parameters, the [wiki:Documentation/Configuration main documentation is here]. To achieve the same effect as in the GUI use: |
| 107 | {{{ |
| 108 | ariba.endpoints = tcp{5003} |
| 109 | ariba.bootstrap.hints=mcpovlc{ip{127.0.0.1};tcp{5002}} |
| 110 | }}} |
| 111 | The first is the local server socket port, the second is the bootstrap information for the remote IP and port. Note, that you can only use hostnames in the GUI, the settings file requires IP addresses. In the settings you can use furthermore IPv6 addresses, RFCOMM, and automatic bootstrap modules. |
| 112 | |
| 113 | We currently have three automatic bootstrap modules that help to join the network without giving any IP/port information: |
| 114 | * broadcast - A periodic broadcasting protocol using IPv4 and IPv6 |
| 115 | * mdns - Multicast DNS using the Avahi library |
| 116 | * sdp - Bluetooth service discovery protocol |
| 117 | If you are running on a LAN, you can e.g. use the following in the settings |
| 118 | {{{ |
| 119 | ariba.bootstrap.hints=mcpovlc{bootstrap} |
| 120 | }}} |
| 121 | for running the automatic broadcast based bootstrapping module. Note, that a client does only broadcast its bootstrap information if the module is enabled, and can only receive the information if the module is enabled. Just using it on one machine does not make sense, you have to use it on multiple machines. |