Notices by Just Dude (justdude@mastodon.bsd.cafe)

@andy_warb @feld it lacks some good community promotion but the actual use is non commercial

https://community.openhab.org

I got started and got it running in Freebsd in minutes, the dashboard and integrated stuff works fine

I am switching from Home assistant to OpenHab.
I like the setup, automations. Modeling my equipment in rooms, floors is super handy
The gui is also nice and easy, graphs are not setup but the examples look nice.
The export of data to MySQL or any other persistent database is simple and integrated

What a respectable amount of plugins
It is a bit new and fiddling withall the new ways it gets configured but intuitive

So any tips or links to how-to guides and best practices?

#OpenHab

Just flashed into my mind, I spent hours less on system maintenance since I switched from Linux and Proxmox to #freebsd and #bhyve

It is easy to install, it is up and running…. No memory leaks, no package conflicts, no nothing except steady performance and user (sysadmin) joys

Remarkable effort. Thanks

Anyone tips to reduce the CPU and memory usage of #BHyve instances?

Looking at my #freebsd box running 10 jails, these 2 at the top consume more then all 10 jails together

I can reduce the assigned CPU and memory, but anything else would help.
The 2 Linux VMs are needed due to their invasive installs.
Maye #Podman can come to the rescue?

Podman working install on #freebsd

Next step is to test an OCI linux image via #podman

Forgot to mention this for #freebsd to you all

https://github.com/0xERR0R/blocky

Blocky

Blocky is a DNS proxy and ad-blocker for the local network written in Go with following features:

Features

Blocking - Blocking of DNS queries with external lists (Ad-block, malware) and allowlisting

Definition of allow/denylists per client group (Kids, Smart home devices, etc.)
Periodical reload of external allow/denylists
Regex support
Blocking of request domain, response CNAME (deep CNAME inspection) and response IP addresses (against IP lists)
Advanced DNS configuration - not just an ad-blocker

Custom DNS resolution for certain domain names
Conditional forwarding to external DNS server
Upstream resolvers can be defined per client group
Performance - Improves speed and performance in your network

Customizable caching of DNS answers for queries -> improves DNS resolution speed and reduces amount of external DNS queries
Prefetching and caching of often used queries
Using multiple external resolver simultaneously
Low memory footprint
Various Protocols - Supports modern DNS protocols

DNS over UDP and TCP
DNS over HTTPS (aka DoH)
DNS over TLS (aka DoT)
Security and Privacy - Secure communication

Supports modern DNS extensions: DNSSEC, eDNS, ...
Free configurable blocking lists - no hidden filtering etc.
Provides DoH Endpoint
Uses random upstream resolvers from the configuration - increases your privacy through the distribution of your DNS traffic over multiple provider
Blocky does NOT collect any user data, telemetry, statistics etc.
Integration - various integration

Prometheus metrics
Prepared Grafana dashboards (Prometheus and database)
Logging of DNS queries per day / per client in CSV format or MySQL/MariaDB/PostgreSQL/Timescale database - easy to analyze
Various REST API endpoints
CLI tool
Simple configuration - single or multiple configuration files in YAML format

Simple to maintain
Simple to backup
Simple installation/configuration - blocky was designed for simple installation

Stateless (no database, no temporary files)
Docker image with Multi-arch support
Single binary
Supports x86-64 and ARM architectures -> runs fine on Raspberry PI
Community supported Helm chart for k8s deployment