overview for bravemonkey

A years-long investigation just unmasked a major torrent pirate, the how remains unclear in c/piracy@lemmy.dbzer0.com

[–] bravemonkey@lemmy.ca 2 points 2 days ago (1 children)

Why are you switching away from Mullvad? My Nord subscription is ending soon, I was planning on subscribing to Mullvad for the privacy.

Getting to Know Nintendo Switch 2 – Freeing up Storage Space in c/nintendo@lemmy.world

[–] bravemonkey@lemmy.ca 3 points 3 days ago

They should allow deleting save files in bulk. Every demo creates a save that is a pain to remove when there are many of them.

Dreamwidth Studios in c/opensource@lemmy.ml

[–] bravemonkey@lemmy.ca 5 points 3 weeks ago* (last edited 3 weeks ago)

This will sound harsh, but you got downvoted for posting a random link to a github page without any explanation of what it was or why anyone might be interested in it.

Try a little bit more effort next time maybe.

How do I choose which independent developers to donate to and how much should I donate? in c/nostupidquestions@lemmy.world

[–] bravemonkey@lemmy.ca 23 points 2 months ago (1 children)

No amount of donations should be considered shameful, and anyone who tried shaming you for donating isn't worth your time

If someone opened a store and just sold stuff at cost, which undercuts every other competitors by alot. Would this not for the big corps to come way down on their prices? in c/nostupidquestions@lemmy.world

[–] bravemonkey@lemmy.ca 7 points 4 months ago (2 children)

How would this store afford to pay its employees, rent and utilities if it only sold things at cost? One store alone would also make no difference, you’d need a chain of many stores.

1

Podman rootless - forwarding container port through firewalld on the same port fails (lemmy.ca)

submitted 2 years ago* (last edited 2 years ago) by bravemonkey@lemmy.ca to c/containers@lemmy.world

0 comments fedilink

I’m running a rootless podman container listening on port 8080 on OpenSUSE Tumbleweed.

From the same host, there's no problem accessing the container. Trying to access the container remotely fails due to firewalld blocking the connection.

What I don't understand is this:

If I configure firewalld to forward port 80 to the container on port 8080 using

firewall-cmd --add-forward-port=port=80:proto=tcp:toport=8080

I can access the container from a remote computer using port 80.

However, if I try:

firewall-cmd --add-forward-port=port=8080:proto=tcp:toport=8080

I'm not able to reach the container. It seems that every port I try will work except for port 8080 in this case, and I can't find any references explaining why this might be the case.

What's going on here? Is it a conflict by trying to forward a port to itself? Is there any way to allow port 8080? Trying to allow port 8080 in the public zone fails as well.