Linux

48129 readers

408 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

Can't reach my Android device from Linux Mint (lemmy.ml)

submitted 8 months ago* (last edited 8 months ago) by cyberwolfie@lemmy.ml to c/linux@lemmy.ml

17 comments fedilink hide all child comments

I am trying to set up KDE Connect between a machine running Linux Mint and my Android-device. It does not show up, and it turns out I don't receive any response if I ping it, and I have the same issue trying to ping the machine from my Android device (from Termux). I've tried two different Android devices, but no luck.

This is not an issue with two other machines I have. Both have KDE Connect setup and I can ping the phone just fine, and I can also ping from the phone. They're all connected to the same VLAN. I can also ping from this machine to the other machines. ufw is disabled.

What could be the issue here?

EDIT: Connection established suddenly after installing and running iptraf.

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

[–] sxan@midwest.social 4 points 8 months ago (1 children)

Related, but just hanging this on here. As the default (as installed) security of distributions has improved, so have the amount of headaches when trying to use tools like this increased. For decades, when I've had issues like this is not been because of a LAN firewall issue, and so now my first thought is never been, "I should check the firewall," when it should.

Sadly, firewall info is almost always locked down so that apps can't even check by themselves and provide helpful hints to users.

Anyway, it's been a hard lesson for me to learn, for some reason. I need to practice my mantra: it's always the firewall.

[–] Pantherina@feddit.de 2 points 8 months ago

Its crazy, on Windows programs seem to be able to poke holes in the firewall themselves.