Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ASN.Telegram.list有更新 #29

Closed
im-Kalix opened this issue Jan 15, 2023 · 1 comment
Closed

ASN.Telegram.list有更新 #29

im-Kalix opened this issue Jan 15, 2023 · 1 comment

Comments

@im-Kalix
Copy link

im-Kalix commented Jan 15, 2023 •
edited

在实际使用中发现了发往5.28.195.7的请求，国内直连第一次握手成功后会被阻断。whois相关查询结果节选如下：

# whois.ripe.net

inetnum:        5.28.192.0 - 5.28.199.255
netname:        TELEGRAM-MESSENGER-INFRA-NET
country:        NL
status:         ASSIGNED PA
admin-c:        VVV27-RIPE
tech-c:         VVV27-RIPE
mnt-by:         IPFFM
created:        2022-05-18T07:07:43Z
last-modified:  2022-05-18T07:07:43Z
source:         RIPE

在ASN.Telegram.list中已经存在两条极为相似的规则：

IP-CIDR,5.28.195.163/32,no-resolve // IPFFM - Internet Provider Frankfurt GmbH
IP-CIDR,5.28.195.205/32,no-resolve // IPFFM - Internet Provider Frankfurt GmbH

再结合ripe.net和ipip.net的查询结果，综合起来，我认为可以把以上两条规则合并为
IP-CIDR,5.28.192.0/18,no-resolve
@im-Kalix im-Kalix mentioned this issue Jan 15, 2023
Closed
@im-Kalix
Copy link
Author

IP-CIDR,91.108.0.0/16,no-resolve // eTelecom_Customers_NAT_Network
这一条是不是多余了？和IP-ASN 62014重复了吧，有什么依据吗？好像有概率误伤其他IP。

VirgilClyne added a commit that referenced this issue Jan 18, 2023
@VirgilClyne
fix(ASN.Telegram): fixed #29
a00d350 
Update ASN.Telegram.list
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@im-Kalix