home.social

#adguard — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #adguard, aggregated by home.social.

  1. Wollte etwas mit Filterlisten für #Adguard Home rumspielen und eventuell mit weiteren (brauchbaren) erweitern. Bin dann auf cybertalk.io/ gelandet. Auf dem Stand 99% bereits durch #uBlockOrigin blockiert. Das macht kein Spaß und ist auch nicht seriös. Weg damit.

    #uBlock_Origin #uBO #Tracking #Ads #Filterliste

  2. Den gestrigen Di.Day habe ich zum Anlass genommen, meine digitale Unabhängigkeit noch einmal massiv auszubauen:

    Ab sofort läuft bei mir auf einer kleinen Hetzner VPS ein AdGuard und ein Unbound DNS mit DNS over TLS. Jeglicher Netzwerktraffic der durch meine OPNsense und dann durch die Fritz!Box nach aussen geht, geht per DNS over TLS über meinen eigenen DNS mit entsprechenden Blocklisten.

    Ja, es ist kein VPN involviert. Vodafone bekommt also zumindest noch die IP Adressen mit.

    Aber in erster Linie ging es mir vor allem um den DNS Rebind Schutz und die Blocklisten.

    #diday #adguard #unbound #dns #opnsense #vodafone #unabhängigkeit #digitalesouveranitat

  3. roughtime.sandbox.google.com in #Adguard gesehen und wurde natürlich bereits geblockt. #Google ist echt ne Seuche.

    #Smartphone #Samsung #Ads #Tracker

  4. AdGuard has declined to change the default coloration of icons in the "App Management" tab of AdGuard for Windows, despite accessibility concerns.
    However, AdGuard has said they plan to introduce a high contrast theme some time in the future.

    github.com/AdguardTeam/Adguard

    #AdGuard #AdGuardWindows #Accessability

  5. Dandelion Sprout has raised a valid accessibility issue with AdGuard for Windows.
    In the "app management" tab, the options for each app are shown through small icons. If something is on, it is light green. If it is off, it is light grey. There is no other distinction on this page.
    Even as someone who isn't colorblind and has ok vision (and an ok monitor), the two look way to close.

    github.com/AdguardTeam/Adguard

    #AdGuard #Accessability

  6. Новый VPN-протокол TrustTunnel спасет нас

    Привет, Хабр! На днях AdGuard выложил в открытый доступ свой VPN-протокол, который назвал TrustTunnel. В статье разберемся, чем он отличается от того же VLESS и как устроен на самом деле.

    habr.com/ru/companies/femida_s

    #vpn #tcp #ip #udp #белые_списки #обход #блокировки #ркн #adguard

  7. Какие запросы и куда отправляет MAX

    Моя вторая статья - анализ сетевых запросов MAX и почему этот анализ - моё самое большое разочарование! Не ожидал я такого конечно, но описал все как есть.

    habr.com/ru/articles/939550/

    #max #мессенджеры #запросы #сетевые_протоколы #национальный_мессенджер #adguard #proxy #трафик #трекер

  8. I added a new service in my self-hosting:

    a DNS server with adblock support powered by NSD, Unbound, and AdGuard Home

    #freebsd #nsd #unbound #adguardhome #adguard #selfhosting

  9. 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 since 3 years: github.com/systemd/systemd/iss

    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 (github.com/systemd/systemd/iss)? 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: martinheinz.dev/blog/92

    #systemdresolved #ubuntu #Ubuntu2404 #uptimekuma #dns #usg #unifi #ubiquiti #adguard #pihole #netplan #networkmanager #ipv4 #ipv6 #alpine #docker #glibc #musl

  10. Quali DNS privati utilizzare?

    Una lunga lista di alternative: quali DNS privati utilizzare? Vi proponiamo anche molti DNS per bloccare pubblicità e traccianti!

    LINK --> lealternative.net/2022/07/13/q

    #OltreGoogle #adguard #DnsPrivati #doh #doq #dot #nextdns #quad9

  11. Quali DNS privati utilizzare?

    Una lunga lista di alternative: quali DNS privati utilizzare? Vi proponiamo anche molti DNS per bloccare pubblicità e traccianti!

    https://www.lealternative.net/2022/07/13/quali-dns-privati-utilizzare/