Date: Tue, 25 Nov 2025 01:51:52 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 291163] feature request: blacklist-helper support for route --blackhole Message-ID: <bug-291163-227-L53CvacUjS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291163-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291163 --- Comment #1 from Jose Luis Duran <jlduran@FreeBSD.org> --- Thank you for sharing your ideas regarding blocklistd. With respect to this particular request, I can initially think of: 1. Using a custom control script: You can use your own control script with the functionality you wish to have. For example: cp /usr/libexec/blocklistd-helper /usr/libexec/my-blocklistd-helper Configure blocklistd to use your control script: sysrc blocklistd_flags="-C /usr/libexec/my-blocklistd-helper" Change the "add", "rem", and "flush" actions to achieve whatever you are looking for. For example: add) ... route add -blackhole ${addr}/${mask} <gateway> If your routing daemon redistributes static routes, you'll achieve your objective. The opposite can be done for "rem", and optionally "flush". 2. Suggest pre/post action hooks upstream: Given we are a downstream of https://github.com/zoulasc/blocklist, I'd suggest opening the feature request upstream. Maybe with the option to add pre/post hooks to the control script actions. In this case, you would just attach your custom functionality to the post-add/rem hooks, for example. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291163-227-L53CvacUjS>