this is what I’m talking about when it comes to the selfhosted communities.

if you don’t know how to properly segment and vlan your network, you have no business exposing your shit to the internet.

I wouldn’t go onto a teen community and spout off how to make explosives even though they’re relatively safe to a trained individual.

same reason behind not allowing a hobbyist and amateur community to think that iptables and firewalld is the best/only solution.

it’s dangerous and someone will get hurt eventually.

this is selfhosted. a community that’s predominantly amateur or hobbyist.

• anyone gaining physical or remote access to the device can set rules. by protecting the entire network with a hardware firewall you mitigate attack vectors from other hardware on your network that become compromised.
• iptables and firewalld are notorious for locking users out of the system by overzealous or green system admins. in the msp world this happens practically by the hour.
• iptables and firewalld can be used against you in the event of a breach. one of the first things an attacker may attempt is to forward ports and lock system admins out as they take over the system.
• make sure you save your rules properly or they’ll be gone after a reboot or botched upgrade
• migrating your rules from one system to another when you’re changing hardware or restoring a system is a huge pain in the ass.
• got a network change that’s going to modify the subnet your systems are on? get ready to migrate all 15 of your devices one by one for the next 8-15 hours (depending on the complexity of your rules)

it’s far easier, and safer to have all your network config done in the network. from system migrations to securing/hardening. it’s far more efficient and effective to have a single source of truth that manages network routing and firewall rules. hell, you can even have a redundant or load balanced firewall configuration if you’re afraid of a single point of failure.

point is, firewalld and iptables is for amateur hour and hobbyists.

if you want to complain that “docker doesn’t respect system firewalls” then at least have the chutzpah enough to do it the right way from the beginning.

What if you rent a bare metal server in a data center?

any msp will work with your security requirements for a cost. if you can’t afford it, then you shouldn’t be using a msp.

Or rent a VPS from a basic provider that expects you to do your own firewalling?

find a better msp. if a vendor you’re paying tells you to fuck off with your requirements for a secure system, they are telling you that you don’t matter to them and their only goal is to take your money.

Or run your home lab docker host on the same vlan as other less trusted hosts?

don’t? IDK what to tell you if you understand what a vlan is and still refuse to set one up properly to segment your network securely.

It would be nice if there was a reliable way to run a firewall on the same host that’s running docker.

don’t confuse reliable with convenient. iptables and firewalld are not reliable, but they are certainly convenient.

You may say these are obscure use cases and that they are Wrong and Bad. Maybe you’re right, but personally I think it’s an unfortunate gap in expected functionality, if for no other reason than defense-in-depth.

poor network architecture is no excuse. do it the proper way or you’re going to get your shit exposed one day.

this is the second time I’ve seen a post like this.

docker has always been like this. if it’s news to you then you must be new to docker.

if you’re using the built in firewall to secure your system on your wan, you’re doing it wrong. get a physical firewall. if you’re doing it to secure your lan then you just need to put in some proper routes and let your hardware firewall sort it out with some vlans.

don’t rely on firewalld or iptables for anything.

I have written so many scrapers in my life that would have probably helped thousands of people.

it was all for porn though. they shall never see the light of day.

(sits in his Lamborghini Plex while a beautiful blonde gives him a handy) I’m fine, mate. Maybe later.

fun fact. git allows you to use emojis for branch names.

can’t wait for this to start. then maybe I won’t have to hear about it from the jellyfin shills every week.

I’m almost certain you changed your comment.

however, I fail to see the relevancy of proxies and tunnels to the content of the original post.

just pay for a lifetime pass…

these damn kids will wake up on day and go, “why do you need xpg? jpgxl is just fine!”

they don’t realize it yet that the only reason why jpeg xl exists is to silently slip that corpo collar around their necks.

🤷 only time can feed wisdom and cure stupid.

going for the nuclear option I see…

oh I asked. this is a big company with 6-8k employees.

the answer was always, “no”.

looking for my plot, though I might just become a fur trapper instead of a farmer.

I had two options at work.

Mac or Windows 11.

Mac user here.

get hired as an entry level Q&A, drink with the devs when you break their shit.

they’ll accept you eventually.

I have only ever know two devs that knew what the fuck OSI was. two out of at least one-hundred and fifty.

it’s nice to see a technical joke on here that’s more than just “hehe your language is bad”.