I know that SpamHaus is using this dataset as a large (at times sole) contributor to their blocklists. So corporate buyers are doing exactly what you describe, albeit indirectly.
Lack of any IoCs also makes it hard to refute or remedy. Plus I think it paints even Tor relay nodes with the same brush as malicious proxies.
Truly kafkaesque if you start getting restricted and nobody tells you why or even knows what to tell you because the sources have all been mixed and obscured.
They give you the full /64 even on vps or kimsufi(low end servers) it's just that the interface is configured with the ::1/128 by default in their cloud-init.
Their documentation about it is not consistent though, so the confusion is understandable.
If it's a station (client) then it's unlikely, as long as your APs are compliant.
With some chipsets it can end up being entirely ass-backwards - if you use an Intel WiFi chipset, a nearby AP can broadcast the wrong region and cripple your connectivity.
Outdated regulatory databases and firmware efforts by vendors have generally made both illegal and legal usage beyond ch 1-12 at 2.4GHz rather difficult.
Lack of any IoCs also makes it hard to refute or remedy. Plus I think it paints even Tor relay nodes with the same brush as malicious proxies.
Truly kafkaesque if you start getting restricted and nobody tells you why or even knows what to tell you because the sources have all been mixed and obscured.
reply