3 @section Configuration areas options
5 @ref{Multicast} areas configuration only used with multicast packets.
10 id: OU67K7NA3RPOPFKJWNVBYJ5GPLRBDGHH6DZSSJ32JL7Q3Q76E52A
12 pub: ALCX2NJBANMBNFTQ27C3C6W2WJIXSE74R27TSYZQKMD2UJERCEOQ
13 prv: VQ3B4TLAZZB2G7RS3OSS5NUVKAS44OGY5YMQPMTAHQMZZLNG25MA
15 subs: ["alice", "bob", "eve"]
16 incoming: /home/incoming/areas/nodelist
19 id: CKKJ3HOAVOP7VPNCEGZRNDO34MUOOJ4AXHDFCSVSOE647KN5CMIA
21 pub: 5MFPTJI2R322EUCTGCWZXTDBCVEL5NCFDBXI5PHPQOTLUVSQ3ZIQ
22 prv: LVGIZQRQTDE524KEE5FOWLE2GCQBILY4VSQBDHWJC6YUTOJ54QCQ
24 subs: ["alice", "bob"]
25 exec: {sendmail: ["/usr/sbin/sendmail"]}
29 id: OU67K7NA3RPOPFKJWNVBYJ5GPLRBDGHH6DZSSJ32JL7Q3Q76E52A
35 Each key is human readable multicast group/area/echo name.
37 The only required field is the @code{id}. You can not process multicast
38 packets that has unknown area identification.
41 @code{subs} contains a list of recipients you must relay incoming
44 Knowledge of @code{pub} and @code{prv} keys gives ability to decrypt
45 multicast packet and process its contents (file or exec transmission).
46 For accepting file transmissions you must set @code{incoming}, similar
47 to @ref{CfgIncoming, neigh's node option}. For accepting exec
48 transmissions you must set @code{exec}, similar to @ref{CfgExec, neigh's
51 You can accept multicast packets from unknown senders, by setting
52 @code{allow-unknown} option.
58 That area is for multicast sending of @file{nodelist} files, with
59 relaying it to @code{alice}, @code{bob} and @code{eve} further.
61 That area is for multicast discussion through @code{sendmail} handled
62 exec packets. Relaying to @code{alice} and @code{bob} and accepting
63 messages from unknown participants.
65 We just relay that area packets to @code{dave} and @code{eve}, but
66 without ability to see what is inside them. Pay attention that
67 @code{allow-unknown} does not play any role here, because we are not
68 even trying to decrypt (and authenticate) those multicast packets.