mosquitto VS Pi-hole

mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;

References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd http://www.proftpd.org/ accessed on 01/27/2018. Filezilla https://filezilla-project.org/ accessed on 01/27/2018. Fritzing https://fritzing.org/ accessed on 05/25/2022. Appendices:

This is a perfect use case for MQTT, e.g. this library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message.

While working on a personal project Komponist, I was due to update Mosquitto MQTT Broker due to a CVE and found some interesting changes that will impact me in the future when it comes to configuring the Broker. This post provides a solution to make the Broker compatible with future versions using new and less visited concepts in Docker Compose v2, namely:

Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server

I think he means implementation of MQTT protocol, like https://mosquitto.org/

Could MQTT work for you? You'd need a broker like Mosquitto, and then any of a number of MQTT clients.

Si te preguntas, ¿por qué no usar Adguard o Pihole? 🤔

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.