pfsense:pfblockerng:selectively_enforcing_pfblockerng_for_specific_clients_or_networks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| pfsense:pfblockerng:selectively_enforcing_pfblockerng_for_specific_clients_or_networks [2020/11/29 13:03] – peter | pfsense:pfblockerng:selectively_enforcing_pfblockerng_for_specific_clients_or_networks [2021/01/06 10:06] (current) – [Basic Example] peter | ||
|---|---|---|---|
| Line 39: | Line 39: | ||
| This means all the Unbound commands generated by pfBlockerNG are not referenced when a client in 192.168.10.x queries pfSense, so DNS queries go through unchanged. | This means all the Unbound commands generated by pfBlockerNG are not referenced when a client in 192.168.10.x queries pfSense, so DNS queries go through unchanged. | ||
| - | For the 192.168.20.x network, the entries are included and redirected to our sinkhole. | + | For the 192.168.20.x network, the entries are included and redirected to the pfBlockerNG |
| It is important to note that you can use these entries in any CIDR notation that fall within your network topology. | It is important to note that you can use these entries in any CIDR notation that fall within your network topology. | ||
pfsense/pfblockerng/selectively_enforcing_pfblockerng_for_specific_clients_or_networks.1606655010.txt.gz · Last modified: 2020/11/29 13:03 by peter