We’ve got a troll who keeps coming back and it’s true that he has a new IP each time but it’s relatively easy for me to spot him and stop him based on his location coming up and his style. Mostly he has IPv6 IPs What I noticed was that Screened IPs shows a couple of his: [image] But they’re not …

I can confirm that if you add a block for an IPv6 range (e.g. 2001:2012:208:2a00::/64) it’ll work as expected: [image] but we do need to fix search and the column width. As for the automatic roll-up, we probably want to do something like: if we have ≥3 blocks in the same IPv6 /64, then summariz…

Apologies, if I click to edit I see the full IP with a /128 at the end, so maybe I can mask ban?

Yes, in fact repeated spam blocks will automatically roll up IP address blocks to increasingly large subnets, such as 255.255.255.* and 255.255.*.* I’m not sure what this code does with IPv6 though.. cc @mpalmer @zogstrip

I reckon I didn’t test IPv6 blocks. Added to my list.

Does Discourse handle blocking of IPv6 okay?

Product Support

1101010 (Theo) March 16, 2018, 11:47pm 6

Thanks a lot for this.

I did briefly try one with four stars in between the remaining colon blocks and /128 at the end but it was rejected as in error.

Topic		Replies	Views
Unintuitive IPv6 address search in Screened IPs UX	0	103	April 16, 2025
Can't search blocked IPs Feature	6	1882	February 10, 2015
How can I block an IP address? are there wildcards? Product Support	14	7188	May 28, 2016
Stop discourse blocking CIDR blocks Product Support	2	1635	September 21, 2016
Spammers signing up from "blocked" IP addresses Product Support	8	1513	May 27, 2015

Does Discourse handle blocking of IPv6 okay?

Related topics