Page MenuHomeFreeBSD

Add a section to blacklistd to the PF chapter of the handbook
ClosedPublic

Authored by bcr on Jun 9 2019, 12:44 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Mar 24, 3:54 AM
Unknown Object (File)
Feb 9 2024, 11:14 PM
Unknown Object (File)
Dec 22 2023, 10:53 PM
Unknown Object (File)
Nov 27 2023, 7:43 PM
Unknown Object (File)
Nov 16 2023, 8:23 AM
Unknown Object (File)
Nov 14 2023, 2:34 PM
Unknown Object (File)
Nov 14 2023, 2:08 AM
Unknown Object (File)
Nov 9 2023, 9:55 AM
Subscribers
None

Details

Summary

This patch adds a description on how to use blacklistd together with PF to the handbook.
The rendered output can be found starting at section 30.3.2.5.

I'm not really sure about the proper placement of this. It could go at the end of the chapter, it's own chapter or where it is now. Where it is currently, having too many sub-sub-subsections does not look good to me.

Test Plan
  1. Apply the patch in the local doc directory
  2. Build the handbook afterwards
  3. Check the output of firewalls-pf.html

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

en_US.ISO8859-1/books/handbook/firewalls/chapter.xml
1052 ↗(On Diff #58434)

"a network that should not be accessed"
I'm not sure what you mean here.

1096 ↗(On Diff #58434)

Rules either belong to...

1097 ↗(On Diff #58434)

which applies to?

1136 ↗(On Diff #58434)

SSH primarily uses TCP?

(And not just primarily. I don't think you can do SSH over UDP.)

Update diff to address Kristof's comments.

Given that it's possible to use blacklistd with ipfw as well (at least, I believe it is), it should probably get its own chapter, with pf and ipfw subchapters.

Sorry to keep you waiting for an update for so long.
I've refactored the blacklistd section into it's own chapter at the end of the firewalls chapter. There are no links from the PF chapter (or any other) to it yet.

Other than the typo this looks good to me.

en_US.ISO8859-1/books/handbook/firewalls/chapter.xml
4108 ↗(On Diff #61691)

Expire?

Good catch with the "expore", which should indeed be "expire". For some reason, igor did not catch that.
I think we can risk committing it to the handbook now and fix other things in a followup commit.

This revision was not accepted when it landed; it landed in state Needs Review.Sep 20 2019, 12:50 PM
This revision was automatically updated to reflect the committed changes.