frederic (@frederic@chaos.social)
Ich schaue mir nach langer langer Zeit noch mal #PiHole an, aber für ihre API möchte ich sie schon mal hauen:
- Authentifizierung per GET-Parmeter statt Header
- CRUD-Operationen nicht mit PUT/POST/DELETE sondern GET `action=set/delete`
- Gibt *immer* HTTP 200 zurück, aber im Body dann `{"success": false}`
Show Original Post
amgine (@amgine@mstdn.ca)
I see very few advertisements, using #pihole + #uBlockOrigin + #PrivacyBadger (does not affect advertising, per se, but does affect tracking which *does* affect advertising.) + more.
I answered 'Qualified no'. I am generally positive toward sites which serve their own advertising - e.g. sailboatdata.com - which circumvents all my adblocking. But ads are the primary distribution for exploits - which M$/Goog/&c. know - so any ad is a risk.
#AdBlocking is #CyberSecurity.
Show Original Post
lauchmelder (@lauchmelder@social.tchncs.de)
@kuketzblog
Bei mir laufen einige Raspis:
#nextcloud mit 5 TB auf raspi4 8gb
#pihole auf einem raspi zero2
#kodi auf einem raspi3b
#rasbian mit xrdp auf einem raspi 4 4gb zu testzwecken
Show Original Post
mycel (@mycel@mastodon.floe.earth)
@kuketzblog
#pihole und #OpenCPN
Show Original Post
d33pjs (@d33pjs@infosec.exchange)
It's always DNS, right? If someone experiencing some strange issues with ubuntu, maybe this toot is for you.
tl;dr: switch from systemd-resolved to resolvconf.
I thought, the saying from the beginning was just something from the "old days". No DNS Problems in 2024 anymore, right? But Ubuntu taught me different.
Ubuntu is using systemd-resolved since 20.04 (if I'm correct). But I was shocked, when I was looking at my uptime kuma Container on a Ubuntu 22.04 LTS Host. It was constantly failing. Sometimes 3 services at the same time, sometimes just 1 service a day. One Check suddenly failed. 60 seconds later, the next check, switched back to green again. But all fails had the same error message: "getaddrinfo ENOTFOUND domain.com". Doesn't matter if they were internal domains or external. Sometimes some of them just failed.
I thought it could be an old Firewall Applience that were running at like 120% system utilization and were serving DHCP and (with this) internal DNS. But no. Not even high latencies from that Firewall. Then I thought it might be AdGuard (in a Docker Container). So I switched to PiHole. But the problems were still the same.
Then I turned on debug logs of systemd-resolved and found out that sometimes it was switching to the secondary DNS Server for whatever reason and just attaching the search domain to the following requests:
1. AAAA of demodomain.com
--> no answer (because only A were available)
2. A of demodomain.com
--> somehow failed, systemd-resolved switched to second DNS (debug log of systemd-resolved is hard to read, not sure why it somehow failed)
3. AAAA of demodomain.com.local
--> it just attached the searchdomain of the system to the domain which now resulting in errors from all following DNS Server
After another round of wrong requests it suddenly get back his head. But in the meantime, uptime kuma already failed.
The solution in my case: switch "back" to resolvconf package on Ubuntu. Which comes to at least one downside: it seems to not have an interface to netplan and/or networkmanager (which leads to manual creating and managing of resolv.conf, not via DHCP, bummer). But after I switched: Everything is working fine and without any problems since days.
"We" also have an open bug report which since 3 years: https://github.com/systemd/systemd/issues/21123
It's not exactly the same issue, but I think the root cause is connected somehow: it seems to be a problem of IPv6.
But a) I need (or better: want) IPv6 in my case/that network and b) WTF? How can this be a good solution to turn off IPv6 (https://github.com/systemd/systemd/issues/21123#issuecomment-2028976737)? Not to mention that we still need a solution for Post-IPv4.
By the way: If you still experiencing DNS issues inside Docker Container, maybe Alpine could be another issue: https://martinheinz.dev/blog/92
#systemdresolved #ubuntu #Ubuntu2404 #uptimekuma #dns #usg #unifi #ubiquiti #adguard #pihole #netplan #networkmanager #ipv4 #ipv6 #alpine #docker #glibc #musl
Show Original Post
Papeleo (@Papeleo@mastodon.social)
1a. #Pihole zum Blocken unerwünschter Datenverbindungen aller Geräte im Haus
1b. #PiVPN, u.a. damit alle unsere Geräte auch von unterwegs das Pihole nutzen können
2. #Solaranzeige zur lokalen Visualisierung der Leistungsdaten meiner PV-Anlage über Grafana, also ohne den chinesischen Server des Herstellers
Show Original Post
zeesem (@zeesem@muenchen.social)
Und #Tandoor als lokal gehostetes Kochbuch.
Show Original Post
jskeletti (@jskeletti@det.social)
Es ist erschreckend, wie viel Werbung, Tracker und sonstiges Ungeziefer die #PiHole wegsenst...
Show Original Post
wutti (@wutti@digitalcourage.social)
Raspberry Pi mit #PiHole, #DNSCryptProxy und #DietPi installiert und konfiguriert 💪
Show Original Post
deflockcom (@deflockcom@mastodon.social)
Same indeed
#ads #ad #virus #antivirus #malware #security #web #adguard #brave #ublock #pihole #meme #memes
Show Original Post
sb (@sb@fed.sbcloud.cc)
@jwildeboer @bert_hubert
This will be a great "smell test" to hear what's getting by tracker blockers in the browser, on a #piHole, whatever. It's almost like it was designed for vision impaired folk, which I dig.
Show Original Post
gcvsa (@gcvsa@mstdn.plus)
If anyone has any leads on good #pihole blocklists that cover AI-generated bullshit websites, I'd appreciate a tip.
I was just searching for a picture of a particular product, and DuckDuckGo returned many results from obviously fraudulent #AI #generated sites like "10 Best (extremely specific product name of which there is only one in existence)". #10Best is a dead giveaway.
I've added a bunch of them to my local #blacklist, but I'd like to not have to play whack-a-mole all by myself lonesome.
Show Original Post