Hi -
I just upgraded to TruNAS core 13 (from freenas 11, through 12) and I see that FreeBSD 13 has `blocklistd` (as "`blacklistd`", the older name) installed by default, and I'm hoping to be able to use it (because I see many, many failed ssh attempts in my logs) - since it's not part of the TruNAS "core" service listings, I know if I just configure it the normal FreeBSD way, it will get overwritten on boot or upgrade.
Does anyone have a good suggestion of how to implement something like this in a way that's survivable of a reboot (and also, hopefully, an upgrade) ? It feels like I can probably do it with a startup script, which it looks like is a supported thing, but if someone has done something like this already, I'd love to not need to reinvent the wheel...
(comments about how getting failed ssh attempts mean I should rearchitect my network will be summarily ignored)
I just upgraded to TruNAS core 13 (from freenas 11, through 12) and I see that FreeBSD 13 has `blocklistd` (as "`blacklistd`", the older name) installed by default, and I'm hoping to be able to use it (because I see many, many failed ssh attempts in my logs) - since it's not part of the TruNAS "core" service listings, I know if I just configure it the normal FreeBSD way, it will get overwritten on boot or upgrade.
Does anyone have a good suggestion of how to implement something like this in a way that's survivable of a reboot (and also, hopefully, an upgrade) ? It feels like I can probably do it with a startup script, which it looks like is a supported thing, but if someone has done something like this already, I'd love to not need to reinvent the wheel...
(comments about how getting failed ssh attempts mean I should rearchitect my network will be summarily ignored)
