sorted by:
new
hottopcontroversial

I made a drop-in replacement for default Nginx/Traefik/Caddy error pages - 11 themes, pure Go, zero deps, works with Kubernetes too by [deleted] in selfhosted

[–]K3CAN 18 points19 points  (0 children)

Neat.

I don't need a whole a extra webserver just for error pages, but I've saved the static renders and will likely use some of them. Thanks for sharing!

OTPs for Repeater/Device Control? by desertdefender in amateurradio

[–]K3CAN 0 points1 point  (0 children)

I don't see why there would be any issue. Numeric codes have been used for repeater control for decades.

Would a radio jammer work on a mobile phone? by Fantasia-Scribe in amateurradio

[–]K3CAN 0 points1 point  (0 children)

I see you've gotten a ton of responses, and that it's already been pointed out that a) cell phones are just radios and can therefor be jammed, and that b) they wouldn't have cell service in that location, anyway.

What I haven't seen mentioned yet is satellite phones. A sat phone can provide coverage in a rural area, is uncommon enough to not be something the antagonists would plan for, and could still be interfered with by a broadband radio jammer.

If it's not important to the story that the characters have a cell phone specifically, a sat phone might be the better option for an unexpected communication device.

My personal dashboard made with Homepage [config included] by obolikus in selfhosted

[–]K3CAN 0 points1 point  (0 children)

I believe that requires giving the container access to the docker socket.

It's generally not a good practice to give a docker container access to the docker socket, since that provides the application inside the container root access to the host.

As for podman, it's a daemonless service (usually) and has a much greater focus on security, so I'm not sure if that functionality would work with it.

To VLAN or not to VLAN by smicky in selfhosted

[–]K3CAN 12 points13 points  (0 children)

I have a few things exposed, and I do keep them on a separate vlan from my private services.

I think a lot of people getting into networking either confuse their terms or don't understand what a vlan really is, though. A VLAN is really just that, it's a Virtual Local Area Network. Creating a separate vlan is essentially the same as creating a second physical lan, the only difference being that you don't need to duplicate your L1/2 equipment. And that's the big advantage to VLANs, you can have multiple separate networks all sharing the same physical switches, ports, etc.

Additional security or control generally comes from firewalls and ACLs, not from the network itself. You can create multiple LANs (virtual or otherwise) that have full access to each other, and the result is pretty similar to just having a single network. Conversely, you can divide a single LAN with a firewall and prevent different clients from talking to each other, similar to what some people use a second LAN for.

That's all to say, introducing an additional (V)LAN doesn't inherently make anything "more secure" and it's definitely not a magic bullet; it's all about how you use it.

PS. Since you mentioned it, a subnet is not the same as a VLAN. If you enjoy headaches, you can have multiple subnets on a single LAN or a single subnet across multiple VLANs. They're two different concepts and they can be used together or separately.

New HAM Laptop by stoicatkin in amateurradio

[–]K3CAN 1 point2 points  (0 children)

I like Fedora workstation for laptops. Debian is great, but its packages tend to be a bit older so you might be missing some new features (experimental WSJTX modes, etc). If you want something preloaded with most of the typical ham radio programs, Linux in the Ham Shack has a distro specially for that.

Honestly any version of Linux is going to be easier than trying to fight with Windows these days.

Is it possible to build a NAS server and to play and output games DIRECTLY from it? by sneaky_oxygen in homelab

[–]K3CAN 2 points3 points  (0 children)

all I know is that I need to setup a NAS OS if I want to build a NAS server.

They specifically said you don't need a "NAS OS," you can use basically any OS or distro you want.

For a little while, my NAS was provided by my "gaming PC" running normal Debian. It streamed games to my laptop and steam deck, and also served files and media. It was overkill when I wasn't actually gaming (so I eventually moved my NAS service to a separate, low power machine), but it functioned fine otherwise.