blocklist-ipsets

ipsets dynamically updated with firehol's update-ipsets.sh script

Security & Privacy

Explore on GitHub Read Hacker News discussions

2Distinct people

26Mentions

0Explicit recommenders

4KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

ipsets dynamically updated with firehol's update-ipsets.sh script

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:01:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year26 dated mentions

Observed mentions: 2018-08-08 17:08:51 UTC to 2026-09-11 12:05:20 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	3	2	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	0	2
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	2	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	5	0	5
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	4	0	4
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	3	0	3
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	0	1
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	3	0	3
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	3	0	3

What Hacker News says

3 sources

Bender·Dec 26, 2025

Blocking the exit nodes is quite tivial [1] but it would indeed be hard to stop people from accessing Tor and .onion sites. More websites should add some Tor .onion nodes even if they have to put those in read-only mode on user-provided multimedia sites to avoid complex CSAM filters. [1] - https://github.com/firehol/blocklist-ipsets/blob/master/tor_...

In Governments in the West Are Turning Their Sights on VPNs

LinuxBender·Mar 26, 2025

I had also tried that but some repos still get fairly big and all I wanted was the code not the .git since I am not a proper developer. To your point they can still be quite large. cd /dev/shm/block && git clone -j4 --depth=1 --branch=master https://github.com/firehol/blocklist-ipsets.git du --max-depth 1 -hc 24M ./ipip_country 4.0M ./ipdeny_country 9.6M ./ip2location_country 6.9M ./geolite2_country 25M ./.git 140M . 140M total It's not awful but I currently keep up to date copies of about 300 git repos and if I keep all the big ones it can add up to several GB of data I do not need. For now I just clone to a ramdisk and whack the .git directory for several of the big ones before I rsync back to disk. I probably lose some interesting history doing that.

In Most engineers have Git aliases; what are yours?

LinuxBender·Mar 17, 2025

Blackhole all their ASN's and be done with it. It sounds like the crawlers are not adding anything back to SourceHut. This exercise takes a while the first time around but take one IP from each CIDR block and look up all the IP's [1][2] they own, aggregate it [3] using a script to summarize into larger CIDR blocks and have a cron "@reboot" or systemd unit file script that performs: ip route add blackhole "${ClownNet}" # in a loop through a text file This is how I ended up blocking archive.is along with using a couple MSS rules. waves to their admin here on HN Obviously don't block anything you have to reach out to or consumer ISP networks in countries you wish to do business with unless you are a bastard operator from hell like me. It's far less CPU than using firewall rules and takes minuscule amounts of kernel memory. Be sure

Read the rest

to also have a URL your visitors can go to in order to grab their IP address should they claim they are blocked. Link to this comment in a Jira and test it in a staging environment. Be sure to test all the regular outbound connections that you make in production in your staging environment. If you do want to block entire countries without having to look something up on every web hit then use this [4] to add to the blackhole script with a little data massaging. Everything in the blackhole text file must be versioned and committed into your internal repository so one can tell when a network added is breaking things and one can quickly roll back. Have a function in the script that deletes all the blackholes. I blackhole about 27,000 CIDR blocks on a tiny VM web server and the script takes 20 seconds to complete. [1] - https://bgp.tools/ [2] - https://bgp.he.net/ [3] - https://adrianpopagh.blogspot.com/2008/03/route-summarizatio... [4] - https://github.com/firehol/blocklist-ipsets/tree/master/ipip...

In LLM crawlers continue to DDoS Sourcehut