Larvitz :fedora: :redhat:
and 1 other
boosted
@selfhostingsh
Also possible alternatives to pi-hole: AdGuard Home, Technitium DNS
@Viq Good additions. AdGuard Home is arguably a better pick for most people now β built-in HTTPS filtering, encrypted DNS out of the box, and a cleaner UI. Pi-hole still wins on community blocklists and ecosystem.
Technitium is underrated. Full authoritative DNS server, not just a blocker. Worth it if you're running split-horizon DNS or need zone management.
Aleksandr Yakunichev
boosted
In the past couple of days I ran into increasing Internet connectivity issues.
At first I thought it could be a problem with public #DNS resolvers, but to my surprise it turned out to be my #OpenWRT router having a significantly high number of packet losses!
Time to update the OpenWRT firmware. I used auc to keep the existing configurations - which worked very well.
After the firmware update and reboot, packet losses were gone and RTA much more stable!
https://www.claudiokuenzler.com/blog/1523/update-openwrt-firmware-reboot-fixed-packet-loss-lan
In the past couple of days I ran into increasing Internet connectivity issues.
At first I thought it could be a problem with public #DNS resolvers, but to my surprise it turned out to be my #OpenWRT router having a significantly high number of packet losses!
Time to update the OpenWRT firmware. I used auc to keep the existing configurations - which worked very well.
After the firmware update and reboot, packet losses were gone and RTA much more stable!
https://www.claudiokuenzler.com/blog/1523/update-openwrt-firmware-reboot-fixed-packet-loss-lan
Seth of the Fediverse
boosted
Along the way my ISP's router #DNS cache and #DHCP server helped to frustrate me at every turn π it's why I tacked on the side-project of installing #PiHole, though not quite ready to cut over to that as DHCP server yet.
At the very least my three main network machines now have easy to remember static IPs so when all else fails I don't have to open the awful router web interface to find my stuff.
Overall though I'd call this experience a success. No data was lost and I learned a lot π
Well it took a whole long weekend of troubleshooting and rebuilding, but once again my #homelab is running smoothly. There were a few factors that combined to degrade things to a point where I just needed to examine my whole network and what was running on my machines.
The root turned out to be a network bridge configured with #systemd-networkd not playing nicely with docker being installed to run a big compilation job.
Once #docker screwed with the network config things spiralled from there.
Along the way my ISP's router #DNS cache and #DHCP server helped to frustrate me at every turn π it's why I tacked on the side-project of installing #PiHole, though not quite ready to cut over to that as DHCP server yet.
At the very least my three main network machines now have easy to remember static IPs so when all else fails I don't have to open the awful router web interface to find my stuff.
Overall though I'd call this experience a success. No data was lost and I learned a lot π