Gavin Henry

Thanks for replying. If you're using the Docker hub one and not doing https://github.com/SentryPeer/SentryPeer#docker then you'd need to rebuild the container and just add a `-d` to the CMD section...

Sorry, I forget the issue subject says Debian 11 :-D

Hmm, that is strange for Homebrew. For your container, check out this post - https://stackoverflow.com/a/41147654/1072411

Hi @ynasida If any other SentryPeer nodes are online, enabled with p2p mode and connected bootstrap.sentrypeer.org or other nodes, then when they get a probe, you will get their bad_actor....

We do store bad actors permanently on the DHT, so we could get them on start up. I've just done it so we listen on that key and get other...

> Thanks, @ghenry ! I think I understood but still have two questions. My pleasure. > 'If any other SentryPeer nodes are online, enabled with p2p mode and connected bootstrap.sentrypeer.org...

Trying running two nodes on different IP addresses and then using sipsak against one. You should see the replication on the other node.

Going to close for now. Get back in touch with any other questions @ynasida Thanks!

It will be all the peer to peer traffic. As we're listening on port 4222, you start to become part of the main OpenDHT (https://jami.net) DHT - which you can...

Yeah, good point! I'll ask the team, but I don't think so. You're part of a public DHT and that means all bad_actors will get distributed and HA/DR is fantastic...