Bug #12952
closedAfter update to v. 22.01 DNS Resolver Custom Options for bypassing PfBlockerNG not working
0%
Description
Immediately after updating PfSense+ on Netgate 7100 from v. 21.05.2 to 22.01 the bypass setting for PfBlockerNG stopped working.
On 21.05.2 PfBlockerNG blocked blacklisted sites on Vlan 192.168.3.0/24 alone.
From 22.01 All Vlans are filtered.
DNS Resolver custom options are (unchanged between updates):
server:
access-control-view: 172.50.50.0/24 bypass
access-control-view: 172.17.17.0/24 bypass
access-control-view: 192.168.3.0/24 dnsbl
view:
name: "bypass"
view-first: yes
view:
name: "dnsbl"
view-first: yes
server:include: /var/unbound/pfb_dnsbl.*conf
NB: We are using the system in a corporate production environment, the issue is very crippling for our productivity and ability to service our customers.
*Sysem information:
Netgate 7100
22.01-RELEASE (amd64)
built on Mon Feb 07 16:37:59 UTC 2022
FreeBSD 12.3-STABLE
BIOS:
Vendor: coreboot
Version: ADI_PLCC-01.00.00.11
Release Date: Tue Jan 8 2019
Intel(R) Atom(TM) CPU C3558 @ 2.20GHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: Yes (inactive)
For further information contact on mail or call +4560149911
Files
Updated by Jim Pingle over 3 years ago
- Project changed from pfSense Plus to pfSense Packages
- Category changed from DNS Resolver to pfBlockerNG
- Status changed from New to Closed
- Priority changed from Very High to Normal
- Release Notes deleted (
Default) - Affected Plus Version deleted (
22.01)
I cannot reproduce any issues with views in the DNS resolver as described. It's possible there is a local issue in pfBlockerNG in your setup, but this site is not for support or diagnostic discussion.
If you have support through Netgate TAC, create a ticket there for personal assistance.
Otherwise, for assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.