So, check this little idea that I have - I want to browse the internet without all sorts of unscrupulous actors collecting every little bit of metadata on me and my family they can possibly get their hands on.
  • Donut@piefed.socialEnglish
    2·
    5 days ago

    Don’t fall for the trap that they recommend an expensive Pi 5: I am running Pi-hole on a Pi 2 but you can basically run this on obsolete hardware, whether that’s a Pi or a PC/laptop

    • DefederateLemmyMl@feddit.nlEnglish
      1·
      5 days ago

      Misleading statement. It doesn’t block “traffic”, it blocks DNS requests… you don’t know how much traffic this corresponds to.

      • xavier666@lemm.eeEnglish
        11·
        5 days ago

        Correct. The payload of DNS requests is tiny compared to, say requesting a webpage. So there might not be a huge decrease of bandwidth usage reduction. However, having 66.6% less DNS requests is still a win. The router/gateway doesn’t have to work that hard because of the dropped requests.

        • DefederateLemmyMl@feddit.nlEnglish
          2·
          5 days ago

          It isn’t so much about the payload of the DNS requests, but about the content that would have been loaded if the DNS request hadn’t been blocked.

          If you load a page that has 100kB of useful information, but 1MB of banner ads and trackers … you’ve blocked a lot more than 66%. But if you block 1MB of banner ads on a page that hosts a 200MB video, you’ve blocked a lot less.

          Also a 66% blocked percentage seems very high. I have installed pihole on 2 networks, and I’m seeing 1.7% on my own network, but I do run uBlock on almost everything which catches most stuff before it reaches the pihole, and 25% on the other network.

          • mac@lemm.eeEnglish
            1·
            4 days ago

            I run a handful of instances across different networks, 1.7% is suspiciously low, you should make sure you’ve got the right lists. I like HageZi’s

        • rusticus@lemm.eeEnglish
          01·
          4 days ago

          Of course, because ads have zero bandwidth. /s

          Are you an idiot?

          • xavier666@lemm.eeEnglish
            1·
            4 days ago

            As per the article

            on my own network a whopping 66.6% of all traffic is blocked

            I stated it’s actually 66.6% DNS requests being blocked, not the raw bandwidth utilization. Raw bandwidth savings (by not downloading the non-zero ads) would be much lesser.

            Can’t we be nicer on the internet?

            • rusticus@lemm.eeEnglish
              0·
              3 days ago

              No, raw bandwidth savings would likely be very significant. You do realize that for many webpages the ads are most of the bandwidth? On my network (I have capped internet so this is important) if I run dns ad blocking my total bandwidth is 40% less.

              • sonstwas@sh.itjust.worksEnglish
                1·
                3 days ago

                I’m not sure whether it makes sense trying to discuss with you but let’s try…

                You couldn’t know how much traffic you saved because you didn’t load the ad. The ad could be 1KB, 1MB or 1GB, but because you didn’t load it you wouldn’t know it’s size. Without knowing it’s size, you wouldn’t be able to calculate the savings.

                As mentioned somewhere is in the thread you would have to directly compare two machines visiting the same pages and even then it’s probably only approximate because both machines might get served different ads.

  • President@sh.itjust.worksEnglish
    1·
    5 days ago

    I’ve been thinking of setting one up for a while, if I have a home server would I be better off hosting it on that or as a separate device? What are the alternatives to a raspberry pi? They’ve shot up in price over the years.

    • normalexit@lemmy.worldEnglish
      1·
      5 days ago

      If you have a server running, I wouldn’t buy more hardware. They have good example documentation for just such a configuration:

      https://docs.pi-hole.net/docker/

      If your server already has those ports bound (specifically the DNS port 53) you are going to have to get creative; otherwise it’ll work well!

      Worst case, a cheapo pi 3 will do the job. At one point I had it running on a pi zero, so hardware requirements are pretty low.

        • StarkZarn@infosec.pubEnglish
          1·
          4 days ago

          That’s not how that works. network_mode: host shares the network namespace with the container host, so it doesn’t do any NAT, it only exists on the host’s IP. It would be akin to running a natively installed app, rather than in a container. macvlan networking is what gives a container its own IP on the logical network, without the layer of NAT that the default bridge mode networking that docker typically does.