-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network Firewall docs (issue #1025) #1060
Network Firewall docs (issue #1025) #1060
Conversation
@@ -81,7 +81,7 @@ Leave the defaults for "Time Server Information". Click Next. | |||
|
|||
On "Configure WAN Interface", enter the appropriate configuration for your network. Consult your local sysadmin if you are unsure what to enter here. For many environments, the default of DHCP will work and the rest of the fields can be left blank. Click Next. | |||
|
|||
For "Configure LAN Interface", set the IP address and subnet mask of the Application Subnet for the LAN interface. Click Next. | |||
For "Configure LAN Interface", set the IP address and subnet mask of the Application Subnet for the LAN interface. Be sure that the CIDR prefix correctly corresponds to your subnet mask-- pfsense should automatically calculate this for you, but you should always check. Click Next. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add that for the values used in the doc the CIDR should be /24
So they don't need to look it up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Furthermore, in L36, I suggest: This is a very common subnet choice for home routers.
-> The /24 subnet is a common choice for home routers.
Specifically referring to the subnet by CIDR notation adds clarity for non-technical folks, at no cost to clarity for technical audiences.
...maybe we add something like, "default will always be |
In the install docs we recommend using the 10.20.2.0 network with a subnet mask 255.255.255.0 for the monitor server's network. It is configurable by the admin to accommodate certain edge cases. One of which is if the 10.20.1.0 or 10.20.2.0 networks are in use someplace else in the corporate environment. Then the admin would want to use a different network(s) for the app and monitor server networks to avoid routing table issues with SD network firewall. Any internal ip range netmask that provides 2 usable IP addresses will work. |
One more change: In L36 Then we should be all set. |
Agree with @conorsch's last comment. One of the best pieces of advice about writing clearly I've ever received is to always carefully consider the use of the word "this". It may seem clear to the writer at the time of writing due to their mental context, but it is often ambiguous and confusing! |
lgtm. Ready to merge @harlo? |
Network Firewall docs (issue #1025)
as per #1025