The autofill isn't working
-
@propercactus said in The autofill isn't working:
Could it be the API that ronpfs mentions above?
Maybe not, that file is installed when pfBlockerNG is installed, so it doesn't rely on the API for that.
ls -al /usr/local/www/pfblockerng/pfblockerng_asn.txt -rw-r--r-- 1 root wheel 3742472 Nov 10 2020 /usr/local/www/pfblockerng/pfblockerng_asn.txt -
Works for me in Firefox but not Safari, both on a Mac.
It's also the same with Firewall -> pfBlockerNG - Log Browser, if I select Logfiles and maxmind_ver the Log/File Details and Log is empty in Safari.
-
@propercactus said in The autofill isn't working:
@johnpoz OK yup it's working in firefox for my mac, but not in Brave Browser (with the anti-tracker/blocking stuff turned off).
@jdeloach what browser were you trying with?
The browser I was using was Microsoft Edge for Windows 10.
I used to use Firefox but got tired of the ~10 second delay in Firefox opening a web page. Never could resolve how to fix that issue so I went to Edge.
-
I tested it with edge on windows 10, I saw no issues with the asn or geoip filling in the dropdown upon entry of some criteria to look for..
As to 10 second delay in opening pages with firefox? I have been running firefox for ages - I don't recall every having such an issue. Are you letting firefox use doh? That could cause a delay I guess, or maybe your using ipv6 and ipv4 and your having issues with switching to ipv4 when ipv6 doesn't work?
Never been a fan of MS browsers - be it IE or the new edge.. But it really should work in any browser.. As to what is going on with the other browsers on mac, I have no ideas really since I don't have any mac to play with..
Biggest complaint I have had with FF is their attempt to force doh on users.. But since it can be disabled, without all that much effort.. But still should be zero effort, if a user wants to use doh, then it should be on the user to switch to that.. It should never be a default anything in imho..
-
@johnpoz unfortunately DoH is being forced by apple too. I get a warning that my wifi is not private because I'm blocking DoH to known resolvers. At least Apple just throws a warning message and reverts to DNS as usual.
-
Not sure I would call it forced - while an app can try and use it.
From my understanding the default is not to use it. If you have links to info to the contrary I would be interested for sure.
I block all known doh ip and fqdn and block dot port. I would know if any of my devices were attempting to use doh, unless I have missed the IP of some unknown doh out there. But I update the lists regularly - and anything that major player like apple/ios/windows/browsers/etc were defaulting to should be listed on these lists.
The idea that apps or browsers or whatever can just send dns queries to some server they want to set without direct and explicit ok from the user is not a favorable direction that is for sure.
-
@johnpoz said in The autofill isn't working:
I block all known doh ip and fqdn and block dot port. I would know if any of my devices were attempting to use doh, unless I have missed the IP of some unknown doh out there.
Yea same, I guess Apple is just complaining that the DoT port is closed irrespective of if it's using it or not. It just gives me a privacy alert sometimes in the Wifi area saying the network isn't allowing encrypted DNS.
-
Im blocking dot, and I have seen no such warning on my iphone. I see the privacy warning about not use random mac..
-
@johnpoz Yea this is it here https://www.google.com.au/amp/s/amp.reddit.com/r/pihole/comments/hfpraa/ios_14_privacy_features_your_network_may_be/
I only see it intermittently occasionally. Only because I was switching between my wifi networks that I noticed it. Doesn’t happen all the time strangely.
Maybe it does random DoH/DoT queries to test if blocking and alerts I dunno, it seems to happen randomly in my case.
-
I will keep an eye out for it - maybe you have some app trying to use it?
Just took a look at my log for dot.. Only my shield TV is hitting it now and then.. Seems to try once an hour ;)
And good thing is - its trying it to the dns I have set it to use.
