Preset SMP relays silently drop all connections from a public SMP relay
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- haskell
- Domaine
- networking
Piste de recherche
The report names no source files or tests; start by reading the relay connection and block-list handling, then compare the reported direct TCP failures with the working Tor connections. Use the packet captures, traceroutes, and timestamps the reporter offers to investigate why these relay addresses are dropped. Done means identifying the cause and resolving or explaining the block.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
I run a public SMP relay (stock simplexmq v7.0.1, with an info page that lists operator and complaint contacts). For several days now my relay can't connect to any of the preset SimpleX SMP relays (smp4 to smp19.simplex.im). Every new TCP connection from it is silently dropped. It happens from all the addresses the relay has used, two IPv4 and one IPv6. I emailed and wrote in chat a few days ago but got no reply, so I'm asking here.
The odd part is that it only affects the SMP relays. From the same addresses I can reach ntf2/ntf3, all xftp1-6 servers and the website without any problem. Through Tor all 14 SMP relays work fine. Another server I have at the same hosting provider also reaches all 14 relays over IPv4 and IPv6.
I spent quite some time making sure it's not my side. I captured packets on the network interface before the firewall. The SYNs to your relays (for example 23.128.248.112 and .121, on both 5223 and 443) go out and get retransmitted, but nothing ever comes back: no SYN-ACK, no RST, no ICMP. Connections from the same address to other operators' relays get a SYN-ACK right away. I compared firewall counters before and after the test, and none of my rules touched your addresses; they aren't in any local ban list either. DNS answers match 1.1.1.1 and 9.9.9.9. Routing is normal: right gateway for each source address, no blackhole routes, nothing in mangle/raw/nat. A TCP traceroute to 23.128.248.112:5223 gets to 194.110.60.53, the last hop before the relay, and stops there. From my other server the path goes through the same 194.110.60.53 and the relay answers.
The block also seems to follow the relay's DNS name. When I moved the name to a new IPv4 and IPv6, both new addresses were blocked within about an hour. The old IPv4 started working again roughly 1.5 hours after the name moved away from it, and then about a day later it was blocked again (other names in the same domain still point there). Right now none of the three addresses can reach any of the 14 SMP relays.
For now I've set socks_mode: always, so private routing from my relay to yours goes through Tor and messages still get delivered. But it's slower and depends on Tor.
If the preset relays use a server block list (like the one described in the moderation RFC from December 2024), I'd really like to know whether my relay is on it and why. Nobody has sent me any complaint, and if there is a report about content on my server I'll deal with it right away. More generally, it would help operators to have some way to find out about a block and appeal it.
I can share the captures, traceroutes and exact timestamps privately if that helps.
- Langage dominant
- Haskell
- Étoiles
- 865
- Forks
- 125
- Merge moyen
- 1 j 20 h
- PR mergées (30 j)
- 64
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de simplex-chat/simplexmq
-
xftp CLI: Generated web link is missing the /file pathPeut-être pris Une pull request liée à cette issue est ouverte ou déjà fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
simplex-chat/simplexmq#1853 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
simplex-chat/simplexmq#1781 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 4/5 3-5 jours Accessibilité débutants 32/100
simplex-chat/simplexmq#2074 ·
Les mainteneurs répondent en général sous 1 jour
-
resolver: resolve .simplex names, on smp7 and then on the preset routersPeut-être pris @shumvgolove l’a pris il y a 18 jours. Ouverte
simplex-chat/simplexmq#2011 · 2 commentaires · 1 personne assignée ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 30/100
simplex-chat/simplexmq#1864 ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de simplex-chat/simplexmq
Issues similaires
-
bug desktop
Difficulté 2/5 1-3 heures Accessibilité débutants 85/100
simplex-chat/simplex-chat#8291 ·
Les mainteneurs répondent en général sous 1 jour
-
[BUG]: C# programs with top-level statements fail to compilePeut-être pris @AsyncNigam l’a pris aujourd’hui. Ouvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
compiler-explorer/compiler-explorer#9625 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
needs triage type: enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 3 jours
-
reflex-0.10Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 62/100
commercialhaskell/stackage#8180 ·
Les mainteneurs répondent en général sous 1 jour
-
documentation
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
OpenZeppelin/canton-contracts#140 ·
Les mainteneurs répondent en général sous 1 jour