The only range size supported currently is /16 which makes some sense for IPv4, but not so much for IPv6. By default, $wgBlockCIDRLimit['IPv6'] = 19 so a range of /19 should also be used as the default size for IPv6 blocks.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T179459 Enhance blocking in AbuseFilter | |||
| Stalled | None | T179454 AbuseFilter range blocks should be smarter | |||
| Resolved | Huji | T179456 AbuseFilter should use a different range size for IPv6 range blocks |
Event Timeline
Comment Actions
Change 387761 had a related patch set uploaded (by Huji; owner: Huji):
[mediawiki/extensions/AbuseFilter@master] AbuseFilter block range should not exceed wgBlockCIDRLimit
Comment Actions
@Huji — Unless it is an emergency, please do not add tickets directly to Anti-Harassment sprints. Our team holds Sprint planning meetings every-other Wednesday to select the tickets which we will focus on. Feel free to tag any ticket with the Anti-Harassment tag.
Comment Actions
Change 387761 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] AbuseFilter block range should not exceed $wgBlockCIDRLimit
Comment Actions
Change 390889 had a related patch set uploaded (by Huji; owner: Huji):
[mediawiki/extensions/AbuseFilter@master] Update the blockrange message in AbuseFilter, remove "/16" from it
Comment Actions
Change 390889 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] Update the blockrange message in AbuseFilter, remove "/16" from it