Hello,
I have setup a JAMS instance that is running pretty well.
On the same server, I have also setup a TURN server that seems to be OK too.
I have also setup a DHT node on this server with :
docker run -d -p4222:4222/udp -p8080:8080/tcp ghcr.io/savoirfairelinux/opendht/opendht-alpine dhtnode -n 0 -p 4222 -s --proxyserver 8080
I am taking these pages as references :
- Utilisez Jami sur un réseau local — Documentation Jami
- Running a node with dhtnode · savoirfairelinux/opendht Wiki · GitHub
Actually, the container is manually started with this command line (not using systemd).
I aim at having my Jami clients (desktop and mobile) to use it, in what could be seem as a private network.
As JAMS let configure only the DHT Proxy entry point, I set in the blueprint “Use a custom DHT Proxy configuration” and set my Proxy URL: http://my.server.com:8080
From here, I have some issues to let 2 Jami clients communicate, and that seem quite random:
- desktop is registering on DHT (green dot)
- mobile on Wifi (same LAN as desktop) is registering on DHT (green dot)
- turning mobile from WiFi to mobile (so moving to internet) turn the green dot to orange, and never come back to green, until I put it back on WiFi
In the client settings, I see my “my.server.com” as a bootstrap, or on another client the official bootstrap.jami.net
Question 1: Is this setup enougth for the Jami clients to use it as a bootstrap ?
Question 2: If I have a (severe) internet cut, and my Jami clients can only see my (not in same LAN) server (JAMS + TURN + DHT node), should my clients still able to communicate with this single DHT node ?
Question 3: As I understood from the many pages, DHT is only used to allow find each other. messages (text, voice, video, files) are done peer-to-peer only (eventually through the TURN server I have set up). Do I understand it well ?
thanks for your information