Incomplete documentation for FreeBSD ipfw
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
When I see the official documentation of ipfw or the man pages 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 but not in the docs. They're even discussed in the lists.
So I would like to understand if these are unofficial or undocumented options, and if they might be 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?
freebsd firewall documentation ipfw
asked Jun 27 at 12:03
Yogesch
8215
add a comment |Â
up vote
0
down vote
favorite
When I see the official documentation of ipfw or the man pages 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 but not in the docs. They're even discussed in the lists.
So I would like to understand if these are unofficial or undocumented options, and if they might be 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?
freebsd firewall documentation ipfw
asked Jun 27 at 12:03
Yogesch
8215
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I see the official documentation of ipfw or the man pages 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 but not in the docs. They're even discussed in the lists.
So I would like to understand if these are unofficial or undocumented options, and if they might be 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?
freebsd firewall documentation ipfw
asked Jun 27 at 12:03
Yogesch
8215
When I see the official documentation of ipfw or the man pages 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 but not in the docs. They're even discussed in the lists.
So I would like to understand if these are unofficial or undocumented options, and if they might be 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?
freebsd firewall documentation ipfw
asked Jun 27 at 12:03
Yogesch
8215
edited Jun 27 at 13:34
asked Jun 27 at 12:03
Yogesch
8215
asked Jun 27 at 12:03
Yogesch
8215
asked Jun 27 at 12:03
Yogesch
8215
8215
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58
add a comment |Â
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
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.
answered Jun 27 at 17:09
Yogesch
8215
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
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.
answered Jun 27 at 17:09
Yogesch
8215
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
add a comment |Â
up vote
1
down vote
accepted
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.
answered Jun 27 at 17:09
Yogesch
8215
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
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.
answered Jun 27 at 17:09
Yogesch
8215
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.
answered Jun 27 at 17:09
Yogesch
8215
answered Jun 27 at 17:09
Yogesch
8215
answered Jun 27 at 17:09
Yogesch
8215
answered Jun 27 at 17:09
Yogesch
8215
8215
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
add a comment |Â
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
Then for better results add a patch to your bug report that copies that information into the rc.firewall manual.
– JdeBP
Jun 28 at 8:50
1
1
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
Haven't looked but man pages will often refer you to the comments in the conf files for more information. General practice on FreeBSD is to look in the conf files also.
– Rob
Jun 28 at 11:37
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
I think there is no need to start a big fuss on variables in /etc/rc.firewall. Actually, some of oldschool guys usually wipe its contents and write rules by hand ignoring the template.
– Mikhail Zakharov
Aug 8 at 14:26
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452205%2fincomplete-documentation-for-freebsd-ipfw%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Maybe you should open a bug report too (bugs.freebsd.org/bugzilla).
– uzsolt
Jun 27 at 12:23
Yes, that might actually be a good idea in this case. Just did it bugs.freebsd.org/bugzilla/show_bug.cgi?id=229363
– Yogesch
Jun 27 at 12:58