It would be useful if it were possible to ban IP ranges not just by netmask, but also by ASN number (as provided by asmap).
Suggested by @gmaxwell.
-
sipa commented at 3:18 AM on June 1, 2020: member
- sipa added the label Feature on Jun 1, 2020
- fanquake added the label P2P on Jun 1, 2020
-
naumenkogs commented at 7:21 AM on June 2, 2020: member
Big ACK :)
-
naumenkogs commented at 2:40 PM on June 24, 2020: member
I was implementing this, but then realized that "mapped AS" might not make sense here?
I assume the main goal here is to protect against inbound Sybil conns based in certain cloud providers? Then it makes more sense to look at the actual final AS, not the "mapped" AS (a.k.a bottleneck).
Perhaps in practice final equals mapped in the majority of cases, but I don't think we want to rely on that? But then it would be unfortunate to supply 2 different files: one for mapped ("bottleneck") ASes and one for actual ASes... @gmaxwell @sipa
- jasonbcox referenced this in commit e59a7e1253 on Nov 13, 2020
Contributors