Jami stopped working in a fully decentralized "Local DHT + Yggdrasil bootstrap" mode after the latest updates

Hello,
For some time now, I have been using Jami in a fully decentralized configuration, without any dependence on the jami.net infrastructure.
After the last two or three updates to Jami (Android), this configuration stopped working, even though it had been fully functional before.
Below, I describe the idea, how to set it up, and what exactly stopped working.

What is my goal

My goal is to use Jami without any centralized components whatsoever, including:

no registration at jami.net

no bootstrap nodes from jami.net

no DHT proxy

no TURN/STUN servers

no UnifiedPush

only direct p2p communication via OpenDHT

all traffic on Yggdrasil (global IPv6 overlay network)

Before the update, this worked perfectly fine.

Network architecture

I use Yggdrasil on all devices (Android and computer).

One device at home (phone or Linux machine) acts as the only bootstrap node for all Jami clients.

Jami is configured to join DHT only through this Yggdrasil IPv6 address:

[]:4222

No other bootstrap nodes have been added.

DHT proxy list is disabled.

TURN/STUN are disabled.

UPnP is optional.

Connectivity mode is Local DHT node (not UnifiedPush).

Local discovery has no effect because Yggdrasil is a separate network.

1 Like