Bug 229363 - Incomplete documentation for FreeBSD ipfw
Summary: Incomplete documentation for FreeBSD ipfw
Status: New
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-27 12:53 UTC by shriyogeshchandra
Modified: 2018-06-27 17:10 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shriyogeshchandra 2018-06-27 12:53:44 UTC
When I see the official documentation of ipfw[1] or the man pages[2] it seems that it is sometimes incomplete. Specifically, there are a lot of options like, 

    firewall_myservices
    firewall_allowservices

etc., which can be found in many online guides[3] but **not** in the docs. They're even discussed in the lists[4]. 

So I would like to understand if these are unofficial or undocumented options, and if they might be arbitrarily removed at some point in the future since they're not formally documented. More importantly, is there a single comprehensive documentation source for ipfw, short of grokking the source code? 

  [1]: https://www.freebsd.org/doc/handbook/firewalls-ipfw.html
  [2]: https://www.freebsd.org/cgi/man.cgi?ipfw(8)
  [3]: https://www.digitalocean.com/community/tutorials/recommended-steps-for-new-freebsd-10-1-servers
  [4]: https://lists.freebsd.org/pipermail/freebsd-questions/2016-July/272455.html
Comment 1 shriyogeshchandra 2018-06-27 13:05:44 UTC
Not being too experienced with it, I do not know what else is missing in the ipfw docs, but I am happy to add some notes about the few things that I found missing, based on what I learned from the other guides on the internet. Just let me know where to make/submit the changes.
Comment 2 shriyogeshchandra 2018-06-27 17:10:22 UTC
So it seems that the options which are left out in the official docs are actually easily found in /etc/rc.firewall, which also happens to have the relevant explanations in the comments.