fast.com speedtest not working most of the time
-
I do have an issue with actual pfBlockerNG (pfSense 23.01) python mode enabled and speedtest website from https://fast.com
It says: 'Could not reach our servers to perform the test. You may not be connected to the internet'
Could this be because of pfBlockerNG python mode with CNAME validation?
Can someone check if fast.com is working for you?
-
@thundergate said in fast.com speedtest not working most of the time:
https://fast.com
I have pfSense.
It's connected - if not then can some one explain who I managed to post this message ?
I have 'pfBlockerNG' - latest version. I guess.
But I didn't had CNAM validation achecked (activated) Should I ? Live is better using this option (your question tends to prove not ;)
I check that option now.
For good manners, I stopped 'unbound' and started it again - now my local cache is empty, forcing every DNS info to be refetched.
Btw : I'm forwarding - not Resolving - these days.
I asked pfBlocker to show 'fast.com' was handled :
I even saw he CNAME (whatever that might be ;) )
Also note that everything is IPv6.
For the speed test to work, I guess 'api.fast.com' is used. That's the endpoint used by the JS in the web fast.com page.
Last but not least : what IP and/or DNSBL feeds did you add ?
Did you check them ? (like : open them up, and read them all !)
If one of those lists contains 'api.fast.com' or 'fast.com' you just proved that pfBlockerNG does what it promised to do
-
@gertjan
Hi. Thx for your feedback.Yes - checked the lists. That's not the issue.
I think it really has something to do with the CNAME validation function.
Don't know exactly what is causing those issues at all.
-
@thundergate Found the issue.
Also had some issues with affinity checking it's servers.
When I enable (check) System > Advanced > Firewall/NAT > 'Clear invalid DF bits instead of dropping the packets' everything is working fine.
Don't know why - but it's working now.