Preset SMP relays silently drop all connections from a public SMP relay

Aperta
#2,017 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
haskell
Ambito
networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Haskell
Stelle
865
Fork
125
Merge medio
1g 20h
PR unite (30g)
64

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Leggi la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di simplex-chat/simplexmq

Tutte le issue di simplex-chat/simplexmq

Issue simili

Altre issue su Haskell

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.