Preset SMP relays silently drop all connections from a public SMP relay
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- haskell
- Bereich
- networking
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Haskell
- Sterne
- 865
- Forks
- 125
- Ø Merge
- 1 T. 20 Std.
- Gemergte PRs (30 T.)
- 64
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus simplex-chat/simplexmq
-
xftp CLI: Generated web link is missing the /file pathEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
simplex-chat/simplexmq#1853 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
simplex-chat/simplexmq#1781 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 32/100
simplex-chat/simplexmq#2074 ·
Maintainer antworten meist innerhalb von 1 Tag
-
resolver: resolve .simplex names, on smp7 and then on the preset routersEvtl. vergeben @shumvgolove hat das vor 18 Tagen übernommen. Offen
simplex-chat/simplexmq#2011 · 2 Kommentare · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 30/100
simplex-chat/simplexmq#1864 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in simplex-chat/simplexmq
Ähnliche Issues
-
bug desktop
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
simplex-chat/simplex-chat#8291 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[BUG]: C# programs with top-level statements fail to compileEvtl. vergeben @AsyncNigam hat das heute übernommen. Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
compiler-explorer/compiler-explorer#9625 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
needs triage type: enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 3 Tagen
-
reflex-0.10Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 62/100
commercialhaskell/stackage#8180 ·
Maintainer antworten meist innerhalb von 1 Tag
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
OpenZeppelin/canton-contracts#140 ·
Maintainer antworten meist innerhalb von 1 Tag