"
Ok, thanks, that's what I was asking. I completely understand that explanation. Kind of curious they do it that way relative to how most others do it but it works and that's what counts. Thanks!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
General Discussion / Re: Why firewall rules and vlans must use /32
January 21, 2020, 10:38:00 PM
Right, but /24 is the actual network which OPNSense then blocks or passes the entire subnet. This CIDR notation works correctly on other systems, for example, /12, /26, but you have to use a "network of one" /32 on OPNSense when setting a rule for a single host. If I have a host with an IP of 192.168.1.5/24 I have to set that up as 192.168.1.5/32 for the rules to work correctly.
I've not seen that elsewhere, you would simply use 192.168.1.5/24.
I've not seen that elsewhere, you would simply use 192.168.1.5/24.
#3
General Discussion / Why firewall rules and vlans must use /32
January 21, 2020, 09:09:16 PM
Can someone explain this to me? I did a brief search but couldn't find much.
I'm Cisco trained, have used pfSense for about a year and am on OPNSense, but do not understand why I need to use /32 instead of conventional notation.
I don't see this documented anywhere but have seen it in postings which lead me to use the /32 format for rules, vlans, etc with success.
I'm Cisco trained, have used pfSense for about a year and am on OPNSense, but do not understand why I need to use /32 instead of conventional notation.
I don't see this documented anywhere but have seen it in postings which lead me to use the /32 format for rules, vlans, etc with success.
Pages1
