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

未關閉
#2,017 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
haskell
領域
networking

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
Haskell
星號
865
分支
125
平均合併
1 天 20 小時
30 天內合併 PR
64

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

simplex-chat/simplexmq 的其他 Issue

查看 simplex-chat/simplexmq 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。