Changes

Talk:PFSense and OPNsense

1,627 bytes added, 4 February
/* communications error to 127.0.0.53 timed out */ new section
The following lines were added (+) and removed (-):
Selectively enforcing pfBlockerNG for specific clients or networks: filtering content for specific clients or networks in pfSense while keeping pfBlockerNG is not a simple task. If we wanted a simpler solution, we could’ve just added a Custom DNS server for our VLAN we wanted content filtered on. Unfortunately, doing this circumvents Unbound (DNS Resolver) and we lose the functionality of pfBlockerNG. To complicate matters more, Unbound does not allow you to specify different servers for the same lookup zone based on who’s querying the server.* https://mitky.com/pfblockerng-pfsense-filter-specific-clients-computers-network/Zenarmor block websites on the pfSense software firewall and the importance of web filtering.* https://www.zenarmor.com/docs/network-security-tutorials/how-to-block-websites-on-pfsenseThe hosting platforms used by Discord is primarily  Google Cloud Platform.  * https://www.netify.ai/resources/applications/discord== Block Malicious IPs in pfSense at David's Homelab  ==pfSense provides a package called pfBlockerNG which allows for advanced and dynamically updating blocking rules based on blocklists or GeoIP data. It also supports DNS blocking so can fully replace Pi-hole if you choose to enable this feature.* https://davidshomelab.com/block-malicious-ips-in-pfsense/== communications error to 127.0.0.53 timed out ==communications error to 127.0.0.53 timed outdefine a rule on LAN to allow a workstation to pass traffic to destination- the firewall itself.  This allows DNS queries to go between the workstation and firewall when the firewall is the DNS server ubound.
Admin
Bureaucrat, administrator
16,192
edits