pfBlocklerNG v3.0.0_6-devel blocking all outbound traffic?
-
Applied update this morning. Nothing appears in the pfBlockerNG Report after the time I updated. All outbound URLs are unable to resolve DNS. Not sure what happened but had to stop pfBlocker so work could continue.
-
is unbound running ?
-
@nogbadthebad Yes
-
@rloeb said in pfBlocklerNG v3.0.0_6-devel blocking all outbound traffic?:
had to stop pfBlocker so work could continue.
we received this as a gift after 3.0.0.5, be patient...pls.
there is finally progress at this level
-
Rebooted pfsense appliance. Now seems to be working, although it's not clear the DNS queries are being redirected.
-
@rloeb said in pfBlocklerNG v3.0.0_6-devel blocking all outbound traffic?:
Rebooted pfsense appliance
that would have been the proposal
what do you mean....
@rloeb "it's not clear the DNS queries are being redirected."the colleague's @NogBadTheBad question was about this, ergo the traffic is not blocked by pfBlockerNG, the resolver probably had a problem, somewhat
-
@daddygo Apologies for delayed response. Juggling too many glass balls... Put Wireshark on WAN side of pfsense and saw some DNS queries go to 8.8.8.8 (should have been TLS to 1.1.1.1). Restarted everything and did not see that occur again.
-
@rloeb said in pfBlocklerNG v3.0.0_6-devel blocking all outbound traffic?:
Put Wireshark on WAN side of pfsense and saw some DNS queries go to 8.8.8.8 (should have been TLS to 1.1.1.1). Restarted everything and did not see that occur again.
if the setting is good it is impossible
Like:
+++++ https://docs.netgate.com/pfsense/en/latest/recipes/dns-redirect.html
-
@daddygo Yup. Verified. Thank you.
-
@rloeb said in pfBlocklerNG v3.0.0_6-devel blocking all outbound traffic?:
Thank you.
Do not mention it
