ShitpostCentral

For instance, say I search for "The Dark Knight" on my Usenet indexer. It returns to me a list of uploads and where to get them via my Usenet provider. I can then download them, stitch them together, and verify that it is, indeed, The Dark Knight. All of this costs only a few dollars a month for me.

My question is, why can't copyright holders do this as well? They could follow the same process, and then send takedown requests for each individual article which comprises the movie. We already know they try to catch people torrenting so why don't they do this as well?

I can think of a few reasons, but they all seem pretty shaky.

1. The content is hosted in countries where they don't have to comply with takedown requests.

It seems unlikely to me that literally all of it is hosted in places like this. Plus, the providers wouldn't be able to operate at all in countries like the US without facing legal repercussions.

2. The copyright holders feel the upfront cost of indexer and provider access is greater than the cost of people pirating their content.

This also seems fishy. It's cheap enough for me as an individual to do this, and if Usenet weren't an option, I'd have to pay for 3+ streaming services to be able to watch everything I do currently. They'd literally break even with this scheme if they could only remove access to me.

3. They do actually do this, but it's on a scale small enough for me not to care.

The whole point of doing this would be to make Usenet a non-viable option for piracy. If I don't care about it because it happens so rarely, then what's the point of doing it at all?

I'm trying to setup Wireguard to use as a VPN on my server using this guide. I currently run Pihole on the same machine.

The handshake succeeds, and I can even ping IP addresses. However, it doesn't receive DNS responses. I checked in Wireshark and see the following:

I'm admittedly pretty inexperienced when it comes to routing, but I've been at this for days with no success. Any help would be greatly appreciated.

Edit

I now realize that it would have been relevant to mention the my Pihole instance was running inside a rootless podman container.

To test things further, I wrote a small echo server and spun it up on bare metal. Wireguard had no issues with that. My guess is that something between wireguard and specifically rootless podman was going wrong. I still don't know what, unfortunately.

My fix was to put Pihole in a privileged podman container with a network and static IP e.g. --net bridge:ip=10.88.0.230. I also put wireguard into a privileged podman container on the same network --net bridge. Finally, I set the peer DNS to the Pihole's static IP on the podman network (10.88.0.230).

As I said before, I still don't know why podman wasn't replying to the correct IP initially. I'm happy with my fix, but I'd still prefer the containers to be rootless so feel free to message me if you have any suggestions.