---

Configuration areas options ¶

Multicast areas areas configuration only used with multicast packets.

areas: {
  nodelist: {
    id: OU67K7NA3RPOPFKJWNVBYJ5GPLRBDGHH6DZSSJ32JL7Q3Q76E52A

    pub: ALCX2NJBANMBNFTQ27C3C6W2WJIXSE74R27TSYZQKMD2UJERCEOQ
    prv: VQ3B4TLAZZB2G7RS3OSS5NUVKAS44OGY5YMQPMTAHQMZZLNG25MA

    subs: ["alice", "bob", "eve"]
    incoming: /home/incoming/areas/nodelist
  }
  echoarea: {
    id: CKKJ3HOAVOP7VPNCEGZRNDO34MUOOJ4AXHDFCSVSOE647KN5CMIA

    pub: 5MFPTJI2R322EUCTGCWZXTDBCVEL5NCFDBXI5PHPQOTLUVSQ3ZIQ
    prv: LVGIZQRQTDE524KEE5FOWLE2GCQBILY4VSQBDHWJC6YUTOJ54QCQ

    subs: ["alice", "bob"]
    exec: {sendmail: ["/usr/sbin/sendmail"]}
    allow-unknown: true
  }
  whatever.pvt: {
    id: OU67K7NA3RPOPFKJWNVBYJ5GPLRBDGHH6DZSSJ32JL7Q3Q76E52A
    subs: ["dave", "eve"]
  }
}

Each key is human readable multicast group/area/echo name.

The only required field is the id. You can not process multicast packets that has unknown area identification.

subs contains a list of recipients you must relay incoming multicast packet on.

Knowledge of pub and prv keys gives ability to decrypt multicast packet and process its contents (file or exec transmission). For accepting file transmissions you must set incoming, similar to neigh’s node option. For accepting exec transmissions you must set exec, similar to neigh’s node option.

You can accept multicast packets from unknown senders, by setting allow-unknown option.

In the example above:

nodelist

That area is for multicast sending of nodelist files, with relaying it to alice, bob and eve further.

echoarea

That area is for multicast discussion through sendmail handled exec packets. Relaying to alice and bob and accepting messages from unknown participants.

whatever.pvt

We just relay that area packets to dave and eve, but without ability to see what is inside them. Pay attention that allow-unknown does not play any role here, because we are not even trying to decrypt (and authenticate) those multicast packets.