v0.47.0

Two nodes under one callsign now work

DAPPS treats the SSID as part of a node's identity everywhere, as the docs always said. G6FCI-7 and G6FCI-8 are two stations, not one.

• Messages between two SSIDs of one callsign are delivered. Before, a node took mail for another SSID of its own callsign as its own: it sat in its local inbox as "awaiting ack" and never left (#239).
• Routing keeps one route per callsign and SSID. The routes exchange between nodes now carries the full callsign, and learned routes and discovered paths are stored per station. Two SSIDs of one callsign behind a relay can now reach each other (#242).
• The Neighbours panel marks a neighbour that may have the wrong SSID ("SSID?").

Upgrading

• Every node should upgrade. Mixed versions still exchange mail. Routing only improves once both ends have upgraded, and in the meantime routes from a node that hasn't upgraded stop covering stations with an SSID.
• No configuration changes. Neighbours and route hints work as they are. A route hint with no SSID still covers every SSID of that callsign. A hint written with an SSID, which never matched anything before, now routes that station.
• Learned routes start afresh after the upgrade and relearn on their own. Downgrading to 0.46 is safe; routes simply relearn again.
• A neighbour entered without its SSID still works locally, but is now advertised to other nodes as SSID 0. Correct the SSID if the panel marks it.

Known issues

• BPQ changes the SSID of a call made through it to 15 minus the SSID, so G6FCI-8 arrives as G6FCI-7. If you run two DAPPS SSIDs of one callsign and calls pass through BPQ nodes, avoid SSID pairs that add up to 15.
• Route gossip from older nodes covers SSID 0 only until they upgrade.