DNS based ad/abuse domain blocking | Hacker News Reader

DNS based ad/abuse domain blocking

github.com

36 pointsbehnamoh6 comments

Everyone I read about OpenWrt I go down the same rabbit hole. Look on their site, see compatible devices, read disclaimer about certain chip sets, check suitable device for preferred capability, find they aren't available to purchase or are too expensive. Do nothing.

Having used OpenWRT for a number of years, unfortunately the compatibility goes deeper than just the list of devices. My WRT3200ACM has had quite a few WiFi problems with mwlwifi despite being officially compatible.

If I were creating the setup today - I'd probably go for the route of having the gateway and wireless APs separate.

that’s the conclusion I have come to as well. Ubiquiti AP and pfsense router.

I’d love a OpenWRT or similar box, but I don’t want to spend 10 hours researching the correct device to buy. I want stuff that just works…

I did a bit of research on the router side - seems that passive cooled boxes like protect.li ones would work very well with pfsense or opnsense. Technically any x86 machine could work, but for an always on appliance it's important to keep the power draw in mind.

Tinyminimicro project from servethehome may be also worth checking out, they have a few appliance recommendations there.

Worse: not following the instructions quite right and brick your router. De-bricking requires buying a new router or finding/ordering a jtag cable adapter.

They sell routers openwrt pre-installed. Better guarantee on security updates for your router.

OpenWrt has a nice page on blocking DNS over TLS. It works by IP blocking the ever growing list of service IPs. You can set it up so it auto updates and blocks new IPs as they come online.

I think it's important to have control over your network and devices with your home. Devices should fall back to native DNS should DNS over TLS is unavailable.

Reply on news.ycombinator.com