Linux

48287 readers

647 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

What am I doing with iptables? (lemmy.pe1uca.dev)

submitted 4 months ago by pe1uca@lemmy.pe1uca.dev to c/linux@lemmy.ml

10 comments fedilink hide all child comments

I've only used ufw and just now I had to run this command to fix an issue with docker.
sudo iptables -I INPUT -i docker0 -j ACCEPT
I don't know why I had to run this to make curl work.

So, what did I exactly just do?
This is behind my house router which already has reject input from wan, so I'm guessing it's fine, right?

I'm asking since the image I'm running at home I was previously running it in a VPS which has a public IP and this makes me wonder if I have something open there without knowing :/

ufw is configured to deny all incoming, but I learnt docker by passes this if you configure the ports like 8080:8080 instead of 127.0.0.1:8080:8080. And I confirmed it by accessing the ip and port.

you are viewing a single comment's thread
view the rest of the comments

[–] lemmyvore@feddit.nl 7 points 4 months ago* (last edited 4 months ago) (1 children)

Keeping a port open if you don't want it open is bad practice.

Why even bother having a firewall then? I mean, why block any ports if you're going to open the ports for services anyway, and there's nothing listening on the others, right?

The point of having a firewall is that you start with DENY on all possible chains and interfaces, and you describe explicitly what is allowed to happen.

A firewall thus becomes a living specification of the networking rules for your server, the same way ansible for example describes the functionality.

If you're not willing to do it like that then don't bother having a firewall, there's no point.

[–] atzanteol@sh.itjust.works 2 points 4 months ago (1 children)

I'm responding to this

I'm asking since the image I'm running at home I was previously running it in a VPS which has a public IP and this makes me wonder if I have something open there without knowing :/

What you're saying is true - but practically speaking there isn't a real risk to having a port open that has nothing listening on it. Maybe a port scan can identity your OS a bit better.

[–] lemmyvore@feddit.nl 1 points 4 months ago (1 children)

The main goal should be having a thorough approach. People hear "firewall" and assume it means blocking things but it's really about having a comprehensive network specification.

[–] atzanteol@sh.itjust.works 2 points 4 months ago

Yes - again you're talking about "theory" and I agree completely. I'm not arguing with you.

I'm saying that "dude you're probably fine if you've opened your firewall for a while to get something working".