# What topology should be generated by the helper functions GNUNET_TESTBED_run()
# and GNUNET_TESTBED_test_run(). This option has no effect if testbed is
# initialized with other functions. Valid values can be found at:
-# https://gnunet.org/content/supported-topologies
+# https://gnunet.org/supported-topologies
OVERLAY_TOPOLOGY = NONE
# Number of random links to be included to the generate the above topology.
# This option is required if the OVERLAY_TOPOLOGY is set to FROM_FILE. It is
# ignored for all other topologies. This option should contain the path to
# the file containing the topology information. The format of the file is
-# presented at: https://gnunet.org/content/topology-file-format
+# presented at: https://gnunet.org/topology-file-format
# OVERLAY_TOPOLOGY_FILE = /path/to/topology-file
# The following options are required if the OVERLAY_TOPOLOGY is set to
# Where should testbed write load statistics data
# STATS_DIR = /tmp/load
-# What services should be shared among peers.
+# What services should be shared among peers.
# Format is "[<service:share>] [<service:share>] ...". The shared services are
# started standalone without any other peer services or a hostkey. For this
# reason, only services which doesn't depend on other services can only be
# connectivity restrictions of NAT boxes
[testbed-underlay]
AUTOSTART = NO
+NOARMBIND = YES
BINARY = gnunet-daemon-testbed-underlay
# The sqlite3 database file containing information about what underlay
# restrictions to apply
-# DBFILE =
+# DBFILE =
[latency-logger]
AUTOSTART = NO
+NOARMBIND = YES
BINARY = gnunet-daemon-latency-logger
# The sqlite3 database file where the latency values are to be stored
-# DBFILE =
\ No newline at end of file
+# DBFILE =
\ No newline at end of file