It would seem @ about line 104 in features.html
    href="https://wiki.ipfire.org/configuration/services/ids"
would need to be changed to ... 
    href="https://wiki.ipfire.org/configuration/firewall/ips"
 
That would fix the button press.
And perhaps it would also seem reasonable to change the text references from "Detection" to "Prevention" and correspondingly change the acronym "IDS" to "IPS"

https://community.ipfire.org/t/broken-link-in-https-www-ipfire-org-features/7284/3

http://git.ipfire.org/?p=ipfire.org.git;a=commit;h=73cebb40bb196fe2312f79da703adb7b75920f2f

Author: Michael Tremer <michael.tremer@ipfire.org>

features: Update text and link around the IPS

Fixes: #12749
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

Oh nice, I didn't know there was a nice script that does this for me :)

This is all rolled out now. Thank you for noticing.

The web-page text “Upon detection, alerts are raised and the attacker is immediately blocked”  tends to hint of the legacy technique of blocking the attacker with Guardian.  Nowadays the ‘attacker’ is not blocked, rather the offending packet(s) that raise alerts are ‘dropped’.

Y(In reply to Charles Brown from comment #5)
> The web-page text “Upon detection, alerts are raised and the attacker is
> immediately blocked”  tends to hint of the legacy technique of blocking the
> attacker with Guardian.  Nowadays the ‘attacker’ is not blocked, rather the
> offending packet(s) that raise alerts are ‘dropped’.

Yes, I stumbled over this one as well.

I believe that in all this brevity, this is correct. We will scan first, then detect something, and then log the packet and drop it. Guardian worked differently, but worked in the same way.

The entire website is (hopefully) be replaced soon and the entire features page will go. To avoid investing too much time into this, I would like to leave it the way it is and hopefully we will do better with the next one.

Sounds good.  Thanks for all your dedicated efforts on this damn fine product.