beerclue

joined 2 years ago
[–] beerclue@lemmy.world 3 points 9 hours ago

Grew up in a very religious home, in a very religious country (orthodox christian). I don't think I ever truly "believed", but I didn't want to upset my family, so I got married in church and baptized my kids. I am an atheist, and don't practice any religion now.

[–] beerclue@lemmy.world 4 points 2 days ago

Jizăs Craist.

[–] beerclue@lemmy.world 1 points 3 days ago

I don't think I've ever encountered what you say... I use WG it to access a network, not a device. I have a few dozen devices, physical and virtual, why should I set up wg on all of them? Tailscale, maybe, it's a different story, but I prefer to "self host" and not rely on a 3rd party provider. Wireguard was relatively easy to set up too, a few years ago... and in the meantime, if I need to add a new client, it's a two minute job.

[–] beerclue@lemmy.world 1 points 4 days ago* (last edited 4 days ago) (2 children)

Right, but I have wireguard on my opnsense. So when I want to reach https://jellyfin.example.com/ , if I am at home, it goes phone -> DNS -> proxy -> jellyfin (on the same network). If I am connected to the VPN, it goes from phone -> internet -> opnsense public ip -> wireguard subnet -> local subnet -> DNS -> proxy -> jellyfin. I see some unneeded extra steps here... Am I wrong?

[–] beerclue@lemmy.world 1 points 4 days ago (4 children)

Oh, I get that, but it just doesn't make any sense to me to be physically next to the server, and connect to it via VPN...

[–] beerclue@lemmy.world 1 points 5 days ago (7 children)

My network is not publicly accessible. I can only access the internal services while connected to my VPN or when I'm physically at home. I connect to WG to use the local DNS (pihole) or to access the selfhosted stuff. I don't need to be connected while I'm at home... In a way, I am always using the home DNS.

Maybe I'm misunderstanding what you're saying...

[–] beerclue@lemmy.world 2 points 5 days ago

I can stay connected, still works, but I don't think I need the extra hoops.

[–] beerclue@lemmy.world 4 points 5 days ago (9 children)

I also have a different subnet for WG. Not sure I understand what you're saying...

[–] beerclue@lemmy.world 10 points 5 days ago (16 children)

Same, wireguard with the 'WG Tunnel" app, which adds conditional Auto-Connect. If not on home wifi, connect to the tunnel.

[–] beerclue@lemmy.world 2 points 1 week ago (2 children)
[–] beerclue@lemmy.world 3 points 1 week ago

I've been daily driving Hyprland for 4 years now. Before that it was DWM, and before that Gnome. I was never a KDE fan, don't know why... I never disliked it, I just preferred Gnome.

 

cross-posted from: https://lemmy.world/post/27407351

When combined with today’s other vulnerabilities, CVE-2025-1974 means that anything on the Pod network has a good chance of taking over your Kubernetes cluster, with no credentials or administrative access required.

 

When combined with today’s other vulnerabilities, CVE-2025-1974 means that anything on the Pod network has a good chance of taking over your Kubernetes cluster, with no credentials or administrative access required.

view more: next ›